WinGet, choco, scoop, &c, they all have strengths and weaknesses, which is why I had to write this: https://github.com/brianary/scripts/blob/main/Update-Everything.ps1
It’s also why I use Linux at home.
WinGet, choco, scoop, &c, they all have strengths and weaknesses, which is why I had to write this: https://github.com/brianary/scripts/blob/main/Update-Everything.ps1
It’s also why I use Linux at home.
I really like the tiling window support in Pop_OS!'s Cosmos desktop.
As I’ve said elsewhere: I wonder what controls Mozilla has in place to prevent gradual takeover of their board by those with an interest in removing Firefox as a competitor. We’ve watched the sleeper cell in the Supreme Court transform that body into an illegitimate partisan puppet. Mozilla’s actions over the last few years would make much more sense if it were being manipulated into self destruction.
19½ months. That’s how long Mozilla was prepared to listen to a small, unfiltered subset of their users, for a laughably meager maintenance cost.
Yep, which further highlights the problem: @mozilla@mozilla.social 🔗 https://mozilla.social/users/mozilla/statuses/113153943609185249
We’ve made the hard decision to end our experiment with Mozilla.social and will shut down the Mastodon instance on December 17, 2024. Thank you for being part of the Mozilla.social community and providing feedback during our closed beta. You can continue to use Mozilla.social until December 17. Before that date, you can download your data here (https://mozilla.social/settings/export), and migrate your account to another instance following these instructions (https://support.mozilla.org/en-US/kb/mozilla-social-faq).
This was also my recent experience on PopOs!
There’s a little historical baggage, but look at Windows: multiple letters for drives, and all of the paths can be modified, so you have to ask Windows where any important directory is physically mapped (like SystemRoot or Documents or Temp or Roaming AppData or many others), because it doesn’t have this nice consistent structure like Linux. Linux presents a logical layer and manages the physical location automatically. Windows makes you do the logical lookup yourself, but doesn’t enforce it, so inexperienced programmers make assumptions and put stuff where the path usually is.
That’s part of why logging in to Windows over a slow connection can take forever if you have a bunch of Electron apps installed: they’ve mismapped their temp/cache directory under the Roaming AppData, so it gets synched at every login, often GiB of data, and they refuse to fix it.
That and .NET’s CLR, i think.
Windows increasingly allows either slash for paths.
Press WinKey+Ctrl+D, then WinKey+Ctrl+(←or→). Windows already has multiple desktops.
That all sounds good to me. Good clarification.
I was with you right up until the unique passwords. I do use a different randomly generated password for each site.
I guess I feel somewhat safer as relatively anonymous target of spearphishing as I have been for 20 years without incident, instead of as part of a much more valuable collective target, even though that data is probably better protected.
Historically, I’ve seen more “proper” password managers with breaches than browser storage.
I guess you’re completely right if you just assume your own conclusion.
So do feature testing, not user-agent sniffing! For Pete’s sake, it’s 2024! That’s been the best practice for decades!
Annie Linux, but sadly it doesn’t exist yet.
The NexDock works, too.