Coming from Go, I'm really disappointed in Rust compiler times. I realize they're comparable to C++, and you can structure your crates to minimize compile times, but I don't care. I want instant compilation.
Zig is trying to get me instant compilation and I see that as a huge advantage for Zig (even past the first 2 weeks).
I'll probably stick with Rust as my "low level language" due to its safety, type system, maturity, library ecosystem, and career opportunities.
But I remain jealous of Zig's willingness to do extreme things to make compilation faster.
The key with C++ is to learn how to use the build system, make use of binary libraries, and if one can afford to use the very latest compiler versions, modules.
And avoid header libraries, C++ isn't a scripting language.
Homebrew really helps when you want to install more than one app... And you want to keep them updated... And you want to easily delete some of them at some point.
Managing the install lifecycle with one set of commands for multiple apps is why I love Homebrew
I've been amazed at AI's usefulness for Linux sysadmin tasks.
Last week I installed KDE on a new computer with two identical SSDs. One I wanted to wipe for the OS and the other I wanted to keep the data on.
Unfortunately I couldn't tell which one to install the OS on! ChatGPT helped me open a terminal and run the correct udevadm and lsblk commands to see what files existed on each disk.
Good use case and an example of brokenness of UX on Linux in many small and subtle ways. It frustrates me to no end that GNOME, Nautilus, etc. will truncate or hide information in many places. I don't think this has been fixed but the launcher will truncate names with ellipsis. So analyzer will appear as "anal..."
Yeah any time you're translating "user args" and "system state" to actions + execution and supporting a "dry run" preview it seems like you only really have two options: the "ad-hoc quick and dirty informal implementation", or the "let's actually separate the planning and assumption checking and state checking from the execution" design.
Unfortunately, I don't think Nushell brings much benefit for folks who already know Bash enough to change directories and launch executables and who already know Python enough to use more complicated data structures/control flow/IDE features
I'm still rooting for Nushell as I think its a really cool idea.
For me the blocker was having to switch to bash/powershell when moving to a different machine (ie: servers, work machine, etc..). I would end up needing to redo same things to be compatible with the existing tools; eventually I just gave up and got used to readily available shells instead.
For me it was the OneDrive ads on the lock screen. And, when I accidentally clicked "enable OneDrive" (a few years ago, this might have changed), IT TOOK OVER MY DOCUMENTS FOLDER AND TOLD ME THERE WAS NO WAY TO REVERT IT!
Yeah onedrive is seriously annoying. It's nice when the free 15GB backup/sync for the desktop, pictures, and documents folder works (for people who put things there) but the way other MS products work with it seems user-hostile to me.
e.g. it took until 2025 for this RFC to be opened on moving PowerShell profiles and modules out of Onedrive: https://github.com/PowerShell/PowerShell-RFC/pull/388. It should not be taking seconds for my powershell profile to load just because i have onedrive enabled by default.
I also had a non-technical friend recently get burned by a default MS Office setting where edited documents located in the OneDrive folder save directly to onedrive, and it only gets saved on disk when onedrive gets the new copy and uploads it back it to the user's disk. So if the MS office to onedrive integration fails your changes won't save. Apparently users have to enable a setting to first save to a folder on disk? That folder can even be the onedrive folder so onedrive will eventually sync it back up.
reply