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.
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.
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.
nah, that’s not true at all. have a look at ‘rich-text’[1] which allows for transforms on metadata in a separate stream from the main content. it’s the same basic algo used for OT on plain text.
(i was the cto at a startup which used this to create a multi-user text editor with rich text support in 2015ish)
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.
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.
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.