Jumping from loose-typed language to strict-typed language will be hard.
It’s also a matter of your general programming experience. Once you write, like, ten thousand lines of meaningful code in Python, learning C# should take you a month or two at most, you’ll know most programming concepts and algorithms intrinsically, and the rest is just learning syntax.
I think your videocard is about to die.
I have switched from XTerm to Konsole only a year ago.
Microsoft does not see Windows as a product since Ballmer left. It’s more of a liability, because you cannot sell it twice, and you cannot sell a Windows subscription. Windows still makes them just 10% profits, but selling cloud servers and office suite nets them 60% of their profits.
Microsoft IoT is not even a thing, the power of Linux IoT is that you strip everything from your kernel until your system runs on 32 MB RAM.
With any luck, Linux desktop will get the most installations wrapped as an Android app.
Good advice, but if you’re buying a new motherboard, why would you care for replacing it’s components? Choose the one that works properly out of the box.
Check for WiFi and Bluetooth drivers compatibility first. Every x86_64 motherboard should work with Linux well, as in, it will boot and all USB/PCI Express/SATA ports will work. What you should care are peripherals soldered onto the motherboard, like WiFi, Bluetooth, extra Ethernet ports, ten years ago I would say soundcards but nowadays all integrated soundcards are supported, some motherboards have strange ports like Firewire which might not be supported, integrated videocards are now soldered directly onto CPU and not on motherboards like before so HDMI ports should all work on any motherboard.
And yes, as the other commenter said, check that firmware update does not require some Windows program, and could be done only with USB drive and selecting some option in the BIOS/UEFI menu.
It’s because you now need to do
systemctl restart sshdinstead of/etc/init.d/sshd restart, I see no other reason than having to learn new syntax.Arguably, init.d scripts were easier to understand, and systemd is a bit of a black box, it somehow works, but who knows where it writes logs or saves the process pid (it’s all in the documentation somewhere), with init.d script you can just open the script itself and look.