pdpi

And they’re not alone — mercurial is hg and the silver searcher is ag.

Nvidia doesn't really do B2C. They don't sell graphics cards to consumers, they sell GPUs to OEMs who build cards around them.

The "top 20 of 2026" table in the article puts Amazon at $776B, but only 3.75% of that ($29B) attributed to B2C revenue. I don't know whether that number is correct, but AWS is clearly a massive chunk of non-B2C revenue for Amazon.

> It's clear he brought a gravitas to the role that inspired a team of young/new actors around him

That's a lesson everybody on this site should learn — Every senior is a leader, even if they don't think they are. People (mostly the more junior sorts) look up to you as a role model whether you (or they) know it or not, and that's very real power that you must learn how to wield.

I've given negative reviews to technically excellent candidates in the past because just about everybody in the org would look up to them if they got hired, and they would be a terrible role model.

The issue with AI-produced text is rarely bad grammar these days (if anything, that's a marker of human-written text now!), but rather stiff-sounding constructions that humans don't actually use. In this case — semicolons are grammatically correct, but very few people actually use them them (same for em-dashes like what I just used, but you can pry them from my cold, dead fingers).

The same, I expect?

A judge might be a little more lenient with procedural mistakes to a pro se litigant who's trying to comply with the spirit of the proceedings, but smartarses won't get any such luck. At best they'll get a sternly worded warning the first time they get "creative".

I don’t know anything about the Brazilian legal system. In England and Wales, or in the US, the lawyers are officers of the court, which means they have a duty of candour, and a duty to put the integrity of the legal system above the interests of their clients.

That paragraph was never intended to be read by the judge or opposing counsel, it’s a deliberate attempt at messing with the tools they use to analyse the filing. The fact that it’s white text on a white background makes it an incontrovertible attempt at deceit.

We can discuss how wise it is to use AI to analyse legal documents for you, but that doesn’t change how outright deceit should be handled by the court.

A better framing is that security has largely been built on theory that most targets aren't worth the effort to target, so security spending is focused on preventing/mitigating untargeted spray-and-pray attacks.

It's effectively shareware. What was old is new again.

The 2020 Touch Bar 13" was 1.56cm x 30.4 cm x 21.2cm and 1.4kg, so this is the same weight, and thinner while having a slightly bigger footprint.

Yeah, that's what I was getting at. The £700/£800 difference between the iMac and the Mac mini doesn't buy you as much as you'd hope. It's just not very good value at all.

If I were buying a display for work (which is to say, mostly programming), my choice would probably be the £600 BenQ RD280UG — a 28" 3840x2560 display, which is 4k vertically enlarged to a 3:2 ratio.

Lowest spec config costs £1529 vs £899 for the equivalent Mac mini, but the mini gives you Ethernet and 2 cores. Highest spec goes up to £3099 vs £2299 for a matching mini.

£700/£800 buys you a 24" display (with an unspecified refresh rate, so presumably 60Hz), a keyboard, and a mouse. I loved my 27" iMac to pieces, but it's really hard to justify buying this thing today.

One thing that helped me understand it was to reframe it as a network application, where you have a client running on the CPU and a server running on the GPU (the shaders).

A bunch of the complexity comes from having to write both client and server, and the communication protocol between them, then some more comes from the client being responsible for spinning up the server. As with every network service, client/server traffic is the slowest part of the architecture, so a bunch of complexity then comes from having to minimise the amount of network calls (or draw calls, in this case).

Then you hit the part where all of this is performance critical (soft-realtime requirements), so the whole thing is geared towards “writing your own userspace IP stack in C++” rather than “writing a flask application in Python”.

That model of development is what led to Eric Raymond’s seminal The Cathedral and the Bazaar essay.

“Cathedral” refers to development behind closed doors, where you just get a release and a source dump to go with it.

“Bazaar” refers to development done in the open, where you have constant access to the bleeding edge.

At the time of the essay, GCC and Emacs were ESR’s examples of Cathedral-style development, and Linux was the premiere example of the Bazaar style.

The Cathedral style has become a lot less common over the years, but it’s still how e.g. SQLite operates, I think? E.g. Google definitely operates like that with AOSP, but that's arguably more a fruit of them being maliciously compliant with their Open Source promises.