Do you know where I can read more about QR code protocols? I was under the impression that a simple URL (with http/s) is common, and I've never had it not on any device.
I daily drive NixOS, and while I initially had the same experience I've settled on some workflows that basically allow me to run anything with minimal maintenance.
I think it's a problem that many tutorials and example configs you find online are very verbose and propose complex patterns, when you don't really need that much for it to be useful. There is still a learning curve, but you don't need to write a modularized configuration framework if you just want some machines with synced config and apps.
I've written about my workflow here [1], but haven't published it anywhere yet. Not sure how useful this is to other people.
It records escape sequences verbatim during capture, then handles them intelligently during replay.
Recording phase: All terminal output including ANSI escape codes, color sequences, and cursor movements are captured exactly as they appear - no processing or stripping occurs.
Replay phase:
- Decodes various escape formats (\u001b, \033, \x1b) back to actual
escape characters
- Filters out problematic terminal query sequences that could cause
artifacts
- Preserves visual escape sequences (colors, cursor positioning) for
faithful reproduction
So yes, escape sequences are recorded verbatim, but the replayer ntelligently processes them to recreate the original terminal experience while avoiding terminal corruption.
That sounds like a good strategy! I've dabbled in writing task runner, and relaying logs with preserved colors and formatting without messing up the terminal and interleaving messages from different tasks is a huge hurdle.
I wish there was a standard for telling processes "keep the colored and formatted output, but assume it will be read line by line"... It's possible to just let processes write into pty's and then parse the output, but then you pretty much have to implement an entire nested terminal emulator :-(
Interesting - I've had the opposite experience. I usually prefer rust for personal projects, but when I recently tried to use SQLx with sqlite, lots of very basic patterns presented problems, and I wished I had sqlc back.
So, you barely read one sentence, then went to the comments, read an entire thread, and took the time to post about how the author probably thinks they are superior to you?
I strongly recommend rethinking that approach. You ascribed intentions to the author and then spent more time getting upset about them than you did interacting with the content.
There are actually interesting points in that text, yet here we are getting fussy about the author's supposed lack of decorum. That's really disappointing to me.
Funnily enough, I didn't read an entire thread, I read that one comment and posted an agreement to it. I'm not overly fussed if you are disappointed in me.
Most of the time, if you read the headline for a study, and instantly have a thought that would make the entire study's results pointless, it's very very probable the study authors had that thought too and mitigated it. It's their job.
The solution is arguably not super straightforward, but `2&>1` can be emulated by creating a pipe2 and then passing it to both stderr and stdout for the command.
LLMs are useful to me in a lot of ways, I just found it hilarious that it runs into the same pattern over and over and then just gives up, but _still recognized that it's failing_ - most of the time it just confidently outputs broken rust.
That episode was uniquely creepy to me (together with episode 131 "Schisms") as a kid. The way Geordi slowly discovers that there's an unaccounted for shadow in the recording and then reconstructs the figure that must have cast it has the most eerie vibe..
Agreed! I think partially it was also that the "bodycam" found footage had such an unusual cinematography style for the show. TNG wasn't exactly known for handheld cams and lights casting harsh shadows. It all felt so out of place.
It's an interesting episode in that it's usually overlooked for being a fairly crappy screenplay, but is really challenging directorially: Blocking and editing that geeky computer sequence, breaking new ground stylistically for the show, etc.
