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 :-(

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.

[1] https://happens.lol/blog/how-to-nixos-insane/

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.

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.

Seems like it's really an infinite loop. It keeps getting more frustrated and snarky.

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.

Comments URL: https://news.ycombinator.com/item?id=44282421

Points: 5

# Comments: 2

I'm also using nice!nanos in my projects, and they're great little devices. At this point I'd love there to be a good alternative using a dongle, though... I have a desktop PC that I want to use them with, and since they can't connect via Bluetooth at boot time, I always have to connect them to select a boot option and unlock my ZFS drive.

Having an affordable or open source controller that can do split as well as nice!nanos, but also switch between Bluetooth and a dongle is like the holy grail to me. I'd instantly buy 10.

X will never have those things, while Wayland is consistently improving. Yes it has rough edges, yes the security model might be over-engineered, but it's perfectly serviceable nowadays from my point of view.

Whenever I've had to write kotlin for Android in the past I did quite enjoy it. It seems like the entire ecosystem is very enterprise-y when it comes to web though. Forced adherence to object orientedness and patterns like 100 files, 5 folders deep with 10 lines of code each keep cropping up in most kotlin projects I've seen.