Yeah maybe like in 1995… If you’re having this kind of issue in the present day, you’d have to be shooting yourself in the foot very very intentionally. (An example is a broken custom Arch or Gentoo setup, which you shouldn’t be using anyway unless you know exactly what you’re doing.)
I’ve been regularly trying whatever Linux distro is supposed to be good on and off every other year, and there was always something that made me go ‘that should be working right out the box’ and then spend too much time fixing it.
If you’re not able to connect to a NAS for some reason, that’s almost definitely on you or your friend in this case. But even that aside, expecting a one to one transition has always felt odd to me… You don’t switch from an Android device to an iOS device or vice versa with the expectation of everything working one to one. You usually understand that there’s a lot of differences involved.
There’s ofc things like VR that I will admit Linux is quite far behind in, but for general use, Linux is problem-free for the most part these days. And you definitely don’t end up having an unbootable system pretty much ever unless you intentionally fuck it up. Like yeah, Linux lets me uninstall the kernel or bootloader if i choose to do that (it will try to warn me ofc) and that would render the system unbootable. But that would be me being irredeemably stupid, not the operating system’s fault. Hell, some distros like Tumbleweed even come with a better snapshotting setup than both Windows and macOS, making it pretty much impossible to fuck it up that badly.
this is the other thing linux communities are well-known for: blaming the user for not being good enough.
i think the last time my linux failed to boot there was a power outage…but the machine was a laptop. before that it was running an update (fedora/nobara). before that it was installing void (“installation complete” -> reboot ->grub recovery). before that it was running an update (pop_os). Before that it was running an update (manjaro, this was during a brief moment when it was very popular and linux folks claimed it was user friendly and suitable for moderate users). I’ve managed to recover from most of those cases listed above, but with the exception of manjaro that was 2023+2024 right there.
Sounds like a typical Linux user ;)
Yeah maybe like in 1995… If you’re having this kind of issue in the present day, you’d have to be shooting yourself in the foot very very intentionally. (An example is a broken custom Arch or Gentoo setup, which you shouldn’t be using anyway unless you know exactly what you’re doing.)
I’ve been regularly trying whatever Linux distro is supposed to be good on and off every other year, and there was always something that made me go ‘that should be working right out the box’ and then spend too much time fixing it.
So not just from 1995.
If you’re not able to connect to a NAS for some reason, that’s almost definitely on you or your friend in this case. But even that aside, expecting a one to one transition has always felt odd to me… You don’t switch from an Android device to an iOS device or vice versa with the expectation of everything working one to one. You usually understand that there’s a lot of differences involved.
There’s ofc things like VR that I will admit Linux is quite far behind in, but for general use, Linux is problem-free for the most part these days. And you definitely don’t end up having an unbootable system pretty much ever unless you intentionally fuck it up. Like yeah, Linux lets me uninstall the kernel or bootloader if i choose to do that (it will try to warn me ofc) and that would render the system unbootable. But that would be me being irredeemably stupid, not the operating system’s fault. Hell, some distros like Tumbleweed even come with a better snapshotting setup than both Windows and macOS, making it pretty much impossible to fuck it up that badly.
this is the other thing linux communities are well-known for: blaming the user for not being good enough.
i think the last time my linux failed to boot there was a power outage…but the machine was a laptop. before that it was running an update (fedora/nobara). before that it was installing void (“installation complete” -> reboot ->grub recovery). before that it was running an update (pop_os). Before that it was running an update (manjaro, this was during a brief moment when it was very popular and linux folks claimed it was user friendly and suitable for moderate users). I’ve managed to recover from most of those cases listed above, but with the exception of manjaro that was 2023+2024 right there.