81–90 of 133 posts
IndexDB, Postgres, Javascript, Typescript, Clojure. Not bad, but not much more attractive than the usual technology zoo any startup seems to end up with.
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.
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 f…
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...
Earlier quoted context omitted.
If someone else's account is compromised, you would not be, because apps are logically separated. There would be no way for the compromised or uncompromised account to ever see your data. If Instant is compromised, then that's a lot more dangerous. We minimize this risk following security best practices: keeping data encrypted at rest, keeping secrets hashed at creation time, etc.
Oh they’re logically separated. Thanks for explaining that. Now I’m certain nothing could possibly go wrong. /s
If you want more details, read their open source codebase or ask them specifically what documentation would boost your confidence, instead of leaving snarky comments.
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.
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.
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.
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.
Don't get me wrong, as I look for some simple backend for an app I plan it does look another awesome alternative.
But what I'm not understanding is, what makes it 'ai-coded' focused?
And least, vs. other backends, it seems to be TS focused. do you have plans to have some drop-in bindings for (native) mobile platforms?