I've been using JetBrains IDEs for the last 11 years. Before that I used Emacs and Sublime Text. I've tried VSCode, Zed, and others. There's just no comparison on the code insights and code manipulation tools. LSP is far behind what JetBrains can do, although it's slowly catching up these days. I still use VSCode from time to time for other languages like Zig.
I've never experienced sluggishness, but, I also keep track of how much memory it's using and ensure I don't run low. It's clearly a huge resource hog, but I'm also glad for that. It's using all of my computers resources to analyze the code in amazing ways which help me develop fast. Emacs, Sublime Text, and others were all about typing speed. Fast development goes far beyond just typing speed.
Right -- see, I basically maxed out "Mavis Beacon Teaches Typing" in high school. (That is, I practiced with it regularly until it couldn't find any particular problem with my typing, and resorted to giving me practice typing symbols, at which point I got bored and quit.) What prompted me to look at Colemak (and mechanical keyboards) was when some friend/colleagues at work were playing with typeracer.com, and I clocked in at 120WPM on one of the first races. One of my friends didn't really believe it and asked me to repeat the performance in front of him, which I did.
That made me think, maybe if I switched to Colemak and got a better keyboard, I could go even faster. I did both; and though my forearms certainly feel less tired on the odd occasion that I have long bouts of continuous typing to do, I'm neither noticeably faster nor more accurate.
So, both our anecdata seem to match the conclusion of the 1956 study mentioned in this article: That it was the intentional practice that primarily resulted in the improvements, not the keyboard layout; intentional practice on QWERTY would probably yield similar speed improvements to practice on Colemak or Dvorak.
I've had a similar history, and also switched mostly to reduce fatigue & the risk of RSI. Colemak seems easier to use, even if it's not any faster. Of course it's quite possible that the improvement is simply due to the deliberate practice needed to switch layouts; even more than learning to type in the first place switching layouts takes focus and therefore makes it easier to notice & correct bad habits.
I've seen a number of ESP32 IoT devices here on HN, and I haven't heard many of them use firmware encryption with an eFuse.
In this case, it would have been pretty hard to create a certificate if you couldn't read the firmware.
But, also pretty impressed at the same time. I think this is the first Hacker News article I've read about an ESP32 IoT device which has any encryption at all.
Even if they use firmware encryption, the footprint for most of the ESP32 packages is really easy to desolder and replace with a fresh one under your control with basic tools. This option is harder if the ESP32 is speaking some digital protocols to various devices, but having re-brained another air purifier myself they often are just flipping some GPIO lines to signal different components to turn on. Easy in that case to just stare at it for a bit then re-flash or replace and re-flash the ESP32 with your own firmware.
He talks about it in one of his videos. The zip directory was a product of a side hustle of his, which Microsoft then bought out. In the video he comments how much easier it was to integrate when he had access to more internal apis.
I use iwd and systemd-networkd. I don't use may applet or gui control. With my setup I just and up ignoring network configuration the majority of the time.
Edit: I've found iwd such a huge improvement over past wireless networking solutions. It's a big improvement.
I've used Roam Research for note taking for the last year. Before that, I spent two months trying out a dozen competitors. Using it the last year has been amazing for me. I definitely can't go without it now.
I've been using Duply as a simple CLI front end to Duplicity (not Duplicati) for years now. It's worked great for me on many servers and personal machines.
I've never experienced sluggishness, but, I also keep track of how much memory it's using and ensure I don't run low. It's clearly a huge resource hog, but I'm also glad for that. It's using all of my computers resources to analyze the code in amazing ways which help me develop fast. Emacs, Sublime Text, and others were all about typing speed. Fast development goes far beyond just typing speed.