If there's one thing the government is known for, it's writing bug-free, efficient software.
Also, for real, this bug is not that bad. It's obviously a bug you'd rather not have. But no user data is lost. It just fails to surface an overwrite dialogue, and assumes the result is no.
I know you're saying this in jest, but the (US) government wrote code to fly to the moon and back, control robots on Mars, and model the earth (e.g. DoD's WGS 84, all the work by NIST, etc.). Sure, healthcare.gov was not a smooth rollout, but they do deserve some credit overall.
Now Windows on the other hand.... I just set up Windows on a new laptop I bought recently.. just plain Windows as it shipped with my new laptop. Didn't do anything "outside the box" here. I've let it update after this fiasco was supposedly over, restarted - and, of course - can't boot, everything's corrupted, had to reinstall Windows from scratch. Never had this happen with macOS, FreeBSD, or Linux.
It's hard to believe, but it really is _that_ bad. I wish it wasn't!
Never happened to me with Windows. It's not the best, but works.
Linux on the over hand it's a continuous installation of drivers and fixing functionality that works out of the box on my windows: graphics problems, audio, screen, usb, WiFi.
Of course and then you try to install some module and says you have incompatible modules. Then you need to figure out what modules you need to change to match the version of the module to install. This was a few years ago, but I don't have the time to do this.
Plus window management is broken on Linux, too many bugs. Last time I couldn't even alt tab like windows.
You don't appreciate the difference between knowing what's happening to your system well enough to fix it and hoping that an "update" doesn't cause too much unrecoverable damage when it installs itself behind your back.
Working out of the box is nice, but what's magically fixed can be magically broken just as easily. Traditional Linux was more work to get working, but once I got it working I could rely on it to stay working rather than getting broken in the next update. (Linux is no different from windows these days, so I've moved to FreeBSD).
I find windows more problematic, because of the unpredictability. FreeBSD experience: spend a day or two setting it up, but after that you can rely on it always working. Windows experience: it works the first time, but every few months it will have an update that breaks things for a bit.
I tried switching to Linux again for desktop usage since Proton became a thing and I was tired of the weird new licensing model. Installed the new Ubuntu 18.04 LTS and after fiddling around for a week I still couldn't get my sound cards to work properly. The sound quality is just bad and the sound often cuts.
Honestly if I had a little willpower I think I might have been able to get a satisfying result at some point but the effort just wasn't worth it for me. I use my home computer like 3-4hrs a week in the weekend for games and maybe hobby projects if I don't feel like dying. I'd rather just have something that plainly works in a predictable manner, but even that seems to be asking too much nowadays...
> If there's one thing the government is known for, it's writing bug-free, efficient software.
That's because they're usually required to accept the lowest reasonable bid. As someone who works in the public sector, trust me, we try to get the money to people we know will do a good job. We have to work with the shit we buy every day. We want it to be good. There's just a lot of people willing to put in maximum of effort on a bid and minimal effort on execution.
> Also, for real, this bug is not that bad. It's obviously a bug you'd rather not have. But no user data is lost.
I mean, kind of. I agree it's not as bad as the article implies. However, it's a pretty common pattern to download a zip file, extract and overwrite, and then throw out the zip file. It's not directly resulting in data loss, but a very common user pattern will result in data loss when you encounter this bug.
As someone who had to deal with them from both sides, EU public procurement laws are fucked up beyond repair. There is, however, a simple cure for software that the public sector is avoiding in most places:
1. base the software on an established, battle-tested open source product, there is one for almost any business case
2. use the money to hire an in-house team, hiring norms in public sector at least ALLOW for quality selection, unlike public procurement ones
3. develop in the open, invest into visibility, attract community members
4. shill, try to get as many agencies across your and other member states to pick the same solution and co-develop the software with you, this way the cost drops for everyone
Even if you can't find something to satisfy point 1., the other three points would still work to your benefit. If you can push this for long enough to make the software standard in more places, you could get a critical mass of outside developers to form consultancies you could hire later for additional work.
I know Munich is poster-boy of this not working for desktop OS-es but that's really a consequence of two things:
1. They made all the wrong choices (heavy customization, chasing windows look and feel, not tracking upstream progress)
2. They got elected officials who were effectively Microsoft shills (the top-down decision to go back to Windows was heavily pushed by a single executive who was pissed off he couldn't use Outlook he was used to on his previous drone job).
Turns out they often need to tender as fast as possible and just use "lowest price satisfying all other criteria" as a way of choice.
> Turns out it is very easy to be 50% cheaper than anybody else if you are not required to have a working product.
You are allowed to specify absolute requirements in addition to sorting criteria. For example, you can say, worth more than some price, "the contractor shall have at least n years of experience". As descendant says, these are used to work around ban of subjective selection. Sometimes, they overdo it, and no vendors qualify at all.
> You are allowed to specify absolute requirements in addition to sorting criteria. For example, you can say, worth more than some price, "the contractor shall have at least n years of experiene".
Exactly these are being used to pick a specific vendor. "Must have at least N people certified to do X for at least Y years", with "must have turnover of X for the last Y years" and few more, and you find out, that there is exactly one company qualifying.
There is no fast when talking abou tenders. You need to give at least 6 months by law to give companies a chance to respond. If they start asking basic questions, they get extra time to read each others answer. 9 months to 1 year seems a reasonable guess for a not to big tender
If there's one thing the government is known for, it's writing bug-free, efficient software.
Also, for real, this bug is not that bad. It's obviously a bug you'd rather not have. But no user data is lost. It just fails to surface an overwrite dialogue, and assumes the result is no.