3/27/2026 at 7:14:37 PM
by pestkranker
3/28/2026 at 12:54:29 AM
I read the article and it's still not clear to me how they are trying to solve the bottlenecks they talk aboutby gonzalohm
3/28/2026 at 12:57:17 AM
After reading their main page I saw that they are just another provider of CI that claims to be faster. Not sure about others but to me the problem with CI/CD has never been that it's slow. The painful points are setting it up and getting it to work. Once that's done everything after it's not that painfulby gonzalohm
3/28/2026 at 9:08:35 AM
I'm building a product in the same space[1] and, in my opinion, the core problem is that small tasks meant to run as workers end up spinning up a full 64GB server instead. My approach is to separate lightweight checks (e.g. "is this commit tagged as version-*?") into workflows that run on Cloudflare Workers. They're fast, cheap, and highly available. The heavier CI/CD work can then run on usual docker contaiers/VMs.1: https://codeinput.com/products/workflow-automation - The product is still in development. Happy to connect with anyone interested in beta testing or contributing ideas!
by csomar
3/28/2026 at 3:30:45 AM
Do the investors know that "compute layer for code" doesn't mean anything and is total nonsense?by CyberDildonics
3/28/2026 at 12:02:22 PM
It does mean something to me, but perhaps not as profound as whoever coined the term was hoping!by zar1048576
3/28/2026 at 8:58:05 PM
A "compute layer for code" is called a microprocessor and a lot of companies already make them.by CyberDildonics
3/28/2026 at 3:38:24 AM
[flagged]by claytonia