News for hackers. Stuff that matters.
Re:Instant 1.0, a backend for AI-coded apps by storus on Thursday April 09, 2026 @07:43PM (#47711760)
An honest question - why would we need any frameworks at all for vibe coded apps? I can just tell the coding agent to use pure HTML5/Vanilla JS/CSS on the frontend and pure whatever on the backend and it would do it. No need for hundreds/thousands dependencies. For deployment I can ask the coding agent to do the same.
Re:Instant 1.0, a backend for AI-coded apps by stopachka on Thursday April 09, 2026 @07:48PM (#47711803)
A few reasons:

1. Unlimited projects: when you spin up traditional backends, you usually use VMs. It's expensive to start many of them. With Instant, you create unlimited projects

2. User experience: traditional CRUD apps work, but they don't feel delightful. I you want to support features like multiplayer, offline mode, or optimistic updates, you'll have to write a lot more custom infra. Instant gives you these out of the box, and the agents find it easier to write than CRUD code

3. Richer features: sometimes you'll want to add more than just a backend. For example, maybe you want to store files, or share cursors, or stream tokens across machines. These often need more bespoke systems (S3, Redis, etc). Instant already comes with these out of the box, and the agents know how to use them.

There are a few demo sections in the post that show this off. For example, you can click button and you'll get a backend, without needing to sign up. And in about 25 lines of code, you'll make a real-time todo app.

Re:Instant 1.0, a backend for AI-coded apps by boxedemp on Thursday April 09, 2026 @09:33PM (#47712502)
>multiplayer

How does it compare to photon networking? I've been using photon and webrtc mostly. I haven't had any issues, but I'm always interested in finding better solutions!

Re:Instant 1.0, a backend for AI-coded apps by stopachka on Thursday April 09, 2026 @11:01PM (#47713103)
Photon looks interesting! I am not too familiar with it, but from what I understand Photon and WebRTC are for communicating messages between clients. Those messages can be very fast, because they aren't blocked by writes to disk. Instant has two similar services, Presence & Streams. The primary sync engine is more for storing relational data.
Re:Instant 1.0, a backend for AI-coded apps by boxedemp on Saturday April 18, 2026 @01:17AM (#47813341)
So not for real time applications?

Still very interesting, thank you for the information!

Re:Instant 1.0, a backend for AI-coded apps by calvinmorrison on Thursday April 09, 2026 @09:23PM (#47712433)
same reasons human do. context and abstraction.
Re:Instant 1.0, a backend for AI-coded apps by storus on Thursday April 09, 2026 @10:42PM (#47712989)
I can get rid of irrelevant abstraction bloat that way and make code perfectly tailored for what is needed. This was traditionally expensive which led to abstraction being packaged in frameworks.
Re:Instant 1.0, a backend for AI-coded apps by IncreasePosts on Thursday April 09, 2026 @09:25PM (#47712453)
You don't necessarily, but each token costs money for the AI to spit out. And probably more money when that output is used as input later. Delegating to a library makes sense financially.
Re:Instant 1.0, a backend for AI-coded apps by storus on Thursday April 09, 2026 @10:43PM (#47712996)
With local inference on pretty decent local models we have nowadays (Qwen-3.5 and better) it's not much of a concern anymore.
Re:Instant 1.0, a backend for AI-coded apps by Bishonen88 on Friday April 10, 2026 @03:12AM (#47714650)
what percentage of people is using local models for anything serious? I reckon single digits if even that. And for a corporate work environment, probably close to 0.
Re:Instant 1.0, a backend for AI-coded apps by walthamstow on Friday April 10, 2026 @08:01AM (#47716786)
Sure, if you've got a £5k laptop
Re:Instant 1.0, a backend for AI-coded apps by IncreasePosts on Friday April 10, 2026 @03:07PM (#47722299)
Sure it is - there's still an opportunity cost of spending tokens(time/energy) creating a library from scratch vs using a preexisting well understood API.
Re:Instant 1.0, a backend for AI-coded apps by debazel on Friday April 10, 2026 @02:50AM (#47714452)
My experience with actually trying this is that current LLMs benefit greatly from having a framework to build on.

More code in the context window doesn't just increase the cost, it also degrades the overall performance of the LLM. It will start making more mistakes, cause more bugs, add more unnecessary abstractions, and write less efficient code overall.

You'll end up having to spend a significant amount of time guiding the AI to write a good framework to build on top of, and at that point you would have been better off picking an existing framework that was included in the training set.

Maybe future LLMs will do better here, but I wouldn't recommend doing this for anything larger than a landing page with current models.

Re:Instant 1.0, a backend for AI-coded apps by jauntywundrkind on Saturday April 11, 2026 @01:27PM (#47732338)
Yes. Intent and patterns will be much clearer for future sessions. If you have a WORN situation (write once read never (modify never, including by the AI)) perhaps you can skip layering and just big ball of mud your system. I doubt many people want that.
Re:Instant 1.0, a backend for AI-coded apps by fny on Friday April 10, 2026 @03:07AM (#47714601)
Why not code in assembly?

I kid but any reason you can think of applies to app development too.

1. Good abstractions decrease verbosity and improve comprehension

2. Raw HTML/CSS/JS are out of distribution just like assembly (no one builds apps like this)

3. Humans need to understand and audit it

4. You'll waste time and tokens reinventing wheels

This inuitively makes sense. LLMs mimic human behavior and thought, so for all the reasons you'd get lost in a pile of web spaghetti or x86, so would an LLM.

Re:Instant 1.0, a backend for AI-coded apps by monooso on Friday April 10, 2026 @05:35AM (#47715600)
> Raw HTML/CSS/JS are out of distribution just like assembly (no one builds apps like this)

Plenty of people build apps with vanilla CSS and JS (and HTML is just HTML). It's a really nice way to work.

Here are a few links to get you started.

https://dev.37signals.com/modern-css-patterns-and-techniques...

https://simonwillison.net/2025/May/31/no-build/

https://bradfrost.com/blog/post/raw-dogging-websites/

Re:Instant 1.0, a backend for AI-coded apps by solumos on Friday April 10, 2026 @12:18PM (#47720359)
Plenty of people, but how many companies?

Plenty of people bake bread from scratch without a mixer, but few (if any) bakeries do.

Re:Instant 1.0, a backend for AI-coded apps by monooso on Saturday April 11, 2026 @07:49PM (#47734975)
Companies are comprised of people.
Re:Instant 1.0, a backend for AI-coded apps by jauntywundrkind on Saturday April 11, 2026 @01:29PM (#47732358)
It's also a good opportunity to use the platform, to get layering naturally.

> I keep seeing Lit gain adoption in gen-UI.

> Lit's plain JS/TS, no-build-required approach is easy for LLMs to generate and for harnesses to integrate.

> If a gen-UI pre-viewer can load standard JS modules, it can load Lit components. No custom Angular, Vue, or Svelte toolchain integration needed.

- Lit author, Justin Fagnani, https://bsky.app/profile/justinfagnani.com/post/3mj376ogels2...

Re:Instant 1.0, a backend for AI-coded apps by ehnto on Friday April 10, 2026 @06:56AM (#47716178)
Echoing other thoughts here but also, it's like getting your first 10,000+ lines of output code for 0 token cost, and no prompting effort, no back and forth or testing etc.

Just jump straight to business logic, scaffolding is done for you already.

I think in your question as well is an idea that apps from now on will be bespoke, small and unique entities but the truth is we are still going to be mostly solving already solved problems, and enterprise software will still require the same massive codebases as before.

The real win of frameworks is they keep your workers, AI or human, constrained to an existing known set of tools and patterns. That still matters in long term AI powered projects too. That and they provide battle hardened collection of solutions that cover lots of edge cases you would never think to put in your prompts.

Re:Instant 1.0, a backend for AI-coded apps by Scholmo on Friday April 10, 2026 @07:00AM (#47716212)
Its build in guard rails.

Its potentially also reduced context it has to know.

Its also a very good way to scale. Lets build a very small and well tested library for x, llm uses x for case y. it doesn't have to worry about x, its content, its security.

Re:Instant 1.0, a backend for AI-coded apps by storus on Friday April 10, 2026 @07:31PM (#47725196)
Security is questionable - if there is a framework hack available or supply-chain attack, you are in danger. However, if you have everything coded from scratch, then good luck to any attacker wasting time on your custom code instead of just exploiting something at scale running on computers everywhere.
Re:Instant 1.0, a backend for AI-coded apps by bdcravens on Friday April 10, 2026 @10:35AM (#47718807)
It probably has more to do with the body of knowledge it draws on than the suitability. I assume it burns more tokens to stay vanilla, as more effort is involved in implementing patterns more readily available "off the shelf".
Re:Instant 1.0, a backend for AI-coded apps by gervwyk on Friday April 10, 2026 @12:57PM (#47720878)
simple. you reduce the surface that you need to manage and shift that responsibility to the framework.

choose a good one and your can save you and your llms 1000s of decisions and future maintenance overheads.

frameworks exists because they scale.

Re:Instant 1.0, a backend for AI-coded apps by insane_dreamer on Friday April 10, 2026 @01:36PM (#47721314)
validation -- you're using already validated components instead of relying on the LLM to create them and ensure they are validated