Skip Navigation
71 comments
  • No. If everyone were on Linux and there was a breaking change introduced by a third-party there would be similar problems.

    The problem is that critical infrastructure isn't treated like critical infrastructure. If something you rely on can go down due to a single point of failure, maybe don't fucking use it?! Have backups, have systems that can replace those systems, have contingency! Slapping Windows on to a small machine and running some shitty Chromium app to work as a cash register is a fucking stupid idea when you consider that it is responsible for your whole income.

    The problem was never Windows. It was companies that were too cheap to have contingency, because an event like this was considered extraordinary and not worth investing in.

    • Nope, that's not how it works on Linux, even if someone introduced the most heinous breaking change people would just not update until things were fixed, in fact the update is unlikely to do that because things are tested before being pushed. If someone were using latest of everything by having something like a Gentoo system with everything building from git maybe that person would be affected and he would have to rollback to an earlier version and keep going for a total downtime of 1h tops, and that is if someone was using the most stupid way possible in production.

      The main reason why this will NEVER happen to a server running Linux is that updates are not automatic, i.e. they get triggered manually, so if there's an issue upstream you don't update, and if you encounter you rollback. The issue is not that Windows had a broken update, that can happen and it's fine, the issue is when the OS forcefully installs that update and breaks your system without you doing anything.

      And yeah, I know what I'm talking about, I worked as a software architect for a large website for a few years and now I work as a software engineer for the servers of one of the largest online games.

      Edit: re-reading your post, I would like to ask you how would you build this critical infrastructure with Windows? Because independently of how you answer it you would have been affected by this.

      • Windows updates don't happen automatically in an Enterprise environment. They are tested and pushed out once the version is determined to be stable.

      • That is a wild assumption with two key flaws

        1. Windows in many workplaces has updates locked down too, except in circumstances where critical security or vulnerability patches are pushed through.
        2. The same is true for many servers that run Linux.

        As someone that works on tier1 services for arguably the biggest tech company right now, that's how it works in most of FAANG. Updates are gated, sure, but like with many things there's a vetting process where some things that look super important and safe just slip through.

        In regards to your edit, I guess most cases are different from others, but if your entire business requires you to be able to use a machine 100% of the time then you should have the means to either use a different machine to continue transactions (ideally one with a known state that won't change, or has been tested in the last few months). If you need to log transactions and process 24-48 hours later do that on something that's locked down hard, with printed/hard backups if necessary.

        Ultimately, risk is always something you factor in. If you don't care about 48 hours of downtime over several years, it's not a huge concern. I'd probably argue that many companies lost more money during these days than they would have spent in both money and people-hours training them on a contingency system to use in case of downtime.

      • the issue is when the OS forcefully installs that update and breaks your system without you doing anything.

        The crowdstrike update was pushed out by their own software I thought, not the windows update system?

        Plus crowdstrike has caused similar issues with Linux systems before, so the solution is to just not use crowdstrike and similar solutions on any OS.

        The issue is not that Windows had a broken update, that can happen and it’s fine, the issue is when the OS forcefully installs that update and breaks your system without you doing anything.

        I would have thought most businesses with windows would do staged rollouts.

    • I mean this is sort of like what the new NIS2 Regulations tries to achieve. Make critical infrastructure producers and maintainers aware and force them to treat their infrastructure accordingly.

  • Wouldn’t it be wild if all government work was located in Microsoft’s M365 services? Like imagine all government data living on a SharePoint site on an E5 M365 tenant. Like if every single citizen processing service was a PowerApps application? Imagine what would happen if Microsoft had an outage or a hack?

    How easy would it be for a foreign adversary to take out a country by only focusing its attacks on a single company? Gosh what a hellscape that would be.

  • I don't like the implied false dichotomy between opening up the kernel and better security. You can definitely have both. Otherwise it's a good report.

  • "We", no. "Too many", yes. In general, hard dependencies on proprietary software or services are often overlooked or ignored as potential future problems. Recent examples of this are Microsoft and VMware. Once the vendor changes things so that you don't like anymore, or drives up prices like crazy, you'll quickly realize that you have a problem you can't solve other than switching, which you might not even be prepared to do short-term.

    The Windows world now experiences this because Microsoft is no longer interested in maintaining a somewhat quality operating system, they are mostly interested in milking their user base for data, and don't hesitate to annoy or even disrupt their user base's workflows in a try to achieve that goal.

    Many Windows users are currently looking at Linux because of this, but the more your whole workflow is based on dependencies to proprietary Windows-only software, the harder your time to switch will be. If you still use Windows today, you should at least start using more open source or cross platform software, which also will work on Linux, because you are on a sinking ship and there will probably be a time when you can't take MS' BS anymore and want to switch. Make it easier for you in the future by regarding Linux compatibility in the hard- and software you use today.

    • I think VMware is actually a good example of in house control. If AWS raised prices everyone would be (and is) trapped. With VMware there are tools that make migration easy.

  • I deal with whole I.T support companies built on the Microsoft partnership platform. All their dev is c#, servers are windows, no concept of other os when it comes to support. It's a real basket of ms eggs situation.

  •  undefined
        
    while True:
            print("yes") 
    
      

    Cant use tab as I'm on a phone

    • yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

      yes

  • Nah, I'd be completely fine if M$ went bankrupt and stopped developing Winblows altogether.

71 comments