Peer Stritzinger
9.1K posts

Peer Stritzinger
@peerstr
Observing the universe into existence one light cone at a time. Board member https://t.co/jfgHlLwJO7 creator https://t.co/MpnKJPwMaF https://t.co/l35QWamid7 Erlang, BSD, Physicist.







Genuinely devastating take to see from someone who popularized the GPL across so many communities. Fails to appreciate the social and cultural importance of the license.











Saying "isolated processes for fault tolerance are not relevant because they were pushed to orchestration layer" is like saying "we don't need threads, because we will just run one pod per core anyway". The difference in reacting and responding to "my connection pool crashed" by restarting the pool locally vs restarting the whole pod is going to be massive, similar to the differences in latency when coordinating across threads vs across pods. Yes, other programming languages have threads, and they raise a signal when they fail, but that's missing the point. What matters it not the signal but the guarantees. If you have global mutable state and a thread crashes, can you guarantee it did not corrupt the global state? If you can't, the safest option is to restart the whole node anyway, because it is best to have a dead node than running a corrupted one. PS: somewhat related 6-years-old post: dashbit.co/blog/kubernete…


New OpenAI repo: Symphony github.com/openai/symphony TLDR: it's an orchestration layer that polls project boards for changes and spawns agents for each lifecycle stage of the ticket You will just move tickets on a board instead of prompting an agent to write the code and do a PR


New OpenAI repo: Symphony github.com/openai/symphony TLDR: it's an orchestration layer that polls project boards for changes and spawns agents for each lifecycle stage of the ticket You will just move tickets on a board instead of prompting an agent to write the code and do a PR











