even though it's at 1.x release, Bun still has so many critical issues (segfault, etc...)

since generation is not deterministic, how do they verify the lock file?

Generation of the lock file is deterministic.

See here for information about determinism https://github.github.com/gh-aw/reference/faq/#determinism

The generation of the workflow file from the input markdown file is deterministic. It's what the agent does when running the workflow that is non-deterministic.

i'm curious what are use cases for a lamp this bright?

Places where the sun doesn't always shine.

i used to love this type of app 20 years ago. i found it mostly not needed these days.

That's a fair point! A lot of older tools were just simple text storage.

We built Blink with a modern philosophy in mind—it's not just for storing snippets, but for instant recall by meaning.

For example, instead of remembering a specific command, you can just search "flask route" and it finds the right snippet in <1 second. It's designed to work like an external brain for developers who are constantly context-switching between different languages and frameworks.

Would love to know if that kind of semantic search would have been useful to you back in the day!

yeah that's a nice addition.

ksnip is pretty damn good too.

Was looking to see if anyone had mentioned ksnip. Agreed, it’s great.

the arch infrastructure is so fragile. their wiki and aur are down pretty frequently.

curious why was it banned? it's doing sth malicious?

Transmission version 4.0.6 is widely banned by private and public BitTorrent trackers due to a critical bug in its announce logic, which causes it to overwhelm trackers with excessive requests (a "hammering" or DDoS-like effect). This issue arises particularly when IPv6 is disabled or unavailable, causing the client to loop rapidly.

everything is dead. what lives on is their protocol.

same for redis, kafka, ...

you can use gpu too. i have to admit the app is very easy to use and super convenient. kudos to creator

Yes, and with GPU, it's Whisper, which has been mentioned elsewhere in this article's comments. I mean that handy.computer provides the other option as a fallback for those who can't or don't want to use the GPU.

cool,, i have to check out process-compose.

It's pretty much just docker compose, but you don't have to forward ports or map volumes because the processes are not running in containers. The TUI is pretty nice also. If docker compose has an equivalent I'm not aware of it.

Its especially nice for use with agents because the process-compose commands can be used to understand what's running, what's pending, what's failing, etc. Of course there's always `ps aux | grep` but that's full of noise from the rest of your system and it doesn't provide and structure for understanding: "foo is not running because the readiness check for bar is failing".

Containers have their place, but I don't think it's everywhere.