423 karma · joined February 9, 2022
They opened themselves up to this line of legal reasoning.
I was also fairly pissed about having to pay $100+ on a calculator which was wholly unnecessary for learning "area under the curve" and "slope at a point". College is such a shakedown.
It's a shame they didn't make it though. From a technical perspective, the old man knew what he was doing.
If this were a forum, instead of a plantation, I could post selections from it, and you could see for yourself.
It is ridiculous. Going by the "Computer Lib" book, and when it was published, it's obvious that Ted knows enough about how computers work, and has had more than enough time to write the thing all by himself--if his only problems were programming ones.
In a way, I am glad he failed. A Google-scale Google is bad enough. Adding a Google-scale Elsevier into the mix is not a plus.
Latest example: Taylorism, applied to the bedroom.
No no no no no no, no no no no no no no no no no. No no no no no no? No! No no no no no no no, no no no no. No no no no no, no no no no no no no no no no.
No no. No no no.
(borrowed from Caitlin Johnstone)
> Although Mercurial was not selected to manage the Linux kernel sources, it has been adopted by several organizations, including Facebook, the W3C, and Mozilla. Facebook is using the Rust programming language to write Mononoke, a Mercurial server specifically designed to support large multi-project repositories.
Mercurial @ Google:
> Speaking of Google, their Mercurial rollout on the massive Google monorepo continues. Apparently their users are very pleased with Mercurial - so much so that they initially thought their user sentiment numbers were wrong because they were so high! Google's contribution approach with Mercurial is to upstream as many of their modifications and custom extensions as possible: they seem to want to run a vanilla Mercurial out-of-the-box as possible. Their feature contributions so far have been very well received upstream and they've been contributing a number of performance improvements as well. Their contributions should translate to a better Mercurial experience for all.
https://groups.google.com/g/mozilla.dev.version-control/c/hh...
For a transactional database, XFS + hardware RAID is going to be a more reliable setup than ZFS + JBOD. Database logs are similar in function to CoW, & the fancier DBs have time-machine features similar to snapshots. Having filesystem & software struggling against each other to solve the same problem, but with different solutions, is a situation that invites so many Heisenbugs. That, and a good RAID controller is going to handle drive-reported errors sooner and more gracefully than a ZFS scrub.
The quality issues in modern machines are the byproduct of a quantity-cult pissing contest rather than necessity. If anything, the excesses are only wasted by sloppier software (which was enabled by the excess to begin with), piggier websites, covert crypto miners, etc. Wirth's law is a vicious cycle.
And it's a false economy: cut corners on the clean-up of discarded speculative branches, get some great numbers on the latest benchmark; the chipmakers who stoop to this get an edge in the market, but by the time it hits the consumer (who has no understanding of such things), the mitigation costs exceed the original "improvement". Because it is such a multi-variate & workload-dependent situation, it may not be cut-and-dry fraud, even though it smells a lot like it.
This is not to ding ZFS. If I were in Sun's position of having to take responsibility for 3rd-party manufactured drives, I'd have done the same thing. And circa 2006, the reliability of in-drive error detection may have been in a poorer state.
Never had a corruption issue the past 10 years that wasn't preceded by months of SMART errors/warnings.
ZFS is fantastic for some applications, not so much for others.
The typical user doesn't need to bean-count every microsecond. He desperately needs a computer that is his own tool rather than an infosec quagmire & the business-end of tech sector money-proboscis.
It is, sadly, the path of least resistance. "Big number good" is much easier for a consumer to grasp than the (qualitative) corners that were cut to achieve those big numbers. Lies, damn lies, & benchmarks!
The combinatorics of making distributed the new default are astronomical. That he dashes this all off so lightly, and in so little detail, makes me wonder if he's ever really done the work. Whether he has, or he hasn't, this is still 100% the wrong direction for anyone outside of a data center.
&& find a decent FFI wrapper if my app isn't in C-land
&& read the docs
&& static link hassles so I don't have to sort-out dynamic-link hassles for every platform
|| round-up a collection of dynamic libsixel libs & figure out how to bundle them with my script if I'm not using a compile-to-machine-code language
vs
b64 := base64.Encode(myImg)
fmt.Printf("\x1b]1337;inline=1;size=%d:%s\n", len(b64), b64)
If it's a feature request where I'm really only handling it to shut a few people up, which route am I going to take?https://sw.kovidgoyal.net/kitty/graphics-protocol/
If the goal is to hot-patch graphics into existing TUIs, Kovid is probably on the right track with this. It needs to be something richer than what sixel or iTerm2 provide--with pixel placement, play/pause, scaling, etc. Though for a do-over of piping a UI over a (relatively) low-bandwidth wire, I think something like Sun NeWS would have been a simpler & more feature-complete approach.
From a dev perspective, it's a lot easier to base64 an image you already have, with a base64 that's already in your stdlibs, than to scour github for a passable sixel library to pre-rasterize that jpeg & reformat it as sixel. I say this as someone who's written a sixel conversion library.
> competing formats
It's not a very old format, yet already supported on 4-5 terminals last I checked.
> something like xterm for linux that is more up-to-date
Dickey put a lot of effort into xterm--especially on the correct emulation of old protocols like tektronics. The GPU-accelerateds may be the new hotness, but I don't think many of those devs are interested in software archaeology like tektronics & sixel.