Live data from Hacker News

The Architecture Behind Lovable and Bolt

beam.cloud

31–33 of 33 posts

Re: The Architecture Behind Lovable and Bolt

#31
post #22

Earlier quoted context omitted.

The Model-Context-Protocol/Mode Control Plane mix up seems to come up a lot in AI slop articles. I assume its because most AI models’ training cutoff was before Model context protocol became a big thing. You can see it here too https://www.unleash.so/post/model-control-plane-mcp-for-ai-a...

And soon, articles like that one will be ingested into next generation of models, and they would become a bit more nonsensical...

AI models are becoming better and better though. Data quality is a known issue and this won’t stop scaling up

Re: The Architecture Behind Lovable and Bolt

#32

Earlier quoted context omitted.

disclaimer: building a competitor ( https://getmocha.com ) Lovable and bolt took a massive shortcut: they outsourced the backend to a third party (supabase). This makes their ceiling to build "useful" software incredibly low. The right approach takes a lot more time: pick an opinionated framework (think ror) and build up a full stack app builder from the ground up. Took us months and months of work to get it working,…

Is this similar to the "vibe" code tool sold to Wix?

yes same category

Re: The Architecture Behind Lovable and Bolt

#33
post #5

Im always hunting for someone whos solved "sandboxing" because setting it up myself is so damn painful. Anyone ever find a good product in this space? Beam seems close, but not quite

A list of sandboxing techniques and products: https://github.com/restyler/awesome-sandbox
Post reply on HN