tkone

Ironically this is EXACTLY what the journald receiver for OpenTelemetry does, which, as they noted, is written in go.

Specifically because you're only supposed to use that OR the c bindings by design because they want the ability to change in the internal format when it's necessary.

so can couch/pouch? (pouch is a façade over leveldb on the backend and client-side storage in your browser)

have you done benchmarks to compare the two?

i know from personal experience leveldb is quite performant (it's what chrome uses internally), and the node bindings are very top notch.

you can fit a lot of goats into a pouch, depending on the size of the pouch

the scratch non-stick pans, which also are horrible for your health.

cast iron, stainless steel.

Transmit is a file transfer client (like FTP). It needs access to your entire drive because you might want to copy something to/from anywhere in your drive.

Google docs was originally ot based as well. I'm not sure about the current state of it.

If you’re debugging something simple or non-distributed, this product isn’t for you.

If you’re working on anything distributed, log aggregation becomes a must. But, also, if you’re working on anything distributed and you’re looking at logs, you’re desperate. Distributed traces are so much higher quality.

Arg this article is wrong.

TrueType was FREELY licensed. You could use TrueType fonts in Windows 3.1. (I know, I was there.)

What Apple didn't license was their Advanced Type Tech (Quickdraw GX?) which allowed for further refinements to glyph positioning.

yes. that is not true. you can build a rich text editor with simple ot. no tree necessary.

this already happened to some extent. the “blessed” way to develop github is in vscode (from ms), using codespaces (from ms), running on azure (from ms). vim/emacs users can use the terminal (although the codespace and port forwarding, at first, had to be done via vscode exclusively) but your entire toolstack needs to be installed each time you launch a new one.

collaborating with anyone at ms already meant you were using teams to some extent.

(former github developer)

Simple answer: github was doing most of this work as SHA1 is a non-allowed hash type for FIPS compliance, which mattered since Microsoft had landed the US DoD JEDI contract.

The JEDI contract was cancelled a in 2021 so the work never continued on that workstream.

source: former github developer

You don't just get the threadpool by default when you write a native add-on. The native add-on needs to opt into the behavior. I can't find a single place in this source code where they're using the threadpool to schedule synchronous code to run in a separate thread.