0x4E4F

joined 9 months ago
[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago

And that is why I use fish. Well, one of the many reasons, lol ๐Ÿ˜‚.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago

My guess is, they had to run it in parallel. So many things relied on the old UI, not to mention run/cmd commands (printui, netplwiz to name a few), that simply just putting modern replacements for those things would have broken every single printer share, user credentials manager, etc., there is out there. So, they decided to run them in parallel. Smart choice if you ask me, since they own most of the desktop market share, if they decided to make a 180 turn on this, that would have cut a significant portion of their user market share... not to mention companies that heavily rely on MS products being pissed AF.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago

They were transitioning to the new Metro look, that's why the 10 different places for the same setting.

And seeing how slowly Control Panel is being transitioned to the new Metro Settings app, I'd have to guess that that thing is so deeply intertwined in the OS and so many things rely on it, that moving to something new is painfully slow.

[โ€“] 0x4E4F@lemmy.dbzer0.com 2 points 8 months ago

Actually, Linux in general, not just Ubuntu. You could even update the app while running said app (like your browser). It won't crash, you just have to restart it in order to use the new version. You could literally be running every single app that the update updates and it won't crash. Once loaded in RAM, there is nothing tying it to the place where it resides on disk. You could even delete the binary if you'd like, it would still keep running... unless you close it, then you won't be able to run it again, lol ๐Ÿ˜‚. There are a few exceptions though, like services (daemons), but that is only in systemd land, other init/service managers will allow you to just restart the service and load the new updated version of it.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago (3 children)

Keeping a Pro or a Home install up to date is not always a good thing. From a security standpoint, yes, I do agree, but when half your personal files go missing after an update... you kinda start wondering why you let this thing update automatically in the first place.

LTSC editions though, yes. I leave them to autoupdate. They do it like once a month anyway, so it's not that big of a deal anyway, it's not really such a big problem. And the updates don't take that long, no new features are added, just security updates and that's it.

So, if you're worried about security and being up to date, I'd recommend the Windows LTSC editions. That is the only thing I ever install if I have to install Windows.

[โ€“] 0x4E4F@lemmy.dbzer0.com 2 points 8 months ago* (last edited 8 months ago)

Well, Steve did tell them they have a gold mine with the mouse thing and other innovative solutions they had going... they didn't listen ๐Ÿคท... a bunch of hippies doing weird things according to management, a waste of time and resources. Oh well, we're just gonna take your ideas, thank you very much ๐Ÿคท.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago* (last edited 8 months ago)

Shit happens ๐Ÿคท. It happens to milti-billion dollar companies as well, like MS. In fact, it happens a lot more frequently (and it's more destructive) than it does with Linux or any other POSIX based OS. I have yet to see an update deleting all my personal files in /home.

Troubleshooting problems is about the same IMO, if you're familiar with the OS and how things work (in general). You just use the terminal more in Linux, since you'd have to open the file manager as root in order to troubleshoot, and that brings a whole other set of issues, like file permissions if you happen to copy a file to, let's say /home/<username>/Desktop temporarily, for troubleshooting. Ah, but now the file has root permissions, not the permissions your user has, and root is the owner of the file, so basically, your user only has read permissions, that's it. You can't move or delete the file. In order to move it or delete it, with a GUI, you'd have to open up the file manager as root again and do it from there. And that is why using the terminal to accomplish these things is so much simpler. You just add sudo in front and that's it, the command will do whatever root could do. And then you realize that just copying and renaming the file to filename.bak in the same location where the file originally resides is so much quicker and better. You can delete or move the file just by adding sudo in front of the command, no file manager needed.

So yeah, troubleshooting is more or less the same IMO.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago* (last edited 8 months ago)

What? People still do that ๐Ÿคจ? I mean... we used to do it when disk space was expensive, but come on, I live in a 3rd world country (not exactly, but it might as well be true) and even I can say that disk space nowadays is dirt cheap. I mean $25 for a 256GB (250, 240, whatever) SSD? That is dirt cheap.

And you can also do it in Linux, but you'll have to do it manually by symlinking, since the package manager won't allow you to install in other locations.

You can also use separate drives for home and the main install. You can define that in fstab by mounting the separate drive in /home which also kinda solves the problem with disk space, I guess. It's also a nice feature when you have to reinstall or try another distro, since all of your settings are already there, you just install everything you might need from the repo and that's it.

Almost every app that has a GUI makes a desktop entry in the applications menu. There are exceptions, but this is just bad packaging, and it's very rare to be honest. Besides, in those few cases you can make your own "shrotcut" (.desktop file) and place it in /usr/share/applications and it will show up in the applications menu.

It's just a getting used to thing. I know, because I have jumped ship. It's more or less the same thing, except you use the terminal more (cmd or PS in Windows), but some things are just easier done in the terminal then a GUI. Let's take the above example. You have an app that doesn't have an installer or the installer doesn't make Start menu entries. You'd have to make a shortcut and copy that shortcut to C:\ProgramData\Microsoft\Windows\StartMenu\Programs in order for it to show up in the start menu. It's more or less the same if you ask me ๐Ÿคท.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago* (last edited 8 months ago)

No, Windows 10 Enterprise LTSC. It's an official release, no debloating required. It's how Windows was like, before 10, it only receives security updates, no new features, it's stuck in time feature wise.

https://learn.microsoft.com/en-us/windows/whats-new/ltsc/overview

Google a bit for LTSC (it was LTSB for the 2016 release, Long-Term Servicing Branch, they changed the Branch part to Channel in the 2019 and 2021 releases).

Windows 11 Enterprise LTSC is coming this year. September, most probably.

[โ€“] 0x4E4F@lemmy.dbzer0.com 2 points 8 months ago

Based on what they did with Win10 and 11, not paranoia at all.

[โ€“] 0x4E4F@lemmy.dbzer0.com 1 points 8 months ago (2 children)

Choosing an install location is totally a Windows only thing. Every other OS has a notion of where binaries and libraries of applications are supposed to reside, except for Windows. This is why you can't invoke anything manually installed from cmd just by typing the name of the application and hitting tab for filename completion. You HAVE TO cd to where the file physically resides, THEN type the name of the binary. Couldn't be stupider if you ask me.

view more: โ€น prev next โ€บ