yes, they have. It just costs a shit ton of money and is extremely difficult to get the suits to sign off on TWO full 'cloud services' bills. It generally doubles your cost and workload and increases your uptime by a couple hours/year, assuming you don't have bugs that affect one or the other cloud in your deployment stack.
It's basically a wash for almost all organizations for twice the cost and effort.
It's basically what leads to extended downtime almost every time. There are just some things in the stack that are still single points of failure, and when they fail it's a mess.
You might be counting out the value of government and military contracts that might not want to do business with a wild card.
SpaceX is killing it because the US government gives them a bunch of contracts, but if stability is slightly more important than cost or speed, amazon has a contender.
I’ve never heard the bring one or three, I’ve always just heard three. I think that exact saying implies that if you have two and one isn’t working out you’ll go crazy but if you have one you’ll be oblivious until it’s too late.
A well serviced rolex in 2026 with laser cut gears drifts +/- 15sec per day.
One with hand filed gears is going to be +/- a minute on a good day, and that’s what early navigation was using. I have watches with hand filed gears and they can be a bit rough.
Prior to that, it was dead reckoning, dragging a string every now and again to calculate speed and heading and the current and then guesstimating your location on a twice daily basis.
Those two wildly inaccurate systems mapped most of the world for us.
You can definitely average two relatively accurate chronometers but you if you only have two it’s difficult to tell if one is way fast or way slow.
In a perfect world they drift less than a minute per day and you’re relatively close to the time with an average or just by picking one and knowing that you don’t have massive time skew.
I believe this saying was first made about compasses which also had mechanical failures. Having three lets you know which one failed. The same goes for mechanical watches, which can fail in inconsistent ways, slow one day and fast the next is problematic the same goes for a compass that is wildly off, how do you know which one of the two is off?
I hope not because I’ve been doing my US taxes on Linux for 15 years.
It’s probably a specific windows desktop app, probably TurboTax by intuit, the company that lobbies to make filing your taxes hard and to destroy any free simple government app to file taxes.
So, not sure why they’d complain about not being able to help shoot their foot off but we all have preferences. :shrug:
My sister was the same, she brought her machine over, I booted a Ubuntu disk and did the disk config in the install and then she set the rest of the stuff up and I haven’t heard from her about it for 5 years, other than that I check if she’s still using it now and again.
If you do regulate. We currently have full regulatory capture in most industries and regulators that are doing their jobs are either hamstrung or the laws are so far behind the industries that they can’t or won’t work.
The key to proper regulation is to keep money and influence from pooling at the top, making it difficult for any single person to buy enough influence.
As it is, we have a dozen monopolies that should be broken up that are making a small section of the population so rich they are essentially above laws.
But, proper regulation can exist if people want it, and more specifically in the case of the USA, legislators want it. Unfortunately, Dems actively prevent it, and republicans are ripping it down, so the rest of us are kinda fucked.
Well, There's not going to be much because it would violate NDA, but, nothing is 'elastic'.
Somewhere, someone, has to buy a set amount of servers, based on a running capacity projection and build those into usable machines. The basis of a datacenter, is an inventory system, a dhcp server, a tftp server, and a DNS server that get used to manage the lifecycle of hardware servers. That's what everyone did at one point, and the best of them build themselves tooling.
What amazon has is built on what was available at the time both for tooling and existing systems that they'd have to integrate with. You almost certainly don't have to build anything that complex. Additionally, you can get an off the shelf DCIM that integrates with your DHCP and DNS servers and trigger ansible runners in your boot sequences that handle the lifecycle steps. It's considerably easier to do now than it was 15 years ago.
While they don't use AWS specifically for a lot of stuff, the internal tooling can still build thousands of boxes an hour though they don't really pay for UI work for that stuff.
You can put a host(s) in a fleet, tell it the various software sets you want installed and click go and you'll have a fleet when you come back, so don't think that what you're being asked to build is impossible or not being used under every single major cloud provider or VPS provider.
The slightly harder part is deciding what you're going to give to devs for a front end. Are you providing raw hosts, VMs, container fleets, all of it? how are you handling multi-zone or multi-region . . ., how are you billing or throttling resources between teams.
The beauty of this is you get a lot of stuff for free these days. You can build out a fleet, provide a few build scripts that can be pulled into some CI/CD pipeline in your code forge of choice and you don't really need to build a UI.
Provisioning tooling is hard, but it's a lot easier now that it was 15/20 years ago and all the parts are there. I've built it several times on very small teams. I would have loved to have 10 devs to build something like that, but the reality is that you can get 80% with a little glue code and a few open source servers.
They re-keyed it specifically so it could be nested, however, they mention the prefix key is intentionally dumb and ment to be remapped, probably to ^a like screen.
The difficulty here is that in the example above, it's unlikely, given any amount of scale, that the two people were on the same team. They were doing different things with the same data and probably didn't know what the other was doing.
Sure you could add a convention to your 'how to log' doc that specifies that all user input should be tagged with double '#' but who reads docs until things break? convention is a shitty way to make things work.
There's 100 ways that you could make this work correctly. Only restarting on a much more specific string, i.e. including the app name in the log line etc . . . but that's all just reducing the likely hood that you get burned.
I've also written a OOM-Killer.sh myself, I'm not above that, but it's one of those edge cases that's impossible to do correctly, which is why parsing and acting on log data generally considered and anti-pattern.
It's basically a wash for almost all organizations for twice the cost and effort.