{"slug": "vue", "name": "Vue", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "Open-source JavaScript framework for building reactive web user interfaces.", "recommenders": 10, "commenters": 26, "warners": 4, "score": 8.956, "rising": 3.04, "first": "2025-12-04", "latest": "2026-10-24", "why": "HN commenters like Vue for convenient, data-driven components in large, complex views, for being more stable than the churn-heavy React ecosystem, and for its first-party devtools.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 11, "neutral": 11, "compare": 1, "warn": 4}, "spark": [0, 1, 0, 0, 1, 2, 0, 1, 1, 1, 1, 3], "listed": true, "loved": ["Enjoyable to use", "Ergonomics"], "caveat": "Others preferred", "short_quote": "Vue is just a huge convenience over raw JavaScript for large, complex view.", "icon": false, "domain": null, "github_repo": "github.com/mgubi/texmacs", "official_url": "https://vuejs.org", "pricing": "open source", "aliases": ["Vue", "Vue.js"], "verdict": [{"text": "HN commenters like Vue for convenient, data-driven components in large, complex views", "cites": [{"id": 782189488, "item_id": 48886843, "url": "https://news.ycombinator.com/item?id=48886843", "by": "WhyNotHugo", "date": "2026-07-12", "stance": "recommend", "quote": "Vue is just a huge convenience over raw JavaScript for large, complex view.", "excerpt": "I appreciate the sentiment, but can't agree fully. I used vanilla JS for many years before AngularJS even existed (and I also tried AngulasJS when it was the new thing). Vue is just a huge convenience over raw JavaScript for large, complex view. Sure, I don't get to do direct DOM manipulation, but when I write C code I also don't get to pick which variable goes in which CPU register. I accept giving up control that A", "context": "", "use_case": "complex UI views", "switched_from": "", "story": "Why Vanilla JavaScript"}, {"id": 788432243, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I like the Vue/React/Svelte model of the DOM being a function of the data.", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "frontend UI", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 758628721, "item_id": 47414295, "url": "https://news.ycombinator.com/item?id=47414295", "by": "murillobrand", "date": "2026-03-17", "stance": "recommend", "quote": "I love the ergonomics of Vue/React", "excerpt": "Hi HN, I've been building an ecosystem of zero-friction, local-first productivity tools called \"That Just Works\". For the UI, I needed something incredibly fast and lightweight. I love the ergonomics of Vue/React, but I didn't want a 40kb+ payload. So, I built Sigwork. It's a 1.7kb (gzipped) fine-grained reactive engine based on signals. Instead of VDOM diffing, components run exactly once. When a signal changes, it ", "context": "", "use_case": "UI framework", "switched_from": "", "story": "Sigwork \u2013 A 1.7kb signal-based reactive framework"}]}, {"text": ", for being more stable than the churn-heavy React ecosystem", "cites": [{"id": 763844880, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "React", "story": "Why AI Sucks at Front End"}, {"id": 798917089, "item_id": 49932318, "url": "https://news.ycombinator.com/item?id=49932318", "by": "rukshn", "date": "2026-10-02", "stance": "recommend", "quote": "I was a long time Vue fan.", "excerpt": "I was a long time Vue fan. I used svelte when it was V1 but the changes in V2 put me off. Where vue was stable. But for my latest project I started using Svelte and I love it. https://github.com/entangle-cloud/wave I love that stores comes out of the box and works well. No more callbacks for two way binding and Vue $emit hacks.", "context": "", "use_case": "", "switched_from": "", "story": "SvelteKit 3"}]}, {"text": ", and for its first-party devtools.", "cites": [{"id": 798928769, "item_id": 49933048, "url": "https://news.ycombinator.com/item?id=49933048", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Vue, as a big framework, got 1st party support.", "excerpt": "I use React, Vue, and Svelte extensively, and I don't think that there is any problem with integrating 3rd party JS libraries in any of these frameworks. React, as the most bare-bones framework, might be simplest to integrate, and you can see that by the enormous size of its ecosystem. Vue and Svelte will have problems with integrating various devtools, due to the fact they use custom syntax to mimic native web tech.", "context": "Uses React, Vue, and Svelte extensively", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}]}, {"text": " The most common caveat is that some developers have moved to React, Svelte or plain HTML instead", "cites": [{"id": 799287317, "item_id": 49955457, "url": "https://news.ycombinator.com/item?id=49955457", "by": "shepherdjerred", "date": "2026-10-04", "stance": "neutral", "quote": "It is certainly better than Angular and Vue, though Vue 3 is tolerable.", "excerpt": "I haven\u2019t found a front end library I like more than React except maybe Astro. I didn\u2019t really like Svelte and I am pretty opposed to htmx. It is certainly better than Angular and Vue, though Vue 3 is tolerable. Maybe there are more popular options nowadays but tbh I am not really looking to move from React. I have zero complaints other than maybe the push towards server rendering and partnering with Next.js React is", "context": "", "use_case": "", "switched_from": "", "story": "Why don't more developers \u201cuse the platform\u201d?"}, {"id": 741026066, "item_id": 46314129, "url": "https://news.ycombinator.com/item?id=46314129", "by": "mythz", "date": "2025-12-18", "stance": "neutral", "quote": "which used to be Vue", "excerpt": "I keep seeing articles religiously pushing htmx, what I'm not seeing are sophisticated examples or apps written with it, just more basic example and interaction examples. I personally prefer UIs with great encapsulation/composition, which used to be Vue, but with AI starting to write more of my UIs now I've switched to React/Next.js for new non-progressive UIs.", "context": "", "use_case": "UI composition", "switched_from": "", "story": "Please just try HTMX"}, {"id": 798917089, "item_id": 49932318, "url": "https://news.ycombinator.com/item?id=49932318", "by": "rukshn", "date": "2026-10-02", "stance": "recommend", "quote": "I was a long time Vue fan.", "excerpt": "I was a long time Vue fan. I used svelte when it was V1 but the changes in V2 put me off. Where vue was stable. But for my latest project I started using Svelte and I love it. https://github.com/entangle-cloud/wave I love that stores comes out of the box and works well. No more callbacks for two way binding and Vue $emit hacks.", "context": "", "use_case": "", "switched_from": "", "story": "SvelteKit 3"}, {"id": 742673296, "item_id": 46417081, "url": "https://news.ycombinator.com/item?id=46417081", "by": "hecanjog", "date": "2025-12-28", "stance": "recommend", "quote": "I used and liked vue for a little while when it was needed(?) but modern HTML fills that gap.", "excerpt": "You sure can! They all have inline defaults like `<span>` so set some CSS baseline on them as needed, but this is like the best kept secret of HTML or something? Unknown tags will become `HTMLUnknownElement` and behave like a span. Edit: the reason for avoiding this in the past was name-spacing. But the standard says you can use a hyphen and then you're OK, native elements won't ever use a `-`. Edit 2: also it's grea", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "You can make up HTML tags"}]}, {"text": ", and Nuxt is called a weak option for SSR.", "cites": [{"id": 798860003, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Svelte is less polished and less comfortable to work with than Vue.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}]}], "praise": [{"label": "Enjoyable to use", "summary": "Several developers say they enjoy or love working with Vue, at work and in personal projects.", "quotes": [{"id": 799853170, "item_id": 49990823, "url": "https://news.ycombinator.com/item?id=49990823", "by": "apt-get", "date": "2026-10-07", "stance": "recommend", "quote": "Web Stack (I enjoy both Vue & SvelteKit)", "excerpt": "Location: Paris, France Remote: Yes Willing to relocate: No Technologies: End-to-end Devops/SRE -- general POSIX sysadmin stuff, modern systemd slash linux, Docker/Podman/Virtualization/etc, CI/CD (mostly Gitlab), managing different kinds of private software forges & repositories, DB clusters (Postgresql & co.), observability (Grafana stack), everything k8s. Software Engineering -- Python, Web Stack (I enjoy both Vue", "context": "DevOps/SRE freelancer", "use_case": "web development", "switched_from": "", "story": "Ask HN: Who wants to be hired? (October 2026)"}, {"id": 765432401, "item_id": 47839525, "url": "https://news.ycombinator.com/item?id=47839525", "by": "aitchnyu", "date": "2026-04-20", "stance": "recommend", "quote": "I love Vue BTW", "excerpt": "With modern editors `<h2>foo<h2>` is one keystroke more than `## foo`. Might as well tap into the React ecosystem (I love Vue BTW) and get module-organization and DRY, live preview, syntax highlighting, autocomplete, linting, AI expertise etc. There are tools to edit PPTs and movies with React. https://wyozi.github.io/react-pptx/ https://www.remotion.dev/", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: MDV \u2013 a Markdown superset for docs, dashboards, and slides with data"}, {"id": 774989666, "item_id": 48436854, "url": "https://news.ycombinator.com/item?id=48436854", "by": "evolabs", "date": "2026-06-07", "stance": "recommend", "quote": "we're on vue for all of our work projects (and I use vue for my private ones, too)", "excerpt": "Lot to unpack in the comment, but maybe to clarify from my end > I'm not the author of most of the animations so far, only a tiny fraction is remade as of now, I just started building tooling for me to develop new / more useful animations or animations for icons that dont exist yet from the lucide lib. The majority of animations was ported from animate-ui and lucide-animated (github.com/imskyleen/animate-ui, lucide-a", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "Show HN: The largest free animated icon library for Vue (523 Lucide icons)"}]}, {"label": "Ergonomics", "summary": "Commenters say Vue's model of the DOM as a function of the data makes complex views much easier than raw JavaScript.", "quotes": [{"id": 782189488, "item_id": 48886843, "url": "https://news.ycombinator.com/item?id=48886843", "by": "WhyNotHugo", "date": "2026-07-12", "stance": "recommend", "quote": "Vue is just a huge convenience over raw JavaScript for large, complex view.", "excerpt": "I appreciate the sentiment, but can't agree fully. I used vanilla JS for many years before AngularJS even existed (and I also tried AngulasJS when it was the new thing). Vue is just a huge convenience over raw JavaScript for large, complex view. Sure, I don't get to do direct DOM manipulation, but when I write C code I also don't get to pick which variable goes in which CPU register. I accept giving up control that A", "context": "", "use_case": "complex UI views", "switched_from": "", "story": "Why Vanilla JavaScript"}, {"id": 788432243, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I like the Vue/React/Svelte model of the DOM being a function of the data.", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "frontend UI", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 758628721, "item_id": 47414295, "url": "https://news.ycombinator.com/item?id=47414295", "by": "murillobrand", "date": "2026-03-17", "stance": "recommend", "quote": "I love the ergonomics of Vue/React", "excerpt": "Hi HN, I've been building an ecosystem of zero-friction, local-first productivity tools called \"That Just Works\". For the UI, I needed something incredibly fast and lightweight. I love the ergonomics of Vue/React, but I didn't want a 40kb+ payload. So, I built Sigwork. It's a 1.7kb (gzipped) fine-grained reactive engine based on signals. Instead of VDOM diffing, components run exactly once. When a signal changes, it ", "context": "", "use_case": "UI framework", "switched_from": "", "story": "Sigwork \u2013 A 1.7kb signal-based reactive framework"}]}, {"label": "Stability", "summary": "Commenters describe Vue as more stable and less churn-prone than Svelte's early versions and the React ecosystem.", "quotes": [{"id": 798917089, "item_id": 49932318, "url": "https://news.ycombinator.com/item?id=49932318", "by": "rukshn", "date": "2026-10-02", "stance": "recommend", "quote": "I was a long time Vue fan.", "excerpt": "I was a long time Vue fan. I used svelte when it was V1 but the changes in V2 put me off. Where vue was stable. But for my latest project I started using Svelte and I love it. https://github.com/entangle-cloud/wave I love that stores comes out of the box and works well. No more callbacks for two way binding and Vue $emit hacks.", "context": "", "use_case": "", "switched_from": "", "story": "SvelteKit 3"}, {"id": 763844880, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "React", "story": "Why AI Sucks at Front End"}]}, {"label": "AI tooling", "summary": "Commenters report that AI coding assistants handle Vue well.", "quotes": [{"id": 792980592, "item_id": 49561287, "url": "https://news.ycombinator.com/item?id=49561287", "by": "crabmusket", "date": "2026-09-04", "stance": "recommend", "quote": "we use Vue at work and Claude and Codex handle it just fine", "excerpt": "I wonder if this is overstated. Anecdotally, we use Vue at work and Claude and Codex handle it just fine. I'd expect Vue to be the third best-represented after React and Angular, but even then, we feel absolutely no need to change things up to get better results. Vue's reactivity is quite similar to Solid's, AFAIK, so I wonder why there would be so many issues with Solid. We have also started to have success getting ", "context": "", "use_case": "frontend framework at work", "switched_from": "", "story": "The asteroid currently hitting front end web development"}, {"id": 788432243, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I like the Vue/React/Svelte model of the DOM being a function of the data.", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "frontend UI", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}]}, {"label": "Polish and devtools", "summary": "Commenters say Vue is more polished than Svelte and has first-party support for key devtools.", "quotes": [{"id": 798860003, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Svelte is less polished and less comfortable to work with than Vue.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798928769, "item_id": 49933048, "url": "https://news.ycombinator.com/item?id=49933048", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Vue, as a big framework, got 1st party support.", "excerpt": "I use React, Vue, and Svelte extensively, and I don't think that there is any problem with integrating 3rd party JS libraries in any of these frameworks. React, as the most bare-bones framework, might be simplest to integrate, and you can see that by the enormous size of its ecosystem. Vue and Svelte will have problems with integrating various devtools, due to the fact they use custom syntax to mimic native web tech.", "context": "Uses React, Vue, and Svelte extensively", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}]}], "caveats": [{"label": "Others preferred", "summary": "Some commenters prefer React, Svelte or modern plain HTML over Vue, and some have switched away from it.", "quotes": [{"id": 799287317, "item_id": 49955457, "url": "https://news.ycombinator.com/item?id=49955457", "by": "shepherdjerred", "date": "2026-10-04", "stance": "neutral", "quote": "It is certainly better than Angular and Vue, though Vue 3 is tolerable.", "excerpt": "I haven\u2019t found a front end library I like more than React except maybe Astro. I didn\u2019t really like Svelte and I am pretty opposed to htmx. It is certainly better than Angular and Vue, though Vue 3 is tolerable. Maybe there are more popular options nowadays but tbh I am not really looking to move from React. I have zero complaints other than maybe the push towards server rendering and partnering with Next.js React is", "context": "", "use_case": "", "switched_from": "", "story": "Why don't more developers \u201cuse the platform\u201d?"}, {"id": 741026066, "item_id": 46314129, "url": "https://news.ycombinator.com/item?id=46314129", "by": "mythz", "date": "2025-12-18", "stance": "neutral", "quote": "which used to be Vue", "excerpt": "I keep seeing articles religiously pushing htmx, what I'm not seeing are sophisticated examples or apps written with it, just more basic example and interaction examples. I personally prefer UIs with great encapsulation/composition, which used to be Vue, but with AI starting to write more of my UIs now I've switched to React/Next.js for new non-progressive UIs.", "context": "", "use_case": "UI composition", "switched_from": "", "story": "Please just try HTMX"}, {"id": 742673296, "item_id": 46417081, "url": "https://news.ycombinator.com/item?id=46417081", "by": "hecanjog", "date": "2025-12-28", "stance": "recommend", "quote": "I used and liked vue for a little while when it was needed(?) but modern HTML fills that gap.", "excerpt": "You sure can! They all have inline defaults like `<span>` so set some CSS baseline on them as needed, but this is like the best kept secret of HTML or something? Unknown tags will become `HTMLUnknownElement` and behave like a span. Edit: the reason for avoiding this in the past was name-spacing. But the standard says you can use a hyphen and then you're OK, native elements won't ever use a `-`. Edit 2: also it's grea", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "You can make up HTML tags"}]}, {"label": "Framework fatigue", "summary": "Some commenters dislike mainstream frontend frameworks, including Vue, in general.", "quotes": [{"id": 784614178, "item_id": 49038386, "url": "https://news.ycombinator.com/item?id=49038386", "by": "epolanski", "date": "2026-07-24", "stance": "warn", "quote": "I cannot swallow yet another Vue/React crap.", "excerpt": "I love both effect and elm, but I cannot swallow yet another Vue/React crap. Especially after having used ruby and elixir extensively after years of react/Vue crap, it feels so backwards.", "context": "", "use_case": "frontend", "switched_from": "", "story": "The front end framework for correctness: built on Effect, architected like Elm"}, {"id": 769716914, "item_id": 48107307, "url": "https://news.ycombinator.com/item?id=48107307", "by": "bborud", "date": "2026-05-12", "stance": "warn", "quote": "Angular, React, Vue.  All terrible reminders of why I try to stay away from the frontend.", "excerpt": "I'm not fond of functional languages. It isn't that I don't get why they are a really good idea (they are). I just can't stand the syntax, the lack of proper standard libraries, and the lack of mainstream-big-ecosystem'ness. Mainstream languages are nice because there is lots of code, documentation, discussion and I can find people I can talk to. And you can write real code in situations where you may not be the one ", "context": "backend developer", "use_case": "frontend development", "switched_from": "", "story": "If AI Writes Your Code, Why Use Python?"}, {"id": 739242208, "item_id": 46202638, "url": "https://news.ycombinator.com/item?id=46202638", "by": "pianopatrick", "date": "2025-12-09", "stance": "warn", "quote": "I didn't like Vue or React", "excerpt": "I didn't like Vue or React so I've been working on my own Javascript framework this year. I wanted to share it at some point as I've gotten value from so many other people's projects. Maybe someone will benefit from my project too. My framework uses an html attribute called foreignkeys=\"\" to hold urls with custom schemes that reference pieces of browser state. When that browser state changes, the framework searches f", "context": "", "use_case": "", "switched_from": "", "story": "A prototype of an event driven JavaScript framework"}]}, {"label": "State design", "summary": "One commenter says Vue ties state hierarchy to view hierarchy, which leads to footguns.", "quotes": [{"id": 763164146, "item_id": 47697759, "url": "https://news.ycombinator.com/item?id=47697759", "by": "oDot", "date": "2026-04-08", "stance": "warn", "quote": "a deep design flaw in mainstream frameworks like React and Vue", "excerpt": "The problems OP tries to address are unfortunately a deep design flaw in mainstream frameworks like React and Vue. This is due to 2 properties they have: 1. They marry view hierarchy to state hierarchy 2. They make it very ergonomic to put state in components I've been through this endless times. There are significant ways to reduce this friction, but in the end there's a tight ceiling. This is why this kind of work ", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "Show HN: Tired of logic in useEffect, I built a class-based React state manager"}]}, {"label": "Nuxt for SSR", "summary": "One commenter says Nuxt is the only SSR choice for Vue and calls it full of ambiguity and footguns.", "quotes": [{"id": 798860003, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Svelte is less polished and less comfortable to work with than Vue.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}]}], "who": [{"by": "apt-get", "context": "DevOps/SRE freelancer", "url": "https://news.ycombinator.com/item?id=49990823", "date": "2026-10-07"}, {"by": "scurnus", "context": "built HumansMap", "url": "https://news.ycombinator.com/item?id=48572698", "date": "2026-06-17"}, {"by": "shakermaker83", "context": "Actuary with math and CS background", "url": "https://news.ycombinator.com/item?id=47741624", "date": "2026-04-12"}, {"by": "adapptivlabs", "context": "bootstrapped software company in Switzerland", "url": "https://news.ycombinator.com/item?id=46272555", "date": "2025-12-15"}], "tags": ["for complex UIs", "for work projects", "pairs with Django", "for AI-assisted coding"], "use_cases": ["frontend framework", "frontend", "frontend development", "web client", "web frontend", "web development"], "compared": [{"slug": "react", "name": "React", "co": 20, "switched_from": 1, "switched_to": 1}, {"slug": "svelte", "name": "Svelte", "co": 10, "switched_from": 0, "switched_to": 1}, {"slug": "angular", "name": "Angular", "co": 6, "switched_from": 0, "switched_to": 0}, {"slug": "htmx", "name": "HTMX", "co": 5, "switched_from": 0, "switched_to": 0}, {"slug": "next-js", "name": "Next.js", "co": 3, "switched_from": 0, "switched_to": 1}, {"slug": "codex", "name": "Codex", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "django", "name": "Django", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "sveltekit", "name": "SvelteKit", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49926536", "title": "SvelteKit 3", "mentions": 4}, {"url": "https://news.ycombinator.com/item?id=50225852", "title": "item 50225852", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49990204", "title": "Reasons to Dislike AI Coding", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49922568", "title": "Ask HN: Who wants to be hired? (October 2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49950554", "title": "Why don't more developers \u201cuse the platform\u201d?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49926931", "title": "Vue \u2013 A WebAssembly Port of TeXmacs", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"neutral": 3, "warn": 1, "recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {"recommend": 1}, "2026-04": {"neutral": 2, "warn": 1, "recommend": 2}, "2026-05": {"warn": 1}, "2026-06": {"recommend": 1, "neutral": 1}, "2026-07": {"recommend": 1, "warn": 1}, "2026-08": {"recommend": 1}, "2026-09": {"recommend": 1, "neutral": 1}, "2026-10": {"recommend": 3, "compare": 1, "neutral": 4}}, "quotes": [{"id": 803613649, "item_id": 50225853, "url": "https://news.ycombinator.com/item?id=50225853", "by": "grindthisgame", "date": "2026-10-24", "stance": "neutral", "quote": "The client is now web based and in Vue.js.", "excerpt": "I used to play a mud back in 1993-1995 called Shadowdale MUD. It was all text over telnet but was insanely fun. Maybe my fav game of all time actually. Nobody kept playing it though. The ability for mortals to immort and add new zones was unique. I wanted a map, some graphics and less text scrolling and typing so I ported it. The original source was in C with plenty of bugs. It's called Dalemud and is on github. I go", "context": "", "use_case": "web client", "switched_from": "", "story": null}, {"id": 799878801, "item_id": 49992425, "url": "https://news.ycombinator.com/item?id=49992425", "by": "karmakaze", "date": "2026-10-07", "stance": "neutral", "quote": "For web I'd probably also accept Vue, Svelte, or (simple) React.", "excerpt": "I was curious about codeberg.org as an alternative to Github for opensource work. They had voted on an LLM policy and decided against vibe-coded repos while allowing some AI use. This got me thinking how I want to use AI and if it fit with their policy. The best I could figure is that I like to start with requirements, use AI to discuss and settle on its high level design and specific aspects of its implementation. I", "context": "", "use_case": "web frontend", "switched_from": "", "story": "Reasons to Dislike AI Coding"}, {"id": 799853170, "item_id": 49990823, "url": "https://news.ycombinator.com/item?id=49990823", "by": "apt-get", "date": "2026-10-07", "stance": "recommend", "quote": "Web Stack (I enjoy both Vue & SvelteKit)", "excerpt": "Location: Paris, France Remote: Yes Willing to relocate: No Technologies: End-to-end Devops/SRE -- general POSIX sysadmin stuff, modern systemd slash linux, Docker/Podman/Virtualization/etc, CI/CD (mostly Gitlab), managing different kinds of private software forges & repositories, DB clusters (Postgresql & co.), observability (Grafana stack), everything k8s. Software Engineering -- Python, Web Stack (I enjoy both Vue", "context": "DevOps/SRE freelancer", "use_case": "web development", "switched_from": "", "story": "Ask HN: Who wants to be hired? (October 2026)"}, {"id": 799287317, "item_id": 49955457, "url": "https://news.ycombinator.com/item?id=49955457", "by": "shepherdjerred", "date": "2026-10-04", "stance": "neutral", "quote": "It is certainly better than Angular and Vue, though Vue 3 is tolerable.", "excerpt": "I haven\u2019t found a front end library I like more than React except maybe Astro. I didn\u2019t really like Svelte and I am pretty opposed to htmx. It is certainly better than Angular and Vue, though Vue 3 is tolerable. Maybe there are more popular options nowadays but tbh I am not really looking to move from React. I have zero complaints other than maybe the push towards server rendering and partnering with Next.js React is", "context": "", "use_case": "", "switched_from": "", "story": "Why don't more developers \u201cuse the platform\u201d?"}, {"id": 798928769, "item_id": 49933048, "url": "https://news.ycombinator.com/item?id=49933048", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Vue, as a big framework, got 1st party support.", "excerpt": "I use React, Vue, and Svelte extensively, and I don't think that there is any problem with integrating 3rd party JS libraries in any of these frameworks. React, as the most bare-bones framework, might be simplest to integrate, and you can see that by the enormous size of its ecosystem. Vue and Svelte will have problems with integrating various devtools, due to the fact they use custom syntax to mimic native web tech.", "context": "Uses React, Vue, and Svelte extensively", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798917089, "item_id": 49932318, "url": "https://news.ycombinator.com/item?id=49932318", "by": "rukshn", "date": "2026-10-02", "stance": "recommend", "quote": "I was a long time Vue fan.", "excerpt": "I was a long time Vue fan. I used svelte when it was V1 but the changes in V2 put me off. Where vue was stable. But for my latest project I started using Svelte and I love it. https://github.com/entangle-cloud/wave I love that stores comes out of the box and works well. No more callbacks for two way binding and Vue $emit hacks.", "context": "", "use_case": "", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798865280, "item_id": 49929080, "url": "https://news.ycombinator.com/item?id=49929080", "by": "phoghed", "date": "2026-10-02", "stance": "neutral", "quote": "I used mainly Vue from 0.12 until 3", "excerpt": "I used mainly Vue from 0.12 until 3 (migrated one project to 3 but didn\u2019t work with it extensively), with a bit of react sprinkled in. Mainly react the last 4 years or so, which let\u2019s be honest is mainly not me writing the code. I tried Svelte a couple times over the years, never really clicked for me though.", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798860003, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "compare", "quote": "Svelte is less polished and less comfortable to work with than Vue.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "frontend framework", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798830912, "item_id": 49926932, "url": "https://news.ycombinator.com/item?id=49926932", "by": "mgubi", "date": "2026-10-01", "stance": "recommend", "quote": "Vue is an experimental port of TeXmacs 1.2.5 to Webassembly", "excerpt": "Vue is an experimental port of TeXmacs 1.2.5 to Webassembly with a new (immediate mode) GUI (Vue), a new icon set, support for Opentype Math fonts, powered by S7 Scheme (instead of Guile). Fully functional. More info at https://github.com/mgubi/texmacs/tree/wip_wasm_vue", "context": "", "use_case": "TeXmacs in browser", "switched_from": "", "story": "Vue \u2013 A WebAssembly Port of TeXmacs"}, {"id": 795401972, "item_id": 49712623, "url": "https://news.ycombinator.com/item?id=49712623", "by": "greentfrapp", "date": "2026-09-15", "stance": "neutral", "quote": "a Vue + dockview frontend", "excerpt": "Hi HN, I built Panel because research work means switching all the time between a chat with an agent, the papers I'm reading, the notebook I'm running and the data files I'm looking at. Panel is a local web app with dockable panes made with dockview. You get chat, files, PDFs, markdown and Jupyter notebooks. The agent can also create custom panes on request, like a protein structure viewer or an SQLite browser. There", "context": "", "use_case": "frontend", "switched_from": "", "story": "Show HN: Panel \u2013 A research workspace where the agent can build its own panes"}, {"id": 792980592, "item_id": 49561287, "url": "https://news.ycombinator.com/item?id=49561287", "by": "crabmusket", "date": "2026-09-04", "stance": "recommend", "quote": "we use Vue at work and Claude and Codex handle it just fine", "excerpt": "I wonder if this is overstated. Anecdotally, we use Vue at work and Claude and Codex handle it just fine. I'd expect Vue to be the third best-represented after React and Angular, but even then, we feel absolutely no need to change things up to get better results. Vue's reactivity is quite similar to Solid's, AFAIK, so I wonder why there would be so many issues with Solid. We have also started to have success getting ", "context": "", "use_case": "frontend framework at work", "switched_from": "", "story": "The asteroid currently hitting front end web development"}, {"id": 788432243, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I like the Vue/React/Svelte model of the DOM being a function of the data.", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "frontend UI", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 784614178, "item_id": 49038386, "url": "https://news.ycombinator.com/item?id=49038386", "by": "epolanski", "date": "2026-07-24", "stance": "warn", "quote": "I cannot swallow yet another Vue/React crap.", "excerpt": "I love both effect and elm, but I cannot swallow yet another Vue/React crap. Especially after having used ruby and elixir extensively after years of react/Vue crap, it feels so backwards.", "context": "", "use_case": "frontend", "switched_from": "", "story": "The front end framework for correctness: built on Effect, architected like Elm"}, {"id": 782189488, "item_id": 48886843, "url": "https://news.ycombinator.com/item?id=48886843", "by": "WhyNotHugo", "date": "2026-07-12", "stance": "recommend", "quote": "Vue is just a huge convenience over raw JavaScript for large, complex view.", "excerpt": "I appreciate the sentiment, but can't agree fully. I used vanilla JS for many years before AngularJS even existed (and I also tried AngulasJS when it was the new thing). Vue is just a huge convenience over raw JavaScript for large, complex view. Sure, I don't get to do direct DOM manipulation, but when I write C code I also don't get to pick which variable goes in which CPU register. I accept giving up control that A", "context": "", "use_case": "complex UI views", "switched_from": "", "story": "Why Vanilla JavaScript"}, {"id": 777163171, "item_id": 48572698, "url": "https://news.ycombinator.com/item?id=48572698", "by": "scurnus", "date": "2026-06-17", "stance": "neutral", "quote": "Vue+ Cytoscape.js for frontend", "excerpt": "I added the Feed feature to the site to make it more usable from mobile. You can scroll and discover important connections. I used Wikidata as source, ArangoDB as database, Redis for caching, Vue+ Cytoscape.js for frontend. If you are from desktop try Explore mode.", "context": "built HumansMap", "use_case": "frontend", "switched_from": "", "story": "HumansMap, a feed of family dynasties and links between orgs. No ads"}, {"id": 774989666, "item_id": 48436854, "url": "https://news.ycombinator.com/item?id=48436854", "by": "evolabs", "date": "2026-06-07", "stance": "recommend", "quote": "we're on vue for all of our work projects (and I use vue for my private ones, too)", "excerpt": "Lot to unpack in the comment, but maybe to clarify from my end > I'm not the author of most of the animations so far, only a tiny fraction is remade as of now, I just started building tooling for me to develop new / more useful animations or animations for icons that dont exist yet from the lucide lib. The majority of animations was ported from animate-ui and lucide-animated (github.com/imskyleen/animate-ui, lucide-a", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "Show HN: The largest free animated icon library for Vue (523 Lucide icons)"}, {"id": 769716914, "item_id": 48107307, "url": "https://news.ycombinator.com/item?id=48107307", "by": "bborud", "date": "2026-05-12", "stance": "warn", "quote": "Angular, React, Vue.  All terrible reminders of why I try to stay away from the frontend.", "excerpt": "I'm not fond of functional languages. It isn't that I don't get why they are a really good idea (they are). I just can't stand the syntax, the lack of proper standard libraries, and the lack of mainstream-big-ecosystem'ness. Mainstream languages are nice because there is lots of code, documentation, discussion and I can find people I can talk to. And you can write real code in situations where you may not be the one ", "context": "backend developer", "use_case": "frontend development", "switched_from": "", "story": "If AI Writes Your Code, Why Use Python?"}, {"id": 765432401, "item_id": 47839525, "url": "https://news.ycombinator.com/item?id=47839525", "by": "aitchnyu", "date": "2026-04-20", "stance": "recommend", "quote": "I love Vue BTW", "excerpt": "With modern editors `<h2>foo<h2>` is one keystroke more than `## foo`. Might as well tap into the React ecosystem (I love Vue BTW) and get module-organization and DRY, live preview, syntax highlighting, autocomplete, linting, AI expertise etc. There are tools to edit PPTs and movies with React. https://wyozi.github.io/react-pptx/ https://www.remotion.dev/", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: MDV \u2013 a Markdown superset for docs, dashboards, and slides with data"}, {"id": 763865985, "item_id": 47741624, "url": "https://news.ycombinator.com/item?id=47741624", "by": "shakermaker83", "date": "2026-04-12", "stance": "neutral", "quote": "I know Python, Django, Vue", "excerpt": "A little more context of it helps. By day I\u2019m an actuary. I went to school for math and computer science. I know Python, Django, Vue\u2026 am comfortable with pandas, SQL, experimenting with streamlit. All of my industry knowledge is in large insurance companies that have their own internal IT departments. The exact opposite of who will go for a scrappy solo developer. But, I love solving problems, and have always wanted ", "context": "Actuary with math and CS background", "use_case": "", "switched_from": "", "story": "Ask HN: How do you find / validate niches for an online business?"}, {"id": 763844880, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "React", "story": "Why AI Sucks at Front End"}, {"id": 763164146, "item_id": 47697759, "url": "https://news.ycombinator.com/item?id=47697759", "by": "oDot", "date": "2026-04-08", "stance": "warn", "quote": "a deep design flaw in mainstream frameworks like React and Vue", "excerpt": "The problems OP tries to address are unfortunately a deep design flaw in mainstream frameworks like React and Vue. This is due to 2 properties they have: 1. They marry view hierarchy to state hierarchy 2. They make it very ergonomic to put state in components I've been through this endless times. There are significant ways to reduce this friction, but in the end there's a tight ceiling. This is why this kind of work ", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "Show HN: Tired of logic in useEffect, I built a class-based React state manager"}, {"id": 761882307, "item_id": 47617644, "url": "https://news.ycombinator.com/item?id=47617644", "by": "Smrtnyk", "date": "2026-04-02", "stance": "neutral", "quote": "Stack is vue and firebase", "excerpt": "I work at a night club and owner was complaining how it is cumbersom to manage reservations with pen and paper and i thought i might vibe code it. Turned out pretty good so invested few months to further refine it and offer it as a SaaS. I am not here to promote it for someone to buy the product. But you can play with it for free if you want. There is a free trial of 3 months with no credit card needed so you can jus", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "I vibecoded the full event management system with custom floor planner"}, {"id": 758628721, "item_id": 47414295, "url": "https://news.ycombinator.com/item?id=47414295", "by": "murillobrand", "date": "2026-03-17", "stance": "recommend", "quote": "I love the ergonomics of Vue/React", "excerpt": "Hi HN, I've been building an ecosystem of zero-friction, local-first productivity tools called \"That Just Works\". For the UI, I needed something incredibly fast and lightweight. I love the ergonomics of Vue/React, but I didn't want a 40kb+ payload. So, I built Sigwork. It's a 1.7kb (gzipped) fine-grained reactive engine based on signals. Instead of VDOM diffing, components run exactly once. When a signal changes, it ", "context": "", "use_case": "UI framework", "switched_from": "", "story": "Sigwork \u2013 A 1.7kb signal-based reactive framework"}, {"id": 742673296, "item_id": 46417081, "url": "https://news.ycombinator.com/item?id=46417081", "by": "hecanjog", "date": "2025-12-28", "stance": "recommend", "quote": "I used and liked vue for a little while when it was needed(?) but modern HTML fills that gap.", "excerpt": "You sure can! They all have inline defaults like `<span>` so set some CSS baseline on them as needed, but this is like the best kept secret of HTML or something? Unknown tags will become `HTMLUnknownElement` and behave like a span. Edit: the reason for avoiding this in the past was name-spacing. But the standard says you can use a hyphen and then you're OK, native elements won't ever use a `-`. Edit 2: also it's grea", "context": "", "use_case": "frontend framework", "switched_from": "", "story": "You can make up HTML tags"}, {"id": 741026066, "item_id": 46314129, "url": "https://news.ycombinator.com/item?id=46314129", "by": "mythz", "date": "2025-12-18", "stance": "neutral", "quote": "which used to be Vue", "excerpt": "I keep seeing articles religiously pushing htmx, what I'm not seeing are sophisticated examples or apps written with it, just more basic example and interaction examples. I personally prefer UIs with great encapsulation/composition, which used to be Vue, but with AI starting to write more of my UIs now I've switched to React/Next.js for new non-progressive UIs.", "context": "", "use_case": "UI composition", "switched_from": "", "story": "Please just try HTMX"}, {"id": 740360882, "item_id": 46272555, "url": "https://news.ycombinator.com/item?id=46272555", "by": "adapptivlabs", "date": "2025-12-15", "stance": "neutral", "quote": "VueJS in the frontend", "excerpt": "adapptiv Labs, Switzerland | Mid-Level Full Stack (C#, VueJS) | Remote or In-Person | 60-100% We are a bootstrapped software company based in Switzerland providing software for the shop floor in machining industry in the DACH (Germany, Switzerland, Austria region) (everything around digitalisation) and are actively looking to extend our team (currently 2 people) with a developer with experience in C# and VueJS. With ", "context": "bootstrapped software company in Switzerland", "use_case": "frontend", "switched_from": "", "story": "Ask HN: Who is hiring? (December 2025)"}, {"id": 739242208, "item_id": 46202638, "url": "https://news.ycombinator.com/item?id=46202638", "by": "pianopatrick", "date": "2025-12-09", "stance": "warn", "quote": "I didn't like Vue or React", "excerpt": "I didn't like Vue or React so I've been working on my own Javascript framework this year. I wanted to share it at some point as I've gotten value from so many other people's projects. Maybe someone will benefit from my project too. My framework uses an html attribute called foreignkeys=\"\" to hold urls with custom schemes that reference pieces of browser state. When that browser state changes, the framework searches f", "context": "", "use_case": "", "switched_from": "", "story": "A prototype of an event driven JavaScript framework"}, {"id": 738480022, "item_id": 46155001, "url": "https://news.ycombinator.com/item?id=46155001", "by": "HiPhish", "date": "2025-12-04", "stance": "neutral", "quote": "We use Vue as our bundler to compile the JS and CSS as well as to run Storybook.", "excerpt": "That's just for the HTML content though. What if you want to add some non-trivial Javascript or generated CSS? Or maybe you want to integrate a frontend tool like Storybook[0] even if your HTML is rendered server-side? Maybe add some tests for your frontend code? There is much more between raw hand-rolled HTML/CSS/JS and a full-blown SPA. At my day job we use Django with HTMX and Alpine, but we also generate the cust", "context": "", "use_case": "bundling JS/CSS", "switched_from": "", "story": "Django 6"}]}