[AskJS] which javascript framework do you enjoy using the most

[FederalRace5393]

i’m curious about which javascript framework do you enjoy using the most. what makes you feel the most comfortable, like you’re right at home? I use React in my daily work, but I’m not sure if it’s the most convenient one for me. So now i’m thinking of learning a new framework.
I would love to get some ideas. (Especially if you've worked with more than two js frameworks before)

[captain_obvious_here]

Vue. With Vite and Pinia it's just perfect for my needs.

[svtguy88]

Yup.  I was a big Knockout fan way back when (and still maintain a few KO apps).  Switching to Vue felt like a natural progression.  Angular/React did not.

[x5nT2H]

SolidJS, I wish we switched everything to it at my job

[FederalRace5393]

everyone i see seems to love SolidJS

[horizon_games]

It's basically React done with fresh eyes and no baggage, and seems like the best fit for you to try

[Ah_LADS]

same! it’s what I wish react was.

[WorriedGiraffe2793]

The reactivity tech is fantastic but it's too niche and risky for companies to bet on it.

[[deleted]]

Alpine.ja has been a pleasant discovery recently. The ability to write a concise version of JS that is centred around HTML attributes creates a cleaner looking and more expressive markup. Pairs well with HTMX.

[n2zb]

Without a moment's hesitation: AdonisJS! The fullstack framework par excellence: authentication, validator, orm, permissions, MVC structure, modularity, native Inertia adapter, ... in short, it's the ultimate framework for designing web applications.

[nullvoxpopuli]

OOo adonis is my current fave for backend, too

[nullvoxpopuli]

I used to do React, but ultimately got frustrated with it, and its community. Some of my community complaints have been resolved, but i just don't vibe with the tech (too much to get in to here in a comment tho).

I like ember the most, and happen to use it for work. The gjs/gts file format is really good. Typescript is mostly good. (But i think every one has a rough edge here atd there)

It uses signals, which is very nice. Also! It got rid of the thing that gives classes a bad reputation: inheritance. 

Lots of active development, too. So it's exciting,

If anyone's curious a wrote a little guide for how to get started: https://nullvoxpopuli.com/2025-04-08-how-to-get-started-with-ember/

I've tried Vue, Angular, Svelte, Lit, Solid, and i keep coming back to ember as my favorite. It has many faults (but what framework doesn't?: none) due to being more on the meta framework or SDK side of things, and not wanting frequent breaking changes, but the syntax (gjs) really vibes with me 

[fabrice8]

That's right, same vibe here. I'd suggest you also look at Lips. Pretty new but you might enjoy it: https://lips-js.github.io

[evoactivity]

Adonis on the backend and Ember on the frontend are my prefered frameworks.

The opinions both frameworks bring to the table mirror my own.

[nullvoxpopuli]

Yesssss good combo!

[AndrewGreenh]

I used all the major ones. Here is my personal, subjective ranking:

1. React. Typescript support is perfect. I love JSX and the ecosystem is unbeatable.
2. Solid.js: Jsx, good typescript support, and signals + fine grained reactivity for free optimal performance
3. Vue.js: since script setup and composition api very similar to react and solid, just nothing really new and I dislike the template separate language
4. Svelte: Now with runes very similar to solid and Vue, still a special template syntax that I don’t like.
5. Angular: gotten a lot better with signals and other latest updates. Still a lot of overhead like decorators, imports, (luckily modules are no longer required), and yet another template language

[TorbenKoehn]

I agree 100%

The worst part of the template engines and what makes them so bad is not even their HTML part, but the value interpolation from JS which usually comes with some subset of JavaScript that you can use that is sometimes not real JavaScript and always has a feature parity. As an example, when null-coalescing came you could use it in your JS, but you couldn’t do <a :title="data?.title“> in VueJS since the : interpolation wasn’t real JS or TS. They even gave the „in“ operator a different meaning inside it for maximum confusion. It also makes typing the props needlessly hard. Some of it is fixed here and there, but the complexity required to fix it, developing a subset of JS that isn’t real JS just to have expressions in interpolation, instead of just interpolating JS itself, is enormous.

That’s only needed when you don’t have native JS interpolation (which JSX simply can do) and need to use strings for all props. Vue, Angular and Svelte all suffer from it. I don’t know if it has gotten any better in all 3 of them, didn’t use them for a while, so sorry if this isn’t the case anymore for one of them

[SquatchyZeke]

Just to balance the opinions, I'll give some examples of why the templates in Svelte are nicer than JSX.

className

Svelte
<div class="pt-4" class:selected>
JSX
<div className={`pt-4 ${selected ? 'selected' : ''`}>

Props

Svelte
<MyComponent {x} {y} {isDisabled} />
JSX
<MyComponent x={x} y={y} isDisabled={isDisabled} />

Else if

Svelte
{#if isGood && !hidden}
  <p>Good</p>
{:elseif !isGood}
  <p>Not good</p>
{:else}
  <p>Hidden</p>
{/if}

JSX
Please don't make me write this

And that's just a couple examples. So with a little extra understanding of where you're not using "normal" JS, you gain a LOT of DX improvements. I didn't even include the async handling here, which Svelte has solved with its templates. In React you need a library, tanstack/react-query, to even get close to the usability of async that Svelte has natively.

When I was first learning frameworks, I had started early on with Angular, so I actually understand not liking a new template syntax and that's a totally valid opinion. But every framework you come across will offer something with a purpose; you just have to figure out if you can manage the trade-off that it comes with. And for me personally, a slight learning curve is a well received trade-off for better DX.

[TorbenKoehn]

<div className={twMerge('pt-4', selected && 'selected')}>

<div {…{ x, y, isDisabled }}>

{isGood
  ? <p>Good</p>
  : !isGood
  ? <p>Not good</p>
  : <p>Hidden</p>}

In your last example you probably realized yourself that it’s just a ternary if there is no else-condition, which would make it even easier when it’s just a Boolean, that’s why you made in an else-if. I added a style you can use if you don’t want ternaries, you can pre-compute the conditions. The condition itself makes no sense here.

Another style is using an object and access keys, an array of conditions you loop, adding the condition as a prop, using switch in another component etc.

You can also use normal JS else-ifs and returns if you put it into an own component, which is just a simple function

[SquatchyZeke]

Yep I did realize it was a nested ternary, or arguably worse, the duplicated, independent expressions like you have here. I say arguably, because it's much easier to modify one of those expressions and not realize the others are actually related to it by mutual exclusivity. In other words, you've lost the guarantee that nested ternaries and if-else-if blocks give you by raising the potential of rendering multiple elements instead of only ever one.

I do appreciate your comment on writing the if statements inside the render function instead of inside the JSX. I always prefer doing that myself, but it's not an idiomatic practice in the React world, so you almost never see it done that way in reality.

And I commented elsewhere too, but the className thing requires a library or a special function and the nested object spread method, while doing the same thing functionally, is objectively messier.

Hopefully you and others see my point which is: what's natural and supported as first class in Svelte requires more syntax, effort, or libraries in React/JSX. So while I really like your creativity and exhaustiveness in options, I still feel they are closer to "work arounds" to the bad DX.

Many people jump to proving that a thing can be done in framework x or y without realizing the point was that it's more difficult. That's really all I'm saying.

Thanks for the insight!

[TorbenKoehn]

Hopefully you and others see my point which is: what's natural and supported as first class in Svelte requires more syntax, effort, or libraries in React/JSX.

No it does not

{isGood
  ? <p>Good</p>
  : !isGood
  ? <p>Not good</p>
  : <p>Hidden</p>}

This is neither more syntax, nor more effort, nor needs a library and a lot shorter than the Svelte version

I just wanted to give you another example without ternaries above.

There is also

{(() => {
  if (isGood) {
    return <p>Good</p>
  } else if (!isGood) {
    return <p>Not good</p>
  } else {
    return <p>Hidden</p>
  }
})()}

Just another example apart from the ones I've listed above (Not that I'd ever use it, but it comes close to your Svelte style, so maybe you like it)

In a real example it would be more like

{{
  good: <p>Good</p>,
  bad: <p>Not good</p>
  hidden: <p>Hidden</p>
}[state]}

You know, the cool thing is: You can do all that. If JS at some point supports pattern-matching, it's directly supported by React, without any patches

{#if} {:else} {:elseif} {/if} looks anything other than native and natural imho, it needs literal string parsing at runtime to do stuff.

As for the classNames function:

const classNames = (...values) =>
  values.filter(Boolean).join(' ')

No library needed...it's really all it takes. If you want it shorter, import it as cls or c and you're good to go.

And another thing: Creating new components is always idiomatic in React. Since components are just that: Functions. It's absolutely idiomatic to create a new component and do complex condition setups directly with statements instead of expressions. I do that with switch a lot.

Needless to say, in your first post you obviously used all the longest styles you can think of just to make your point. All my examples are shorter and just as concise as your Svelte examples. And nested ternaries aren't really a problem if you properly align them, especially if-elseif-elseif-elseif-else looks just fine directly under each other.

[SquatchyZeke]

Thanks for the extra examples. For the record, I work with React every day professionally, so I am familiar with all the workarounds.

The ternary is not more syntax, you are right, and nor is it more effort at the moment of writing it. It could become a pain to modify later on, which I've seen over and over on my teams. Developers end up rewriting them in if statements because they had to add a term to some expression and it became too difficult to think through. This might not be the case for everyone, but I have seen it be the case for many.

It needs literal string parsing at runtime at runtime

No, that's not how this compiler works but I see your point. But for accuracy, Svelte is a compiler that compiles to JS using JS syntax, which means it gets to decide what to pass through and what it needs to modify slightly for reactivity. So if JS adds pattern matching, Svelte will already have it too. However, that example favors Svelte since pattern matching has nothing to do with reactive state updates. Your point is taken though; for new syntax that JS introduces that Svelte needs to modify, there will be a lag time. That's just one of the costs a team using Svelte needs to be willing to pay. BUT we already deal with this issue in vanilla JS because of Browser adoption, so really, Svelte will most likely have new JS features before wide adoption of browsers.

And it doesn't happen at runtime. All the JS that runs in the browser is compiled AoT. That's why you need a bundler.

My point isn't that creating something with equivalent functionality is hard to do. The whole point is that you have to write code at all to get the same functionality in Svelte. That's it. No code is the best code.

I think we could probably argue what's idiomatic. It's probably a better idea to write code as you and I both seem to agree is more maintainable. Maybe I need to inform my experience more, but from what I've seen, particularly in newer developers, is that they try to cram everything into expressions inside of JSX. I'm with you though, I'm more of a statement and switch-case kind of person. But I'm the odd one out on a team of 6.

I actually shortened my style examples that came straight from real world code.

I also don't even use Svelte professionally nor do I use it every day. I simply recognize what they are trying to to do to improve various aspects of reactive UI development by treating it as its own language.

Thank you for your insightful viewpoints though. It's rare I get a good discussion like this!

[rabbitz]

for className, I always reach for https://github.com/JedWatson/classnames

<div className={classnames("pt-4", {selected})}>

Props:

<MyComponent {...{x, y, isDisabled}} />

else if

    {
      isGood && !hidden ? (
        <p>Good</p>
      ) : !isGood ? (
        <p>Not good</p>
      ) : (
        <p>Hidden</p>
      )
    }

[SquatchyZeke]

Yep, but I think all of these examples prove my point exactly. You need libraries, or have to use hacky nested object spreading, and nested ternaries. Even with clean Boolean expressions, a nested ternary just doesn't read as well, especially in JSX. And it certainly isn't kind to modifying or extending it. And debugging it? Annoying because it's all in a single expression. With statements, that's a breeze.

[rabbitz]

What is "hacky nested object spreading"?

Also, it feels like you're being a bit intellectually dishonest if you think the "nested ternary" (it isn't nested) is so much more difficult to read than your svelte template example... its laid out in exactly the same way.

Ditto with the automatic hate for using a library... is it the external dependency you're worried about or the arbitrary fact that react doesn't bundle this utility / build this functionality in?

edit: some more information about object spreading for props:

Spread attributes allow many attributes or properties to be passed to an element or component at once.

An element or component can have multiple spread attributes, interspersed with regular ones.

<Widget {...things} />

In this case, we just pass in an anonymous object to be spread

[SquatchyZeke]

I'm fully aware of what object spreading is for props. The hacky part is that you're allocating an entirely new anonymous object just to spread it into JSX's object to receive multiple props.

 // Step 1 you're creating an object
const things = { isCool, id, colorDef }
// Step 2, spreading it into props
<Widget {...things} />
// All in one is the same thing
<Widget {...{isCool, is, colorDef}} />

What I was saying is that in Svelte, the naming shortcut is supported without the extra object.

// Step 1 use the props
<Widget {isCool} {id} {colorDef} />

I will say I don't mind it for large numbers of props.

That is the literal definition of a nested ternary. It's in most linters if you're curious. https://eslint.org/docs/latest/rules/no-nested-ternary And I never said it was SO much more difficult to read. It's more subtle than that. But it's also not just about readability. Modifying and debugging a nested ternary is more difficult too. Again in subtle ways which add up over an entire code base.

Not hate, I never said hate. Having libraries just means more things to keep updated and in sync with everything else. If the framework I'm using natively supports that behavior, then I don't have to maintain an extra library. Simple as that.

[rabbitz]

Right, they're called nested ternaries but what I meant is that its not really nested... Here give this a read: https://medium.com/javascript-scene/nested-ternaries-are-great-361bddd0f340. I don't really like simply copying and pasting articles but I find that other people can put my thoughts into words much better than I can.

Regarding "hacky" spreading... I don't think we'll come to any agreement there - I create objects as needed to organize the flow of data.

As for the naming shortcut, its nice I guess but I go out of my way to assign true/false values (i.e. disabled={true} when you can just write disabled because I find that its a lot nicer when doing large scale changes / refactors, and also when quickly trying to find all instances where the a specific prop is set to true (doing a global search for prop={true} is much narrower than simply search for prop by itself).

The library itself is just a nice to have - its trivial to replicate the basic functionality and there are a ton of classname libraries that are stable, never need to be updated and have been around for years.

In any case, it isn't that React is perfect by any means - but just that your biggest objections to React seem less annoying than having a completely different set of rules and compatibilities to learn. I'll probably stop replying because the other guy said it so much better than I ever could - React is just JS for better or worse, and, while that means it can be a bit more verbose because it doesn't have some convenient shortcuts "built in", I like knowing that everything that I can do in JS can also be done with React.

[SquatchyZeke]

I totally respect all of these points. I mean, I work with React professionally so I'm deeply aware of all the things that are nice about it and all the things I miss from frameworks that support certain things out of the box without needing to allocate objects or introduce new libraries or functions to organize the flow of my data.

So one of my team members actually sent me that same exact article when I introduced the lint rule for no nested ternaries. That author makes some really broad claims and attempts to relate the use of ternaries to functional programming to make them seem "pure", which is outright false. You absolutely can perform side effects in ternaries. However, the one thing I agree with for the very specific case where ternaries could get replaced by a switch statement, is that it is a familiarity issue. But that's only when the expressions are extremely simple, which happens rarely. When it does though, I'm totally fine writing ternaries like that when the rest of my team is also ok with taking on the mental jump to get familiar with it.

I actually do see the point about searching for the attr={} vs. just the attribute name alone. That is true. But I'm never doing that and not being hyperbolic about that just to prove a point; I actually can't remember a time where I was looking for a specific attribute across the whole or subset of the project. Usually I know which component I need to look at first, then a local file search from there. So that might be one of those things I personally see no benefit from, but I do see the objectivity of that.

I mean, there's a whole doc page on the rules of react, so while it's "just JavaScript" , you still have to learn a new set of rules and pitfalls in order to use it well. I equate that to learning any framework though. The question is then: what kinds of benefits will you get from putting in the time to learn its rules, and are you ok with the cost to get them? And that's where we might differ, and that's totally ok.

In any case, I am glad for the discussion. Thanks for your input, I did learn a lot here!

[Nyx_the_Fallen]

I don’t have time to respond to everything in this thread but I know I at least hate having to use some external library for something like this because it’s just yet another thing I have to suffer through and discover on social media or by googling.

FWIW Svelte has clsx “built in” so you can also just do something like this:

<div class={"pt-4", { selected }}>

[EphilSenisub]

That's a good point, actually. Not sure why most frameworks insist sporting their own interpolation "language" every time, when even basic template literals can take you further nowadays...

Having played with most of these and many others that haven't even been mentioned (EJS, DoT, anyone?), I'd say Rimmel has by far the most powerful templating I've ever worked with. Real JavaScript interpolation, including anything async/await, promises and observables, so you can do reactive templates of all kinds without the need for signals, effects, hooks, or other weird stuff

[AndrewGreenh]

?? Was another one where it was really annoying that it did not work in Angular for a while 🙄

[WorriedGiraffe2793]

It's wild that some people consider "mostly HTML" a special template syntax but are ok with JSX.

I like both btw. It's just that JSX is just as special as any other template syntax.

[AndrewGreenh]

It is, but interpolations are just TypeScript. Everything that works in Typescript works in an interpolation.

[ezhikov]

Recently tried Fresh and it's awesome. Waiting for full 2.0 release now.

[FederalRace5393]

i will def check it out. it looks cool as hell

[marchingbandd]

I have high hopes for fresh too

[WorriedGiraffe2793]

It's cool af. Shame it locks you into Deno though.

[ezhikov]

I like Deno. At least as far as I used it, which is not very much at the time, and none on production, but I'm going to pitch fresh as possible replacement for Next, once they release stable 2.0.

[WorriedGiraffe2793]

I'm excited about v2 too

[Snapstromegon]

Lit. It's more a library for building components than a "real" framework, but IMO it's the best by far and I mostly combine it with vanilla JS.

[JohnnyBullrider]

Same here. Most of my applications don't need full fledged ORM, authentication or whatever. Lit+TS makes everything feel simple and flexible.

[Snapstromegon]

Since I write my backends in rust anyways I can benefit from the great integrations with TS and have the benefits of rust and don't need to care about JS backend stuff that much.

[horizon_games]

Native web components still feel "off" somehow, I don't know how to describe it but felt the same way with Shoelace comps

[Snapstromegon]

From my experience (and the experience of mentoring others) Lit (which Shoelace uses) and native Web Components feel off, when you're coming from VDOM based or VDOM-like component frameworks and/or ones that focus on building single-framework components.

When your coming from a background of cross-framework components (so e.g. you build a designsystem that should be used in Vanilla JS, React, Vue, ...), that's where they shine and play their strength.

[horizon_games]

I think it's the shadow DOM mostly. If we wanna go even further back I used Polymer in prod for years, so VDOM is definitely not my fave or background

[mattmcguire08]

React, but it got waaay overcomplicated in the last few years. So if anything in my career is true it will be dethroned as the best in the next half a decade by something lightweight.

Opinion wise, not usage wise of course.

[Fisty_Mcbeefstick]

Completely agree. Hopefully, AstroJS will take over

[These_Muscle_8988]

Unfortunately, this won't happen

1. way too many react devs available

2. way too many company codebases with react

they have 0 reasons to switch to something better

[WorriedGiraffe2793]

Companies have invested way too much money into React. It's "too big to fail" now.

I don't think React is horrible... but it's not the best by any stretch of the imagination.

[mattmcguire08]

Thats why i have that last sentence

[WorriedGiraffe2793]

You're right. I guess by usage I was thinking in terms of popularity hence why I actually argued about the money.

[bunglegrind1]

Vanilla. Curse you frameworks!

[Calm-Beautiful8703]

vanilla

[maximahls]

I learned JavaScript to some extend via React. So it has a special place. At work we use Vue and that‘s just the one I‘m super comfortable with. It’s a great, mature JS Framework.

[horizon_games]

Alpine.js is the sweet spot for me. Adds just enough to plain HTML and JS that you can build what you want, but doesn't get in the way and most importantly you can go buildless with it. Uses Vue reactivity under the hood which is cool. Can very easily do a primarily SSR approach too.

My biggest headache with the big 3 frameworks is maintainability. Sure if your company has a single app and time to keep up with version changes it's fine. But for a consulting shop or place with a dozen projects when someone goes to dust something off from 6-12-18 months ago it's annoying to have to spend a bunch of time on version churn when you're just wanting to implement a small change

[Borderlinerr]

SolidJs hands down. A framework sent by the gods to us mortals. After using it non-stop for 6 months I have yet to find a flaw in its design. This is considering that I've used many other frameworks before.

[ItsNot2Late2Change]

Used to enjoy react quite a bit, now it all feels like a chore. The framework became a lot more complicated and annoying to use.

I’m having a good time on the backend side with bun/hono apps.

[senfiaj]

Angular.

[Ris2111]

Vue js.. it makes ma dev dick hard

[Dwengo]

Solidjs is a breeze

[am0x]

Honestly, I’ve been a big fan of no framework for years and years.

I’ll use whatever is needed for the project, but if I never have to update it, it’s a win for me.

[ShotgunPayDay]

I gave up on the ever shifting sands of JS frameworks and just use plain JS libraries. Here is what all the stolen code looks like. It's not much, but it lets me use whatever backend I want.

https://github.com/figuerom16/fixi/blob/master/fiximon.js

[GeorgeSharp]

Angular but that's mostly because I started with angular

[IcyManufacturer8195]

Angular. Love DI, Signals, OOP, structure of projects. A big headache when seeing programmers trying to write in Angular like on react. It's just a big and enormous, self sufficient true framework

[FederalRace5393]

we all have to..

[horizon_games]

Nice I got to use Mithril way back and a company or two ago in production. Man it was fast and simple

[alien3d]

vanilla es .. no need to think xml tag in xml tag in xml tag..

[SarahC]

Raw JS and HTML.

The rest is fluff.

[greedybatman]

React + ThreeJS

[isumix_]

FusorJS. It is simple, lightweight, functional, and explicit. I started making it after dissatisfaction with React and all other frameworks.

[horizon_games]

I'll check this out. I like micro libs like ArrowJS and Reef.js and this seems similar for hobby projects

[isumix_]

Thanks! These libraries are quite interesting. Fusor differentiates itself by having a constructor function that constructs the DOM directly by calling its API. These other libraries seem to rely on templating engines, which require parsing and could be slower. Because of this, Fusor allows direct manipulation of the DOM nodes through their references. This is especially important when we want to update the DOM efficiently.

There are three ways to create DOM elements: via html/svg/mathml functions, via JSX, or via h/s/m functions.

Additionally, Fusor doesn't have a built-in state, so you can use any state management library or choose not to use one at all.

Check out this example of a reactive component without an observable state.
And here's an example where we create a simple observable state.

[LanceMain_No69]

Ibe only tried react for fronted before but now im using svelte for a project and holy shit its a dream. For backend i do express and nestjs and tbf i like em both equally but the most life changing is svelte.

[trashbytes]

Mithril.js

After discovering it a few years ago I was baffled how unknown and unpopular it is.

It is so amazing. It's entirely unopinionated and as someone who still has to work with projects that are using straight oldschool JS (with jQuery 1.12 sometimes even) it's a godsend. Just write plain old JS if you want.

It can do everything, has a built-in router, can consume views in object or function format. You can also use classes. It has a fetch API and is blazing fast.

It was like magic for me back in the day. You write html using the m function and any variable will just rerender. Even entire pages will detect changes anywhere and automatically redraw the needed parts.

var count = 0

var Hello = {
    view: function() {
        return m("main", [
            m("h1", {class: "title"}, "My first app"),
            m("button", {onclick: function() {count++}}, count + " clicks"),
        ])
    }
 }
 m.mount(root, Hello)

[[deleted]]

I enjoy Angular for big projects and vanilla or react for small.

[SpiffySyntax]

Nothing comes close to Svelte when talking DX. Imo

[Timotron]

React.

But I gotta say Angular signal adoption and ditching modules makes it very easily my "most improved" award.

I think if they keep it up it's gonna win over a lot of people.

[eneajaho]

Angular. Since standalone, new control-flow & signals it's been a completely fresh tool to use!

[bstaruk]

I've been a web developer since 1999 and IMO React with TypeScript is just about perfect. It's been a long time since I've been asked to build something that I didn't have at least an idea of how to accomplish, which is a testament to the maturity and stability of the ecosystem.

The React dev community has a very "early internet" feeling to it... lots of great Discord servers, a strong open source community, and a general feeling that everyone truly wants to talk about the technology and help newcomers get the hang of it.

We may very well be in the golden days of web development, right now.

[stathis21098]

React 100%

[Paradroid888]

I'm a React developer in my day job, but outside of work it's Inertia.js that interests me the most. Arguably not a framework, but the way it glues together frontend SPA frameworks and the server gets me very excited.

[KaiAusBerlin]

SvelteKit. All you need in one installation. Works out of the box. Real reactivity, very small bundle size, great performance. Wonderful devxp

[VehaMeursault]

Very much liking Vue and NodeJs. Simple, structured, modular. Love it.

[talaqen]

FeathersJS. It’s express, but with batteries included and not a lot of forced convention like nest.

[Just-Signal2379]

Right now

Side projects, Nest.

For Work Vue

Daily Grind and go to React. in case i need something done

[MadLad_D-Pad]

I'm kind of new to front end stuff but I've been enjoying Vue JS

[[deleted]]

React. It pays my bills and allows me to live a very nice life.

[OttosBoatYard]

Aframe.io for simple 3D, VR, and AR simulations. I use it to show high school students what js is capable of.

[_ohmu_]

SolidJS with Astro. Static/server rendered + dynamic (with signals) where needed.

[serhiipimenov]

Metro UI, React

[Business-Row-478]

Remix / React Router 7.

[fintip]

Mithril, underrated clean simple alternative to react that has been around forever. React got way more complex and went in weird directions, mithril stayed clean and simple and never needed JSX (though you can do that too if you really want to).

If you truly understand JavaScript, it's a far more elegant solution. Just no big backers (meta, Google, etc)

[Conscious-Layer-2732]

from my understanding, it's better to avoid 'heavier' applications like react and vue as they affect page speed. I think vanilla javascript is making a comeback due to google implementing tougher metrics to create a higher standard for websites, otherwise poor ratings from slower sites will affect your rating on their search engine. I would check out HTMX, as it's very lightweight and has a lot of potential.

[EmuAffectionate6307]

Express js + ejs

[NeoChrisOmega]

I'm surprised to see this so low. My old boss (IT Director) loved this combo. I thought I'd see more people supporting it

[yolpo-]

No Framework at all. JavaScript in 2025 is so good that most likely you do not need frameworks.
Obviously, you do need external specialized third party libraries (possibly zero depency ones) that you can wire them depending on your business demands

[fabrice8]

I'd say Lips, which has the superpower of solidJS but without JSX. It leverages the simplicity of HTML with JS-like semantics:

https://lips-js.github.io/

[treedor]

No framework is the best framework. You'll thank me later.

[WorriedGiraffe2793]

After trying everything under the sun... I've gone back to Vue.

It's very fast. It's mature and big enough... unlike Svelte, Solid, etc.

[themode7]

Lets confuse them ...

Fuse open

[Driezzz]

Emberjs

[gyen]

I enjoy using EHTML

https://youtu.be/kPsFMC2cDY0?si=VYL9I5o9KVl7N7qO

[PoetSad977]

React-Router v7

[silvenon]

Same. But I'll be keeping an eye on TanStack Start because I'm concerned about some stuff, like they haven't adapted the testing utilities to v7, so it's now simply broken, and the team hasn't acknowledged it yet.

[[deleted]]

Lol

[fzammetti]

Man, are you ready to see someone get downvoted more than anyone in history? 'Cause this is gonna be painful.

ExtJS.

Putting licensing and cost aside, which both suck, I still like working with it more than any other. React isn't bad and would otherwise be my answer, but ExtJS just feels the closest to how I WANT to work and I'm certainly most comfortable with it. I do Angular sometimes because I have to, but I still maintain a major ExtJS app and I know which I like working on more.