It's super weird people are bitter about things that happened almost two decades ago. Much less there was no war. I think Ballmer said some mean words about Linux and Microsoft sued Lindows for infringement and won. After the rename to Linspire Microsoft actually worked with them on compatibility. The whole Windows v Linux "war" is completely contrived by some fans of Linux as some holy war.
That completely glosses over the actual behaviour of Microsoft, and ignoring the kinds of career, business, project, and reputational damage those tactics did.
MS’s attacks on open source, open formats, and free software impacted and still impact democracies, developing nations, general computing capabilities, and create vast market inefficiencies. Looking at it as pure tech misses the forest for the trees. The corruption of the Office OpenXml process alone is a daily pox on the developing world. The tax impact of those entanglements is recurrent, and frequently hurts education and healthcare.
Also: if someone got burnt by some industry jerks and have had to deal with the fallout for decades, “it was 20 years ago” completely misstates the problem. Some BS was started 20 years ago, sure, but with daily crap-bowls that needed to be eaten every day in between. Entire careers have fallen into those cracks, armies of IT staff forced into suboptimal and broken workflows to satisfy decisions based on establishing and abusing monopolies.
Breaking a spine, even years and years ago, impacts the every day. Bitterness can be well deserved with an understanding of what was lost.
> As early as 2002, a court rejected Microsoft's claims, stating that Microsoft had used the term "windows" to describe graphical user interfaces before the product, Windows, was ever released, and the windowing technique had already been implemented by Xerox and Apple many years before.[4] Microsoft kept seeking retrial, but in February 2004, a judge rejected two of Microsoft's central claims.[5] The judge denied Microsoft's request for a preliminary injunction and raised "serious questions" about Microsoft's trademark. Microsoft feared a court may define "Windows" as generic and result in the loss of its status as a trademark.
> In July 2004, Microsoft offered to settle with Lindows.[6] As part of this licensing settlement, Microsoft paid an estimated US$20,000,000 (equivalent to $33,294,574 in 2024), and Lindows transferred the Lindows trademark to Microsoft and changed their name to Linspire.
> completely contrived by some fans of Linux
I mean there are absolutely some fanboy fantasies of grandeur here but I don't think it's the "fans of Linux" who are delusional mate.
There is a lot of middle management. I would include PMs in this. Salesforce does planning from Benioff down. Goals -> each report goals, etc. Planning based off goals - much horse trading. Planning from the lead/pm level - weekly - more horse trading. Reality was urgent stuff got taken care of. Literally over a two year period, outside fancy wording, the technical component of the initial goals maybe completed 30%.
There are a lot of inefficiencies I can see what this manager at AWS was trying to optimize for.
I think Steve's idea of an agent coordinator and the general model could make sense. There is a lot of discussion (and even work from Anthropic, OpenAI, etc) around multiagent workflows.
Is Gas Town the implementation? I'm not sure.
What is interesting is seeing how this paradigm can help improve one's workflow. There is still a lot of guidance and structuring of prompts / claude.md / whichever files that need to be carefully written.
If there is a push for the equivalent of helm charts and crds for gas town, then I will be concerned.
I ran into this building a similar workflow with LangGraph. The prompt engineering is definitely a pain, but the real bottleneck with the coordinator model turns out to be the compounding context costs. You end up passing the full state history back and forth, so you are paying for the same tokens repeatedly. Between that and the latency from serial round-trips, it becomes very hard to justify in production.
California is big, and the LA basin can be extremely dry. For me this is the most I’ve seen since the one bad el nino season in the 90’s, but that one didn’t last nearly as long. It seems normal the last few years to get winter storm conditions that last months.
2025 was the coolest summer I’ve ever experienced living where I do near the coast with an onshore breeze that is now frigid and very wet at times. I usually get fog now in times of the year it rarely happened - almost like san francisco’s notorious summers.
Tracking local weather patterns used to be part of my last career so this stuff I notice pretty well.
I'm split three ways on this:
- he is a Russian asset
- he has serious dementia and the power brokers around him are doing what they can
- or, similar to 2 minus the dementia, he's just trying to grift and enrich himself and friends
Waiting on my passport for an EU country (already have citizenship) to figure out options.
I’d say correct common path. OpenSSL due to hand waving deals with a lot of edge cases the correct path doesn’t handle. Even libraries like libnss suffers from this.
There are multiple overlapping specifications for things like X.509. There are the RFCs (3280 and 5280 are the "main" ones) which OpenSSL generally targets, while the Web PKI generally tries to conform to the CABF BRs (which are almost a perfect superset of RFC 5280).
RFC 5280 isn't huge, but it isn't small either. The CABF BRs are massive, and contain a lot of "policy" requirements that CAs can be dinged for violating at issuance time, but that validators (e.g. browsers) don't typically validate. So there's a lot of flexibility around what a validator should or shouldn't do.
The spec is often such a confused mess that even the people who wrote it are surprised by what it requires. One example was when someone on the PKIX list spent some time explaining to X.509 standards people what it was that their own standard required, which they had been unaware of until then.
I'm drawing a blank on it sorry, it's somewhere in an archive of messages but I can't find the appropriate search term to locate it. However it did turn up a reference to something else, namely this, https://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt. It hasn't been updated for a long time but it does document some of the crazy that's in those standards. The various Lovecraft references I think are quite appropriate.
Technically yes because I saved the messages, which I saw as a fine illustration of the state of the PKI standards mess. However I'd have to figure out which search term to use to locate them again ("X.509" probably won't cut it). I'll see what I can do.
reply