Thread

AI coding has made CI a bottleneck, so we reworked ours to keep up

317 points · 408 comments · julian_digital

torben-friis · 1790026444 · focus · HN ↗
Here's my constant question:
Everyone's going so fast that they keep hitting walls. Review, CI, product asking for things, whatever.
Why have we not seen an improvements in products?
While every post and thread feels like a 90's wall street office, the new android and iphone ship with fewer features than usual. No indie guys come up with a linux-sized alternative OS. Switch 2 remains unhacked. Windows takes 3 seconds to show the right click menu.
Is everyone just running full speed in circles or something?
1. 72deluxe · 1790067287 · focus · HN ↗
  Perhaps it is because the last 20 years has seen a shift in developer culture away from lower-level understanding and native applications so that all the vibe-coded apps you use on the desktop are Chromium-based web "applications".
  If you apply AI to low-level applications, it is quite good and you avoid the runtime bottleneck of webness, I have found. Eg. <a href="https://github.com/Redrum624/Vitrine" rel="nofollow">https://github.com/Redrum624/Vitrine is very good but has a horrible UI due to the webby nature of its rendering - all vibe coded. If you used a native toolkit it'd feel completely different.

Unofficial Hacker News client; not affiliated with Y Combinator.