When is an ad an advertisement and not a recommendation? Microsoft clearly likes to use the term recommendation for what others may see as an advertisement.
There are recommendations in the Start menu, Settings app, Lock screen, File Explorer, Get Help app, and other areas of the operating system already. These are often not that useful. App recommendations in the Start menu are limited to Microsoft Store apps.
Now, Microsoft is testing recommendations in the Microsoft Store app. If you never use the app, you won’t be exposed to these. If you do, you may notice recommendations popping up when you try to use the built-in search.
First spotted by phantomofearth on X, two or three recommendations are shown whenever search is activated in the official Microsoft Store app.
Installing Linux has never been particularly difficult, not in the last 15 or even 20 years anyway. I’ve always found it easier and more straightforward than the contemporary Windows installation process.
The challenging part is wrapping your head around the Linux/Unix way of doing things when things can’t be done through the GUI with just a few clicks.
I think about this sometimes. What stuff can’t you do in a Linux GUI that an average person would be able to do in Windows? For the sake the simplicity, lets limit the GUI to Cinnamon, Plasma, or Gnome.
Obviously, there are obscure GUIs out there, but in the main ones, I think just about everything can be done without CLI.
I’d amend that to say I wouldn’t count “regedit” or group policy muck to be “easy” by virtue of having “a gui”. Those are areas where technically there’s GUI that might be CLI-only under Linux, but hardly friendly enough to make a difference.
Regedit is about 10,000 times more complicated than Windows users think the Linux terminal is
I know the filesystem is simple to Linux users, but the semantic form of physical drives getting a letter always made more sense to me.
I have three drives in my computer. So they’re labeled C:, D:, and E:. You can’t place a file on “The Computer” - it’s stored on some particular drive. If I install a game on the E drive, and then later somehow remove that drive and bring it somewhere else, that game remains on that drive, even if it’s no longer E.
On Linux, as best I understand it, if I have three drives, two of them are at /dev/hdd0 and hdd1. But they’re not actually there, they’re accessed at /media/hdd0 after mounting them (or at least, that’s the convention, and if it’s someone else’s computer, good luck). Then you either begin every game installation path with that annoying prefix, or you start configuring a dozen symlinks. If you place an item in /home/documents/notporn, then who knows which drive it’s on because you don’t know what symlinks someone set up to make that folder.
Windows does have symlinks too now, which has been nice for hacking a few installation directories, but I appreciate that it’s an exception, and everything else follows relatively logical division of space, rather than this hybrid system where the filesystem isn’t just stored files but also devices, programming concepts, and more.
I know the filesystem is simple to Linux users, but the semantic form of physical drives getting a letter always made more sense to me.
That’s one of the things that semi-experienced Windows users need to wrap their head around, but I strongly disagree that drive letters are somehow inferior to a hierarchical file system structure. I mean, the A:, B:, C: … convention was originally just intended for the first IBM PC with 1 or 2 floppy drives. It was never intended to support complex storage configurations, whereas the hierarchical file system was designed for Unix systems that had to handle multiple magnetic drives from the start. It is a much more flexible system to organize your file storage.
On Linux, as best I understand it, if I have three drives, two of them are at /dev/hdd0 and hdd1. But they’re not actually there.
That’s because there is a difference between a block device and a mounted file system. Windows just obscures that difference from you with its archaic drive mapping system.
All your block devices and partitions on your block devices will be in /dev with a meaningful name. You can list them with the lsblk command. If a partition contains a file system that Linux knows how to use, you can mount it anywhere you like.
they’re accessed at /media/hdd0 after mounting them
No that’s not “convention” at all. Some desktop environments may decide to mount undefined drives there, but there really is no convention, ultimately you mount it where you want it to be mounted.
If you place an item in /home/documents/notporn, then who knows which drive it’s on because you don’t know what symlinks someone set up to make that folder.
If your unsure, df /home/documents/notporn should tell you exactly what drive it’s on, but ultimately it’s up to you to know how you’ve organized your storage.
BTW I’ve said this before, but Linux is probably harder for users who know Windows just well enough to be dangerous than it is for relative beginners, because there are so many concepts and things they take for granted that they have to unlearn.
While it might be suitable for server environments with 400+drives, all home setups will have fewer volumes than there are alphabet letters, so it’s a suitable setup there.
Someone else identified how you can run an extra command to identify actual location of a file, and while that’s useful, it’s an extra step that’s unnecessary when the design of the location string itself also identifies that. Unless you can tell me which drive /home/supra-app/preconfiguration/media is on - without running something different. (Vs windows: C:/Users/Someone/AppData/supra-app/preconfiguration/media) That’s what the design of WWW URLs was for - you never have to ask which domain a website is on, and it can even inform you about whether a site is trustworthy.
I don’t think you’re helping your case by showing there’s no drive location convention at all. A friend plugs a USB device in your computer while you’re busy in the kitchen. He’s fine if he just uses a UI autopopup, but if he needs the full path, he has to ask you where you’ve set up auto-mounting, if you have at all.
As an interesting fact, windows totally supports mounting positions to folders and as far as I recall it’s been able to for a very long time, remember doing it as a teenager and thinking it was cool AF.
https://learn.microsoft.com/en-us/windows-server/storage/disk-management/assign-a-mount-point-folder-path-to-a-drive And https://learn.microsoft.com/en-us/previous-versions/orphan-topics/ws.10/cc772671(v=ws.10)
So just to help a little bit without getting too technical…
df -h is your friend to find out which physical drive or partition relates to which directory (called the “mount point”)
If you want, you can set up each drive/partition to be mounted a bit Windows-esque.
For example:
- Drive 1, partition 1 will almost certainly be root
/ - But drive 1, partition 2 can be mounted to:
/mnt/d/ - And then drive 1, partition 3 can be mounted to:
/mnt/e/
And so on.
You’ll need to look up fstab to understand how to do that.
I understand it’s tricky to get your head around initially as I felt exactly the same coming from Windows to Linux.
Once you get your head around partitions being able to be mounted anywhere, it actually becomes really handy
