Yeah, that's part of why I said I'm not entirely convinced. 1 hours vs 2 hours is an unrealistic example. I do still think it can make sense, but the extra actual productivity is probably more in the vein of "getting an extra hour on a 10 or 20 hour project".
Very much agree. It's a pretty common mistake to bundle real information with obviously wrong details and lose credibility. Especially in the eyes of people looking for a reason to discredit the argument.
The disingenuous people who discredit climate change will do so no matter how serious people act. There is no point in changing behavior on their account.
The point is to convince people who are undecided. Using information that's known to be false or weakly supported is then short-sighted and counterproductive, because enough false predictions will turn up that those undecided will tune out entirely
> I also want to say I really appreciate Tim Cook’s emphasis on user privacy and I hope John Ternus can continue this trend.
You're kidding right? News [1] just broke about how Apple's permanent notification storage (that they refuse to fix) undermines encryption and is being exploited by law enforcement. And they conveniently left out the fact that they were giving out push notification data to law enforcement without any warrants from their transparency reports [2]. And these are just from the top of my head.
Do we now presume all companies putting the word privacy on their ads are emphasizing privacy? Because Meta and Google does that too.
Wow, the worst example of violation of privacy is...(wait for it) local push notification storage being plaintext. We already bought it, no need to sell more Apple product to us!
Really what apple is doing is putting a spin on their core business model of selling users the technology rather than renting it to them by subsidizing its development through spying.
It's not so much that privacy is apple's goal, but rather privacy is inherent to apple's business model (unlike google, which has always been spyware).
> I simply don’t do anything that won’t teach me something new or improve my existing skills.
Not trying to be rude but you either must not be a professional software engineer or your skill level isn't that high yet. You simply cannot always do things that teach you new skills or improve existing ones. In any sufficiently complex project, even the most novel ones, you'll do things you've done many times before.
I think professionals are almost always doing things that are at least 30% new...otherwise they've had a long time in one job which is a fortunate thing nowadays.
My last job started with "here's a book about go programming." 2 years later I was learning FastAPI. Now I'm programming in C again but I have spent most of my time learning about git actions and writing SCCS->git conversion software. I've never used SCCS before.
I'm a bit skeptical too, but I can understand his points. Most of what is rote is probably written somewhere and if you have a library of code and snippets (including the existing project), it's easy to copy and adapt it. And that activity is very inducing to flow state, so you don't mind the time spent.
I’m not a software engineer. Most of my work these days focuses on microcontroller exploitation. I have 15 years of professional experience as a security consultant/contractor.
Makes me think they might not have the most knowledgeable people on the job. Hopefully they didn't just throw some unwilling Windows devs into the unknown.
Background shader pre-compilation does not use all cores by default and the only way to change that is to manually edit a file. So unless you're consciously changing it, you won't have this problem. It'll only use all cores when you launch the game.
I have been having the issue with the system hanging up when steam is doing big writes. I had assumed it was due to something wrong with my drive and was contemplating reformatting it.
I like Helix. I couldn't get Neovim to stick after a few tries but Helix let me into the modal editor world. Just works, no config required and their editing model is better for newcomers because you can see what you're about to do. I eventually switched to Neovim after a few months though (thanks to Kickstart.nvim), because configuring with a programming language is just so much more powerful.
That said, I'm convinced people praising Helix because they "don't have to install 60 plugins" or "constantly keep tweaking their config" will just start blaming Helix when it gets plugin support and if it gets a dynamic configuration language.
You don't have to install 60 plugins (I have 6) and you don't have to keep tweaking your config (I haven't touched core parts of my config in years, just like to play around with logic sometimes). It's not a feature to not support these things just because you lack the self control to stop playing with your editor and focus on your work.
> I'm excited to see how neovim is making progress with native LSP, but for years getting it working meant continuously tweaking vimscript/lua code or adopting a plugin written in TypeScript.
Lua and native LSP supports were introduced at the same time. Not getting how you would tweak Lua code to get LSPs to work before Neovim had native support.
> LSP just worked; it read what was on the $PATH and used it.
This is how Neovim loads LSPs as well. You don't need a plugin to download and manage LSPs. You can just install them externally yourself.
> not spending any time configuring LSP servers were the top problems plaguing my usage of neovim.
It's been years since it's just a few lines to enable LSPs with the config shipped in nvim-lspconfig if you don't want to override any server-specific settings. And even then its still pretty easy.
I will give you that Neovim should ship with nvim-lspconfig and just load a compatible LS if its already in the PATH. Enabling each server one wants to use is annoying. But again, it's just a few lines (and I'm pretty sure a lot of people wage war if they did either of those things because "bloat").
I'd explicitly configure which servers were triggered which filetypes (aka autocmd and when I first started doing this, the binding for autocmd didn't even exist in lua yet) and have to bind lsp functions to keybindings across languages. FWIW, I have no idea what I would've done in vimscript, lua is a godsend with tables, loops, and lambdas. At this point in time, I was an early adopter neovim's built-in LSP and everyone else was recommending coc.nvim.
But the juxtaposition at the time was that Helix ships `languages.toml` that includes all of this already out of the box. You can override it, if you want, but actually all I wanted was cohesive keybindings for basic LSP functions.
This assumes that that hour shaved was used elsewhere productively which is not the case.
reply