Author Topic: Microsoft teaming up with Qualcomm to bring windows10/x86 to arm  (Read 8597 times)

0 Members and 1 Guest are viewing this topic.

Offline hans

  • Super Contributor
  • ***
  • Posts: 1653
  • Country: nl
Re: Microsoft teaming up with Qualcomm to bring windows10/x86 to arm
« Reply #25 on: December 13, 2016, 12:11:19 pm »
Windows != Linux. Both systems have other mindsets.
If you're not accustomed to it, you will likely complain about Linux.
If you're accustomed to it, you will likely complain about Windows.

Ubuntu Linux has many drivers baked inside the kernel, also many non-free ones. I only had to switch drivers for my NVIDIA graphics card to proprietary.
Windows OTOH moans about unsigned USB drivers for my own fr'king hardware, even it's simple like CDC, keyboard or mouse. It's annoying enough in W7 - don't even start about W8 or W10.

I've never been able to screw up the dpkg manager out of the ordinary. Only on a hard shutdown or hard abort of the install process. Which is something you never do, neither on Windows.
Why should a reboot fix this? What is magical about a reboot process that should clear up the mistake that just happened? On Windows this seems like the magical fix because it was confused, on Linux it should just lead to the same state prior to reboot. This makes systems more predictable, but it does mean you should get it properly fixed.

I am more happy with Linux than Windows because applications start from the CLI and maybe work up to a GUI. Namely, you can access almost all of the systems and tools functionality from the CLI. This is awesome for headless servers and scripts. Ever seen a script for automating a GUI? It's a horror show.


There is a better substitute for regedit on Linux. It's called /etc/ with configuration files and a text editor. Crapped your settings? Just place back the .bak file and restart the service.

And my personal favorite of Linux: if you run rm / ; it will warn you do you really want to do that? Sure let's do that.. add --no-preserve root.
And so it complies. It removes all your files, including on mounted partitions like harddrives, network drives and the UEFI BIOS if you had that mounted.

That sounds retarded. But it's merely the lack of understanding what the command really does and can affect, than the command being retarded. The command did what it has been told. It's like calling the garbage company to come and clean all your belongings (including your wedding rings and family photo books) from your house. I'm sure they will comply if you tell them '--no-preserve-root' too.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 27169
  • Country: nl
    • NCT Developments
Re: Microsoft teaming up with Qualcomm to bring windows10/x86 to arm
« Reply #26 on: December 13, 2016, 12:48:39 pm »
And my personal favorite of Linux: if you run rm / ; it will warn you do you really want to do that? Sure let's do that.. add --no-preserve root.
I think I know why that is in there... About 2 decades ago an ISP I used to connect to internet was also very active in Linux development. At some point someone typed something like rm myname / (note the extra space!) which promptly deleted all files on the server which had all the homepages and ftp server.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf