Yeah... https://www.sophiajt.com/case-for-nushell/ makes a really good case for Nushell as an alternative to Bash.

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.

I love Debian's stability, but I rely on Homebrew (instead of apt) to get more recent releases of software. Overall it works swimmingly!

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.

I'll bite. Why is it like this (in your opinion of course)?

Mostly the failing events (e.g. the Messages app failing to keep the first word of a message when typing rapidly after sending a message) are, I think, due to Apple using Catalyst for these apps.

Catalyst was an ambitious project, which works… mostly. But in the details, it has a lot of rough cuts. I fully expect Apple to end up rewriting Messages and co completely in SwiftUI eventually, but that will take many years, if they ever do it.

For the rest, most of the time my wild guess would be that Apple is constantly migrating their frameworks, or creating new ones, and the engineers developing apps are using ever moving frameworks. The framework stabilizes at the end of the release cycle (or sometimes even later…), which leaves no time for the front devs to truly finish quality control on their part.

Basically, to summarize, the release cycle is too small. Apple should do releases every two years instead of every year. Or drop the cycle altogether and just release when ready.

I agree, but I tend to find that "git diff aware syntax" also makes things simpler for humans as well

Do you have any favorite docs or blogs on these? Reading about one of the best designed permissions systems sounds like a fun way to spend an afternoon ;)

Looks neat! I highly recommend showcasing the interactivity with a few GIFs in your README. You can script them with https://github.com/charmbracelet/vhs

No

One language vs 3 or 4? And some folks REALLY like Rust

Yes (from the README)

Super impressive, can you link to this post in that issue?

I'd like to try iced, but switched to egui on the official Android support.