Ask HN: What framework/tools to use to build front end in 2023?

I mean this is the obvious answer but React has the largest market share I would think, and so if you are a large enterprise that deals with employee churn and you think you will struggle to find and hire good talent, React is the framework&#x2F;library that is the most common, and therefore likely the easiest to hire for and maintain over time.<p>It is what bootcamps teach and what most people end up learning.

React is probably what many would recommend, but since you said <i>enterprise</i> then please do consider Angular.<p>It is not as trendy and cool as React, but I&#x27;ve used angular a lot in enterprise scenarios and it has a lot going for it: everything you need is already built-in so you do not need to pull in endless crap via NPM that you now need to review&#x2F;manage&#x2F;check-in (i.e. you just have one dependency), it is relatively stable without many breaking changes over time (and the tooling typically auto-upgrades your code via `ng upgrade` when there are - no other dependencies need to have their upgrade managed at the same time), it has all the same bells and whistles as everything else (SSR, vite etc), on-page performance is about as good as everything else, it has a mature and accessible Web UI component library, and it is backed by Google who employ people to actually work on it. Just pick Angular v17 or whatever and get stuff done.<p>Unlike react that relies heavily on loads of third-party frameworks, Angular genuinely is &quot;batteries included&quot; so you can just start building without making endless choices and refactorings whenever your routing framework changes, or there is a security bug in your now-unmaintained form validation library, or that reactivity library is now incompatible with your local storage framework but you can&#x27;t upgrade because it is incompatible with the current version a11y helper library you need to use for legal compliance reasons, or you need to change your CSS library because the UX folks prefer the padding Vs Tailwinds etc.<p>They also just launched a fancy new site too: <a href="https:&#x2F;&#x2F;angular.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;angular.dev&#x2F;</a>

I&#x27;ve seen a client successfully modernize a legacy web app from jQuery to HTMX.<p>I&#x27;m also seeing more and more Svelte in enterprise app clients. It&#x27;s still small but growing. I&#x27;m curious on how the transition to Svelte 5 will pan out when it comes to adoption.<p>But the best answer usually is: Whatever your team is more comfortable with or comfortable learning.

Use what your developers are familiar with.<p>Also worth asking the question: does your project even need a frontend framework?

HTML and JavaScript. If this is truly and enterprise project, whatever you pick of the current crop of JavaScript frameworks will be long gone by the time your application will get a new refresh or seizes to be.<p>React or Vue might be around in 15 years, but they&#x27;ll certainly look vastly different. So unless you have a continues budget to stay up-to-date, with room for the occasional rewrite, your developers will be stuck on &quot;old tech&quot; in a few years.<p>This may not be a web application, if not: WinForms. WinForms will survive another decade or two and will get no new features so it&#x27;s a stable development platform.

Svelte&#x2F;SvelteKit is currently killing it in increasing popularity. It is easy to learn and fixes design patterns around some of React&#x27;s hard to learn and long to type patterns like state management and reduction, and integrated server-side rendering.<p>I recommend to take a look<p><a href="https:&#x2F;&#x2F;svelte.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;svelte.dev&#x2F;</a><p>Naturally it is smaller and newer than React. But innovation is born from the fact people want to make something better than React.

We&#x27;re a six man back end&#x2F;data eng Python team tasked with building a small public-facing webapp. We went with React, specifically create-react-app, because it was the fastest way forward and has a lot of community&#x2F;network effect. As others have pointed out, it&#x27;s relatively easy to hire for.

Rust on nails. <a href="https:&#x2F;&#x2F;rust-on-nails.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;rust-on-nails.com&#x2F;</a>

aws-gocljs:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;nathants&#x2F;aws-gocljs">https:&#x2F;&#x2F;github.com&#x2F;nathants&#x2F;aws-gocljs</a>

Plain React with Vite. Don’t need much more than that.

Vercel&#x27;s website (vercel.com) is just MIND-BLOWING. Like if y&#x27;all know their develop.preview.ship. animation, it was nuts. How do people even think of such things!

I&#x27;m for Vue&#x2F;Nuxt. While reading React code is fine, I found it easy to shoot myself in the foot (causing circular effects or getting no reactivity) in a way Vue didn&#x27;t. Vue feels more explicit. I like React&#x27;s TSX for embedding HTML, but Vue&#x27;s splitting of model and view appeals to me. I&#x27;m torn on that one.<p>Vue&#x27;s ecosystem isn&#x27;t as big, but it&#x27;s an established framework. Both React and Vue feel easier to work with than Angular. RxJS is really cool, but also very comprehensive, making it difficult to keep the entire API in mind. At least for me, who only use it casually (used to use it more while at Google.) And on top of that, I have to know the Angular API. Angular used to be great for Material Design, but I nowadays there are MD packages for all systems.<p>Nuxt is for Vue what Next is for React: SSR and SSG. It adds auto-imports, which is nice. At this point, I see no reason to use Vue alone, since there&#x27;s always something that can be pre-rendered. Perhaps the frontpage, or help pages. Since Vue itself provides entrypoints for SSR, Nuxt is more of a file-structure based router that just simplifies things. The documentation is a bit sparse on e.g. the difference between a plugin and a module, and I usually resort to navigating their source to understand things. That might not be everyone&#x27;s cup of tea.<p>If what you&#x27;re writing is a web app, there is also Quasar, built on top of Vue. Similar to Nuxt in that it ties in directory structure, build system and MVC framework. It is also a Material Design UI widget library. Their selling point is that you can build mobile apps, and web apps with the same library. I.e. like React Native. I felt it strays too far away from the core simplicity of Vue, unlike Nuxt, but it&#x27;s no doubt a very capable framework.<p>Finally, I&#x27;m currently using PrimeVue as the UI widget&#x2F;theming library on top of Vue. It&#x27;s okay. :\ Switched to it when the Vue Bootstrap project decided to to support Vue 3 (or whatever the situation was.) I haven&#x27;t come across anything that&#x27;s actively broken or missing. The companion library PrimeFlex provides layout CSS. Annoyingly, they&#x27;ve decided to close GitHub FRs, and some (far from all) bugs, and just keep track of them internally. Makes it more dificult to communicate, but I don&#x27;t know their reasoning behind it (they didn&#x27;t respond when I asked.)<p>* <a href="https:&#x2F;&#x2F;vuejs.org&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;vuejs.org&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;nuxt.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;nuxt.com&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;vitejs.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;vitejs.dev&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;primevue.org&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;primevue.org&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;primeflex.org&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;primeflex.org&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;quasar.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;quasar.dev&#x2F;</a>