Oh. Em. Gee.
Is this a common take on Okta? The article and comments suggest...maybe? That is frightening considering how many customers depend on Okta and Auth0.
1,150 karma · joined May 30, 2014
Hands-on with Kubernetes, AWS, Linux, Python, and friends. Founded and run security programs, player-coach style. Fluent in engineer, executive, auditor, customer, and lawyer.
Ex-industry analyst: used to tell vendors how their platforms should work; now I find out in real time.
Building and running complex systems since before the Before Times. Now with AI agents, who frequently talk back.
Oh. Em. Gee.
Is this a common take on Okta? The article and comments suggest...maybe? That is frightening considering how many customers depend on Okta and Auth0.
This covers *so* much ground. It's utterly not predictive—but in retrospect, it often explains everything.
And then Sun would hit back: "Yeah, maybe a smidge better... Not saying it is, but maybe, in an ideal light. On the other hand, with Sun, we cost a lot less. That means you can get 3 or 4 of your engineers empowered with a world-class workstation for every engineer you could with <competitor>." Boom. Those economics were compelling.
It also helped that in those days, Sun workstations became the object of desire for a lot of young developers and engineers, myself included. Sun styled itself into the "it" product.
That was a full 40 years ago. And yet, 4th Edition is ancient history even to me.
You're also right to shout out out some of the other innovators: Data General's DG/UX did a great "let's redesign the kernel for multiprocessing and NUMA." IBM's AIX had kernel threads, pageability, and preemptibility at a time when no one else did (plus JFS, LVM, and eventually LPAR isolation). And Sequent DYNIX/ptx had some impressive multiprocessing (RCU) and large DBMS optimizations very early on. HP was by no means alone trying to engineer away Unix' early weaknesses.
For example, HP-UX was a BSD-based Unix implementation that tried very very hard to pretend it was UNIX System V (R2/R3). "No, no really! I'm not one of that university kids!" But BSD was a far better foundation, vastly better networking etc., so that's what it was underneath.
Unix of the era was billed as a multi-user shared system, but it wasn't always great at that. It desperately lacked much of the quiet robustness and workhorse-ness of the proprietary minicomputer OSs of the day (e.g. VMS, AOS, HP's own MPE). No vendor did more to fill that gap and make multi-workload a workaday reality. HP added a fair-share scheduler (FSS), the first multi-system high availability clustering in Unix (MC/ServiceGuard), and scores of refinements along the way. As a result, in practice HP-UX was admirably hardened, and it ran more users and more concurrent competing jobs per system than any other Unix system could. Often by a wide margin.
In ~1995 HP doubled down on FSS with Process Resource Manager (PRM), which could guarantee various "shares" (weighted priorities) of total machine resources. First commercial Unix ancestor to today's containers. In production ~6 years before BSD jails and Virtuozzo, ~10 years before Solaris Zones, ~18 years before Docker/Linux containers, and ~20 or more years before container were mainstream production vehicles.
Unfortunately for HP, its workstations (the ones OP acquired) weren't nearly as popular with universities and developers as Sun Microsystems', so you tended to find HP-UX in commercial production—larger servers, more workload, but smaller numbers. And thus smaller ability to promote its innovations or be selected because of them.
Hat tip to steely-eyed missile man Xuan Bui and the many unsung engineering stars of HP in the Unix era.
"Early metallurgists found to have been experimenting with the properties of metals and ores, laying the foundation for future advances that would prove economically and technologically important" is not the biggest possible reveal.
ed isn’t quite flipping binary toggle switches to load your program, but close enough to deliver the joy of brutal minimalism along with a nostalgic waft of yesteryear.
While a screencap image hides the message, a screencap video shows it perfectly well.
"Fukushima was a massive disaster. It was also Arthur Buzzby's origin story."
That window window of optimism—roughly mid-1980s to mid-1990s—closed fast. Open source projects and _de facto_ standards proved far more powerful in deciding where applications would run, where investments would be made, and which variants survived. Today, the real baseline isn’t POSIX in a binder or some Open Group brand certificate, but Linux + GNU + the APIs everyone codes to. In some ways we've regressed—or more charitably, we shifted back to a more pragmatic form of standardization.
But at the same time, globalization means legal mandates are increasingly extra-territorial in scope and impact. U.S. patent law affects anyone whose products touch the American market.
Similarly, CCPA/CPRA and GDPR reach far beyond their nominal geographic borders.
IANAL nor a patent judge, but this is my understanding after watching the space for some years.
No one genuinely interested in document openness—be it for document workflows, publishing automation, content archiving, or future-proofed documents—would have done it that way.
Maybe it was as simple as dumping a simplistic re-encoding of its legacy binary format into XML and ramming it through standards organizations. But yes, there was malice aforethought and a classic Microsoft playbook in motion: embrace, extend, extinguish.
Very effective way to summarize reports, recommendations, or analysis. IME well-received and appreciated by those consuming complex info for the first time.
Still love the style, though one does need to soft-shoe it so as to not scream "this is LLM copypasta!"
Dean, Ghemawat, and Google at large deserve credit not for inventing map and reduce—those were already canonical in programming languages and parallel algorithm theory—but for reframing them in the early 2000s against the reality of extraordinarily large, scale-out distributed networks.
Earlier takes on these primitives had been about generalizing symbolic computation or squeezing algorithms into environments of extreme resource scarcity. The 2004 MapReduce paper was also about scarcity—but scarcity redefined, at the scale of global workloads and thousands of commodity machines. That reframing was the true innovation.
Unless Google has discovered a way to directly transfer heat to the aethereal plane, nothing they’re doing is new. Mainframes were moving chip and module heat entirely outside the building decades ago. Immersion cooling? Chip, module, board, rack, line, and facility-level work? Rear-door and hybrid strategies? Integrated thermal management sensors and controls? Done. Done. Done. Done. Richard Chu, Roger Schmidt, and company were executing all these strategies at scale long before Google even existed.
Just assumed Prime's claimed ratings were untrustworthy and must be based on some corporate "we'll promote your dreck, no problem-o!" data feed. But a bit sadder that Rotten Tomatoes, once at least reasonably legit and crowd-sourced, now poisoned by the same "everything's good! watch it! watch it!" inflation. Not surprising. Anti-surprising, really. Still a bit sad.
Thank you for the excellent historical, statistical deep dive.
f-strings put the value in the output string exactly where the value should be. Massive win for contextual awareness, no need to count ...3, 4, okay what's the position 4 value over on the right, does it match up?? And they use classic Python string formatting commands, except the = operator which makes them even better with a "name the variable, show its value in a concise way" option. What's not to like?
(And if you don't like them, uh...they're not mandatory. Just don't use them.)
Xerox, LMI, Symbolics, Intel iAPX 432, UCSD p-System, Jazelle and PicoJava—just dozens of fancy designs for Lisp, Smalltalk, Ada, Pascal, Java—yet none of them ever lasted more than a product iteration or three. They were routinely outstripped by MOT 68K, x86, and RISC CPUs. Whether your metric of choice is shipment volumes, price/performance, or even raw performance, they have routinely underwhelmed. A trail of tears for 40+ years.
At long last, the 1990s will soon come to an end.
I wasn’t ratting people out—I was translating. Reminding siloed teams why other groups mattered, why customers cared, and why that business still went ca-ching.
If that feels like snitching, maybe the problem isn’t the messenger.
1. Designated Teller of Hard Truths. I operated outside each client's organizational hierarchy and internal factions. By design, I was expendable and not seen as having a particular bias or “dog in the hunt.” That made it easier to say the difficult things that needed saying. E.g. "Your product...is not good and not competitive." "Competitor X is eating your lunch because A, B, and C. You need to get your act together and admit that those are important issues."
2. Bringer of News from the Outside World. Large organizations become exceptionally insular and self-referential. Everyone inside has to speak the house jargon and more-or-less toe the company line. I could break that spell, bringing in new concepts, perspectives, language, and attitudes. Over the years as a tech analyst, I introduced object-oriented programming, CAD/CAM/CAE, distributed computing, Unix, “Big Iron Unix,” the Internet, grid and clustered computing, web services, standardization, buy-not-build strategies, Linux and open source, virtualization, automated provisioning and orchestration, cloud computing, blade servers, scale-out architectures, and DevOps. Many of these were initially unfamiliar or viewed with disbelief and hostility. I also was a conduit for shifting customer expectations and appetites, market attitudes, and cultural vibes—offering a “voice of the customer” or “voice of partners” when internal teams wouldn't otherwise get a clean, unfiltered read on what was happening in the world outside their walls.
3. Family Counselor. Surprisingly often, I told organizations what other people inside the same organization were thinking, saying, or doing (and what customers or partners thought of that). The degree of insularity, siloing, and parochialism in large organizations is hard to overstate. I was almost like a counselor, helping internal teams see, understand, and appreciate their peers, and put what they were doing into a larger perspective that would have otherwise been overlooked.
I did a lot of other things, but these were my largest, most systematic, and most recurring patterns of "adding value."