HNHacker News
TopNewBestAskShowJobs

jonathaneunice

1,150 karma · joined May 30, 2014

Platform/DevOps, infosec/GRC, and software engineer.

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.

submissionscomments
jonathaneunice··on Okta's NextJS-0auth troubles
> I was pretty appalled to see such a basic mistake from a security company, but then again it is Okta.

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.

jonathaneunice··on I am stepping down as the CEO of Mastodon
"I always want to say to people who want to be rich and famous: 'try being rich first'. See if that doesn't cover most of it. There's not much downside to being rich, other than paying taxes and having your relatives ask you for money. But when you become famous, you end up with a 24-hour job." -- Bill Murray
jonathaneunice··on The Final Straw: Why Companies Replace Once-Beloved Technology Brands
> That’s fine - until it isn’t.

This covers *so* much ground. It's utterly not predictive—but in retrospect, it often explains everything.

jonathaneunice··on Are you stuck in movie logic?
Isn't this called "name it to tame it?" When you engage higher level cognitive functions it reportedly helps you escape predominantly emotional responses.
jonathaneunice··on Installing and using HP-UX 9
There were many early stories about Scott McNealy and his Sun crew going into competitive situations against Apollo, ComputerVision, DEC, HP, Intergraph, Masscomp, SGI, Symbolics, Tektroincs—whoever, really, and there were a lot of whoevers in those days. Competition would argue: "Ours are clearly superior!!" and give a good showing of that. Better networking, display resolution, realtime responsiveness, app performance, rendering speed—whatever metric.

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.

jonathaneunice··on Unix v4 Tape Found
For context, I'm a geezer who got early access reading Lions' Commentary (6th Edition) and comparing it with 7th Edition source (running on a PDP-/something with no more than 128 KiB RAM). That was 1985, as Unix was spreading its way through universities. SIGSEGV haunts me to this day.

That was a full 40 years ago. And yet, 4th Edition is ancient history even to me.

jonathaneunice··on Installing and using HP-UX 9
SunOS evolved to be a great file server and "network computing" server, whereas HP-UX evolved to be a better multi-workload commercial server. Horses for courses—and they often ran on different turf.

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.

jonathaneunice··on Installing and using HP-UX 9
Context Dependent Filesystems were one of those weird, wonderful experiments in Unix' early days that never ultimately escaped its home world. Every vendor Unix had a few. HP were true engineers in those days, so HP-UX had more than a few. But the general corporate attitude toward sharing and standardization was very different. "We want to be standards-based, but we also need some special sauce to differentiate us from the competition."

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.

jonathaneunice··on A 3K-year-old copper smelting site could be key to understanding origins of iron
Right?

"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.

jonathaneunice··on My Ed(1) Toolbox
When even “IDEs are complete overkill—just use vi” sounds like weakness and the entitlement of modern youth, seek out the ed fan pages!

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.

jonathaneunice··on Show HN: The text disappears when you screenshot it
Or the same one.

While a screencap image hides the message, a screencap video shows it perfectly well.

jonathaneunice··on Fukushima insects tested for cognition
Future research should also test for induced meta-insect superpowers.

"Fukushima was a massive disaster. It was also Arthur Buzzby's origin story."

jonathaneunice··on macOS Tahoe is certified Unix 03 [pdf]
There was a time when “open standards” were treated as the definition of Unix. At least that's what we aspired to. POSIX, X/Open, and others competed to be the standard that mattered. Formal standards were hoped to be a sounder, fairer basis for compatibility and interoperability than the earlier era of “Unix is whatever this release says it is" for some subset of 7th Edition, System III, System V, BSD, or one's favorite commercial derivative (SunOS/Solaris, HP/UX, AIX, Xenix, UnixWare, ...).

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.

jonathaneunice··on OrioleDB Patent: now freely available to the Postgres community
Correct.

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.

jonathaneunice··on OrioleDB Patent: now freely available to the Postgres community
IP owners often play the game of “patent what you can, threaten with the rest.” So you might not be able to strictly patent the way data is laid out, but specific, novel algorithms that update or manipulate that layout and improve what was possible before? Those can be understood as key steps of an “innovative process”—and courts have been willing to uphold process claims, especially when tied to what they understand are genuine technical improvements. Fighting even a marginal patent usually means a long, expensive slog with plenty of downside risk.

IANAL nor a patent judge, but this is my understanding after watching the space for some years.

jonathaneunice··on Is OOXML Artifically Complex?
Yes, artificially complex.

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.

jonathaneunice··on Show HN: Hacker News em dash user leaderboard pre-ChatGPT
Hadn't previously seen the effusive emoji everywhere that LLMs love, but otherwise bulleted lists and paragraphs with bold-highlighted run-in headers have been a staple of consulting memos for the longest ever.

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!"

jonathaneunice··on Google's Liquid Cooling
Not quite. Google brilliantly rebranded the work of John McCarthy, C.A.R. Hoare, Guy Steele, _et al_ from 1960 ff. e.g. https://dl.acm.org/doi/10.1145/367177.367199

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.

jonathaneunice··on Google's Liquid Cooling
"From the core to the edges of the server"—what does that even mean?

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.

jonathaneunice··on Google's Liquid Cooling
LOLWUT? Hyperscalers and HPC data centers have been very concerned about power and thermal density for decades IME. If you're just running web sites or VM farms, sure keep racks cooler and more power efficient. But for those that deeply care about performance, distance drives latency. That drives a huge demand to "pack things closely" and that drives thermal density up, up, up. "Hot enough to roast a pig" was a fintech data center meme of 20 years go, back at 20kW+ racks. Today you're not really cooking until you get north of 30kW.
jonathaneunice··on Google's Liquid Cooling
It’s very odd when mainframes (S/3x0, Cray, yadda yadda) have been extensively water-cooled for over 50 years, and super-dense HPC data centers have used liquid cooling for at least 20, to hear Google-scale data center design compared to PC hobbyist rigs. Selective amnesia + laughably off-target point of comparison.
jonathaneunice··on A statistical analysis of Rotten Tomatoes
Movie reviews (stars) given on Amazon Prime's streaming service always seemed incredibly sus. All the bad movies from the long-tail back catalog all seemed remarkably highly-rated. Typical pattern: Forth-rate sci-fi action movie amalgamation of the 12 other well-known sci-fi action hits? Yes!! Four stars!

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.

jonathaneunice··on Python f-string cheat sheets (2022)
I don't understand the f-string hate.

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.)

jonathaneunice··on The "high-level CPU" challenge (2008)
Probably! Everything runs on economics. Network and graphics accelerators did just fine—but then they were (or became over time) high-volume opportunities. Volume drives investment; investment drives progress.
jonathaneunice··on The "high-level CPU" challenge (2008)
"High-level CPUs" are a tarpit. Beautiful idea in theory, but history shows they're a Bad Idea.

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.

jonathaneunice··on AOL to discontinue dial-up internet
TIL AOL still offered dial-up internet.

At long last, the 1990s will soon come to an end.

jonathaneunice··on What Does Consulting Do?
Snitching? That’s an odd flex.

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.

jonathaneunice··on What Does Consulting Do?
Gordon gets it—no surprise. We fought from the same foxholes. I stepped out of that world; he’s still in it, still an ace.
jonathaneunice··on What Does Consulting Do?
As a successful consultant for several decades, I played several major roles:

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."

jonathaneunice··on Ask HN: Why Did Mercurial Die?:(
Network effects, powered by GitHub. Back in the day I loved Hg. Logical and rounded-edges where Git was geeky, tweaky, and rough. And the how many uses this vs. how many use that numbers were not so unequal. Tossup IIRC. But GitHub made Git easy to use as a team, collaborative and social, whereas Bitbucket made it easier but not with the same enthusiasm . Small advantages in user base size, branding, and ease of being supported "in the cloud" compounded over time, until suddenly using Mercurial seemed unusual and off the beaten path yet using Git felt natural and common. When supporting services (like CI/CD services) grew, it was clear who'd they support first. The market leader, natch. And so the momentum grew. Classic VHS vs Betamax.
← PreviousPage 3 of 8Next →