Don't think so, I've got better results when I use a framework, specially with svelte
Ask HN: Does Claude Code remove the need for so many front-end frameworks?
11–20 of 27 posts
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#12Like Rich Harris said in a Svelte talk once: “frameworks are for organizing your mind”. As far as I can tell, the same is true for LLMs
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#13It all depends what you want to build. If you build a simple website, sure go with plain html/css/js. However, if you build something that needs let's say performant DOM updates, React or similar will give you that for free, and otherwise you'd have to develop and test it yourself.
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#14[flagged]
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#15I would rather maintain a vibe coded frontend that uses well organised react components than some huge vanilla js codebase.
I think the needs are perhaps a bit different now. Syntactic sugar is perhaps less important for example. But code structure and architecture are still critical.
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#16In my initial prompt I explicitly tell DeepSeek to use Node, Express, EJS and PostgreSQL only, plain HTML, JS and CSS. Nothing else, not a single extra package.
So far apps are the best, easy to read, easier to maintain.
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#17[flagged]
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#18It depends on what you want your frontend to do.
The main reason frontend frameworks like React/Vue existed was to manage complexity, like state, DOM updates, component reuse. If your target is simple interactions, Claude can absolutely remove the need for a framework by generating clean vanilla JS without you needing the abstraction layer. But for complex interactions, using a framework is still the better choice, you can ask Claude to build on top of a given framework rather than letting it generate custom implementations that may break on edge cases.
So yes, Claude Code does reduce the need for frontend frameworks, but there are still good reasons to use them.
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#19Yes. Memorizing syntax is now obsolete. Frameworks are generally somewhat constrained, now they can be auto-generated to be exactly the UI you want. Only caveat would be saving tokens but tokens are cheap. RIP
Re: Ask HN: Does Claude Code remove the need for so many front-end frameworks?
#20I've been a rails centric developer for 10+ years and dabbled in React, but lately have felt "supercharged" in my domain, and doing side projects that are explicitly front-end React/Next.js, etc. For my primary job, I work in the enterprise where I'll use AI to assist but I'm still coding 50% there. I think you just need to resist the "letting it rip" and doing everything on its, where properly managed it's a great tool. Not to self-promote but the first ai-assisted next.js typescript project I did which was a revelation: https://flip.watch