Because Windows is also perfectly fine for running Windows applications & games. It can also be a royal pain in the arse to set up Windows emulation on Linux depending on your graphics card and some other factors.
It's actually easier to get Linux running on Windows since it has WSL. I have Ubuntu running under Windows with IntelliJ open at the moment and postgres running in the background right now.
Yes you can have a social discourse. What I mean is somebody took time to turn some disinfo in meme form and amplify it. This is inauthentic actors poisoning discussions with lies and division.
Europe certainly is. I should note that while most of their campaigns happen over on Twitter & Facebook that if federated social media ever took off in a big way it would happen there too and it might actually be harder to control if it did.
Well yes and obviously. Russia is a bad actor and obviously wants to sow division & doubt over the war in Ukraine, to sow division in general, and to slander political enemies. They have a special interest in interfering with US and European politics.
They're not the only bad actor of course. If you see memes & misinfo trend about immigration, Ukraine, drugs, vaccines, climate change, abortion, gas & oil, politics, NATO, EVs, MAGA, Palestine / Israel, dissidents etc. then invariably there is a bad actor driving that crap. They'll use their clusters of bots on Twitter to amplify the info until it gets picked up by useful idiots looking to retweet around.
It's time for news orgs and journalists to say a) "we're hosting our content on our own Mastodon server and that will be the source of truth for federated platforms (eventually including Threads and Bluesky)", b) "we will mirror the content across non-federated social media platforms that support free and fair reporting".
In other words give Twitter the middle finger and make the content available everywhere.
It's worse than that. The usual way of buying a company is a memorandum of understanding followed by due diligence, followed by signing a contract and then the actual completion. Elon went straight to signing the contract and then had big old shit fit when the Twitter board held him to the terms of the contract and the penalties for pulling out.
I wait for "try prime for 30 days" offers. I'll sign up for it, instantly cancel it to prevent recurring bills, and then order whatever it was I was thinking of over the last six months. Because once upon a time I'd be on Amazon all the time, browsing this and that, but it has become such a cesspool that I infrequently bother. If I wanted to wade through a sea of Chinese OEM crap and counterfeit products, then I might as well use Aliexpress and be done with it.
The job might be remote, doesn't mean the system is remote. For all you or I know they want somebody to reverse engineer the protocol of this thing, which could be some weird board & driver that hooks into an old PC so they can switch it out for something else.
Doesn't sound like this system is safety critical. You should be more worried if some hacker can change train signs from stop to go. If you ever ride on a train and see steel boxes by the side of the track, those are control systems and they run up and down the line. They might be locked, or possibly alarmed but that's about the extent of their protection. A simple attack would be to just take an axe to one, or set fire to it. A more sophisticated attack could snoop on the profinet traffic and do something evil.
They could socially engineer their way in regardless of some machine being MSDOS or not. Basically if they can gain physical access to the device, or convince somebody to do something with the device it hardly matters what it was running since it can still be compromised.
It really depends if these systems (that appear to control arrival boards) are on a network or not. If they're not, then there is minimal risk to leave them the way they are. Somebody would need physical access to the devices to do harm. If they are on a network then that's a pretty big deal, but some attacks could be mitigated against by tunnelling and/or additional packet filtering to ensure the integrity of messages.
Continuing on a railway theme you should be FAR more worried all the devices that run up and down the side of railway lines - PLCs that talk with each other and operations centres to control things like lights, junctions, crossings etc. If they're more than 5 years old then chances are then all that traffic is in the clear, and because these things live in boxes by the railway line, it wouldn't take much to break into a network and potentially kill people by running two trains into each other.
I wrote extensively in Ruby but for Rake - using Ruby as a build system. Can't say I liked the language although it was okay for how we used it. We have 20 sub projects with some very complex build targets and dependency scanning going on and the Rake syntax was okay. Personally I think its biggest shortcoming was the documentation was very poor and stuff like gems felt primitive compared to other package management systems. One thing I liked from the language was blocks could evaluate to a value which I really use a lot in Rust too.
I think if I were doing an acyclic dependency build system these days I'd use Gradle probably.
As for Rails I expect failed to catch on because even compared to Python, Ruby is a slow language. And Python isn't fast by any stretch. Projects that started with Rails hit the performance brick wall and moved to something else.