acac10

Q: How to properly grill a steak? A: I'm vegetarian; do not eat meat. Completely irrelevant for the question asked. But I do feel the need to express how superior I feel about it.

Pretty significant for hijacking protection in Windows.

Pretty significant for hijacking protection.

You say that until it happens to your mother/father/bf/gf/grandparent/…

Then we will see how you will react.

End User Credentials ? Everyone Uses Cars ? Engineered Universal Conscience? (Since you seem to assume we all share your thoughts & context...)

Dupe of this: https://news.ycombinator.com/item?id=45262858

passkeys started popping up the endgame became clear.

This logical leap puzzles me, as it is completely unrelated to HW lock-in and a rather generic medium.

This is more of a case of OP diverting a topic to shove in his pet peeve on technology they don’t like or understand.

Which many DBs allow: - stored procedures - Oracle PL/SQL

I used to work for Oracle but never liked that approach.

They always have been.

Falklands vs Malvinas, Bodensee vs Lake Konstanz, Lake Geneva vs Lac Léman, countless islands in South China, Sea (Philippines vs Chinese names), Japan vs Korean island names, Chine vs Russian names

and on and on.

Only uninformed people are surprised by this.

How is this equivalent?!? In fact, stronger seller identification is what makes the site safer for everyone. I think you're really missing the point of stronger identification on commercial sites. It should be done for sellers AND buyers alike. It would drastically decrease the number of bad transactions if people knew they were no longer shielded by anonymity.

// Taking another slant at the discussion: Why kubernetes?

Thank you for sharing your experience. I also have my 3 personal servers with Hetzner, plus a couple VM instances in Scaleways (French outfit).

Disclaimer: I’m a Googler, was SRE for ~10 years for GMail, identity, social, apps (gsuites nowadays) and more, managed hundreds of jobs in Borg, one of the 3 founders of the current dev+devops internal platform (and I focused on the releases,prod,capacity side of the platform), dabbled in K8s on my personal time. My opinions, not Google’s.

So, my question is: given the significant complexity that K8s brings (I don’t think anyone disputes this) why are people using it outside medium-large environments? There are simpler and yet flexible & effective job schedulers that are way easier to manage. Nomad is an example.

Unless you have a LOT of machines to manage, with many jobs (I’d say +250) to manage, K8s complexity, brittleness and overhead are not justifiable, IMO.

The emergence of tools like Terraform and the many other management layers in top of K8s that try to make it easier but just introduce more complexity and their own abstractions are in itself a sign of that inherent complexity.

I would say that only a few companies in the world need that level of complexity. And then they will need it, for sure. But, for most is like buying a Formula 1 to commute in a city.

One other aspect that I also noticed is that technical teams tend to carry on the mess they had in their previous “legacy” environment and just replicate in K8s, instead of trying to do an architectural design of the whole system needs. And K8s model enables that kind of mess: a “bucket of things”.

Those two things combined, mean that nowadays every company has soaring cloud costs, are running things they know nothing about but are afraid to touch in case of breaking something. And an outage is more career harming than a high bill that Finance will deal with it later, so why risk it, right? A whole new IT area has been coined now to deal with this: FinOps :facepalm:

I’m just puzzled by the whole situation, tbh.

The key to this is machine AND human readable formats. That is why the text format of protobufs is such a good approach: - structured formats - declared schema - the parser to read the file is also a validity checker (at least for data types)

There are tools that do similar with JSON but none are as simple and unobtrusive as protobuf tool chain.

When SOX compliance became a thing (remember Sarbannes-Oxley?), many moons ago, I was able to send EY consultants away during their audit for Unix controls, just by showing them that all our (Autodesk Unix team) configs were in SVN, logged, with authors and full change control. The Windows team had to spend months figuring out something that was not even remotely close to control or auditability. Frankly, I just assumed that it was the std practice today and I am surprised people are still not doing it.

I think the takeaway from your comment is that you really do not understand the sheer scale of volume of changes done by +100k engineers, their heavy reliance on tools that do cluster-based testing (not local dev machine) and the tens of thousands of tools that perform auto-commits.

It’s a lot easier to shit on a big corp. Intellectually lazy, too.