(although i don't, i have a CLI)
257 karma · joined May 12, 2022
(although i don't, i have a CLI)
Do you recommend any resources explaining the workflow?
By "infinite branches" you probably mean that a nix derivation / flake is a recipe that can build any version of the project?
And it might be because it is easy to provide and maintain compared to a .deb package.
Also, sin is probably used so much that inlinung would probably inflate binary size significantly.
And yes, we only look at physical photos or the "on this day X years ago" reels. But to get here, Immich was a valuable tool.
So this concern cannot be dismissed with just "slippery slope falacy", it's a new vector of the same power grab strategy.
My main concern is that it can overwhelm the context window with useless facts.
But what would be practical effects of DMA on AWS? Who is the customer, who is the vendor?
tsz seems to be a compiler, a replacement for tsc
There could be an env var $AGENT_TOOLS, a string of paths delimited by `:` and tools would be discovered as some specific format of file. Maybe a JSON that contains tool name, list of parameters and the command to run it.
This is essentially decoupling tools from the agent, allowing more customization and per-project environments. It does require shipping and installing more binaries, one for each tool probably.
In other words: an internet browser.
Or maybe it is and android's promises about openness are dead.