The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Is that why Linux is preferred over Windows for supercomputers?
Or for large HA clusters?
Or small clusters?
Or high-resource workstations?
Or credit-card terminals?
Or car on-board computers?
Or car infotainment systems?
Or industrial control systems?
Or IoT devices?
For the desktop, Windows is ubiquituous. Outside of that single, narrow space Linux has been chosen time and time again by industry over Windows offerings.
Now, I've written software for Supercomputing clusters, for HA clusters, for phones, credit-card terminals, Industrial systems, IoT devices, factories, and even munitions control systems, and all of those systems run Linux, not Windows.
On the desktop, the OS is allowed to be unreliable so Windows is great! When the software is controlling explosives, any failure mode is unacceptable and so Windows is very rarely seen.
Now I'm glad that Windows works for you, and you seem to quite like it, but in pure numbers alone the number of Windows installations is a fraction of the number of Linux systems out there. Android (running on Linux, natch) alone has roughly twice as many users as MS Windows globally.
Once Windows hits the numbers that Linux has, then we can actually compare them - now there is no point because Windows usage is so tiny compared to Linux usage.
No. It was the reply to the Linux fans here (see influencer) who bashed Microsoft on every occasion to be slow to deliver code. Also they were early adopters, instantly downloading and installing every "fix" and "feature" they were provided by by their favorite distro.
So, the rest got forced updates, constant change of UI and else to satisfy these influencers.
But, since Linux is religion, with first commandment "Linux is better than Windows, at any given moment", Microsoft achieved nothing, and the rest of the world swallows.
With nearly 14 million of us, Code Project members could put in a lot of complaints if we wanted to. The trick would be to organise the plan of ...um, I hesitate to use the word "attack" as this is not what I want to propose.
Oh please do not be so scared!
That can be called much more suitable than the bad word! It's not an attack!
As a matter of principle, it would only be one thing: "Democratic expression with an organized media protest".
Something about which we often break our head:
"In the name of the Compiler, the Stack, and the Bug-Free Code. Amen."
Microsoft only listens to complaints when enough people complain about the same thing.
Which is true for most companies. You have to prioritize.
People complain so much about Microsoft but I don't see how they are any different than any other company of any product. Oh, except for the fact that they make it easier than anyone else to develop their products and make them better, creating millions of great careers in this world.
Y'all are doing something wrong. Every other version of Windows is terrible but then they get it fixed by the next version. Other than that, all of their software works perfectly for me. I don't know what you all are doing.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
Apparently that's what's been holding the internet together for the last thirty years. Let me explain;
I am currently working on a closed source DHCP client and server. A perfect implementation of RFC 951, RFC 1534, RFC 1542, RFC 2131, RFC 2132 and RFC 3046. The source code was very elegant and I was quite pleased. Verified and tested it against DNSMASQ, ISC DHCP and various other servers and clients. Everything works as expected!
I decided to test against older DHCP clients and servers... that's when I realized that for the last 25 years nobody even completely understood the DHCP protocol. Nearly 100% of the DHCP servers I am testing have bugs.
Older versions of Windows Server with a default install will send just the IP address and lease time. No T1 or T2 values which violates the RFC. It also does weird things like NULL terminate it's strings and identifiers. It also sends some of the DHCP values in the wrong network byte order. I'm finding some other DHCP implementations that implement broadcast/unicast incorrectly and ignore the flags. Some DHCP servers just SPAM the network with gratuitous DHCPINFORM messages.
In fact...excluding software written in the last five years... I can't seem to find any DHCP servers in the past 25 years that does NOT have any bugs.
My once beautiful code now has to check for wrong network byte order, NULL terminated strings, missing DHCP options, missing T1 T2 time values and various other weirdness.
You probably thought these old RFC written 30 years ago have been perfected. You were wrong.