I think they rightly pointed out that US States construct is problematic esp in much more interconnected world.
However, I think fundamental problem still goes back to politics where Congress effectively does not do their job and thus fighting around executive and judicial leave us in worse place. Chevron and lack of it is mostly due to Congress just passing big stuff and then massive fights in courts when Congress could step in and be like "Nope, we are changing our mind, this is happening."
Congress moves too slow to be effective at thwarting off bad policy (largely written by lobbyists) until after it’s done its damage. By then, the senators that sponsored the bill quietly retire. Or they double down behind closed doors to be elected well into their geriatric years. I’m for term limits and age caps.
Lobbyists can't write bad policy unless it is passed by congress, so basically you are saying that congress doesn't move fast enough to stop congress. I'm also skeptical of this "but the lobbyists" argument and I can't think of a single major problem facing the country that can be reasonably blamed on them.
The constitution has been absurdly broken by a cult of partisan federal judges claiming to be textual, but then inventing an absurd canon of non-laws no one can reference:
* Unitary executive theory. Congress can't create a federal reserve, except for when the supreme court likes it.
* Major questions doctrine. Congress can't create an EPA and give it open ended authority to regulate its way to clean air
* Qualified immunity. Congress can't stop ICE agents from murdering people
* Historical tradition as regard to the 2nd amendment. Congress can't ban everyone from walking around with military assault weapons.
I agree that partisan federal judges have caused this but my point is, Congress makes it worse.
Unitary is just wrong and Congress could continue to push back against it.
Major Question keeps coming up Congress does not step in after passing of EPA. Major EPA cases are like "Well, does this mean what we think it means because some comma somewhere" and Congress could step in and say "No, we really meant this."
Qualified Immunity is again something else Congress could step in on and say "Nope, we are eliminating qualified immunity or tailoring it back."
2nd Amendment is third rail I don't wish to touch.
The problem is the inflexibility of the constitution. If judges hadn't made the conscious decisions to turn the constitution into whatever they feel like, you'd be stuck in an even worse system of obsolete 18th century government.
This; the “originalists” who dress up in wigs and shock of shocks, just so happen to rule contrary to the way things have worked for the last 50 years.
I would argue states are ideal in an era of social media-triggered political fragmentation. People can move to the state which aligns best with their preferred policies.
Kubernetes Ops person here who opens HeadLamp at start of the day and leaves it open. Lens is much better than HeadLamp IMO but if you are cost sensitive, HeadLamp can probably get you 95% there.
Or when working on massive infrastructure like this, you write plenty of tests that would have saved you a month worth of work.
They write reordering, push it and glibc tester fires, fails and you quickly discover "Crap, tests are failing and dependency (glibc) doesn't work way I thought it would."
With glibc falling over but systemd-resolved working as intended, I suspect their Linux tests may have accidentally passed. Most desktop Linux installs and a whole lot of cloud Linux installs would've accidentally been saved from glibc's bug by systemd-resolved.
Checks the bio Ahh, Zero Sysadmin experience so does not know about amount of legacy garbage being run at many companies and Enterprises.
Amount of software running on .Net Framework is mind boggling. If there is not 100% compatibility with .Net Framework on Windows running on Linux, forget it. I know of a company still using Visual FoxPro in 2020 and it was still being maintained.
Just like COBOL, across insane amount of businesses/enterprises/government, there are hordes of Windows machines, using technology that last saw updates in early 2000 computing away. Their last supported Windows Server was probably 2008 but somehow they still run on Windows Server 2019 and those licenses are not cheap.
Sure, Windows Desktop is clearly becoming "Whatever" by Microsoft but it's also pretty cheap. NT Kernel and UI work has to be done for server side and until that cash cow is dead, shoving slop into Windows Desktop is cheap revenue stream on work they have to do anyways.
Some .Net Framework might be fine but unless it promises 100% all .Net calls, including ones using "unsupported APIs" or other insane stuff, works, there will be plenty of very unhappy Windows customers.
It's complicated... there's Windows .net apps (which run in wine through mono), there's Linux .net apps (that get run with dotnet), and there's apps that have to be run through mono directly.
IIUC, Microsoft bought-out Mono and donated it to Wine, making it effectively legacy. It probably still 'works', but not many big IT departments are going to run critical apps on some old unsupported hackjob.
Just like IBM, they are big enough that no one ever got fired for buying them.
I've also found they do a good job of getting cadre of executives that float between companies hiring them when they move between companies while they get wined and dined.
Any business that needs convincing to move on from anything labeled NTLM does not care what "nerds" have to say. They are either one of those "I'm not spending money on something that works" or stuck with such legacy technical debt that at this point, removing it from environment is too costly to even consider so executives kick it down the road.
Or it’ll be like a conversation I had yesterday, where the “Active Directory guy” who’s been in the job for 20 years doesn’t even know that there’s an NTLMv1 and an an NTLMv2.
As Ops (DevOps/Sysadmin/SREish) person here, excellent article.
However, as always, the problem is more political than technical and those are hardest problems to solve and another service with more cost IMO won't solve it. However, there is plenty of money to be made in attempting to solve it so go get that bag. :)
At end of day, it's back to DevOps mentality and it's never caught on at most companies. Devs don't care, Project Manager wants us to stop block feature velocity and we are not properly staffed since we are "massive wasteful cost center".
100% accurate. It is very much political. I'd also add that the problem is perpetuated by a disconnection between engineers who produce the data and those who are responsible for paying for it. This is somewhat intentional and exploited by vendors.
Tero doesn't just tell you how much is waste. It breaks down exactly what's wrong, attributes it to each service, and makes it possible for teams to finally own their data quality (and cost).
One thing I'm hoping catches on: now that we can put a number on waste, it can become an SLO, just like any other metric teams are responsible for. Data quality becomes something that heals itself.
You'd be shocked how much obviously-safe waste (redundant attributes, health checks, debug logs left in production) accounts for before you even get to the nuanced stuff.
But think about this: if you had a service that was too expensive and you wanted to optimize the data, who would you ask? Probably the engineer who wrote the code, added the instrumentation, or whoever understands the service best. There's reasoning going on in their mind: failure scenarios, critical observability points, where the service sits in the dependency graph, what actually helps debug a 3am incident.
That reasoning can be captured. That's what I'm most excited about with Tero. Waste is just the most fundamental way to prove it. Each time someone tells us what's waste or not, the understanding gets stronger. Over time, Tero uses that same understanding to help engineers root cause, understand their systems, and more.
What I am asking is, what are the other concerns other than literally the cost? I have interest in this area and I am seeing everyone saying that observability companies are overcharging their consumers.
We're currently discussing the cost of _storage_, and you can bet the providers already are deduplicating it. You just don't get those savings - they get increased margins.
I'm not going to quote the article or other threads here to you about why reducing storage just for the sake of cost isn't the answer.
The first step to solving this is correct cost attribution. And then once you do that, it's easy to go to org leads and tell them that their logs are costing them $X and you can save them 40% by applying these suggestions. They'll be happy to accept your help at that point. But if the costs are all on the Ops team, then why would the product teams care about any cost optimizations which just takes away development time from them.
>The voices that are silent are the ones that are shouting from the rooftops when Israel does this to Palestinians.
Depends on the protester and what they are protesting but many of Israel protests have been against US continuing to support/fund Israel and want US government to do something different.
Iran on other hand is US sanctioned and US actively works against it, very different relationship then with Israel.
reply