TL;DR
Which framework should you use? Well, that depends on what you're developing and your prioritie are. But I made a quick comparison...
For further actions, you may consider blocking this person and/or reporting abuse
"almost" predictable but still a cool way of spelling Alicia.com ;)
Great insights, Alicia! Your framework comparisons are incredibly helpful for developers navigating their options.
Not to be a negative nancy but this article is extremely fishy. First of all congrats if you actually did this but I find it very hard to believe someone actually had the time to build a real app in every framework even over 12 years. The micro ones for testing ? Sure. Secondly, the tone of the article screams AI to me. To much witty coding jokes and humor/witty comments. If English isn't your first language then I apologize! However, how does one write a huge witty article about 12 years of their life but leave in 27 spelling mistakes that I noticed right away. You didn't even edit the blog once ? Extremely fishy. I think this might be (without deep diving the code) ai generated. Just some criticism if this is real no offense 😆.
Nah, it's fine - i get the skeptisism.
But I can assure you, no AI. (and most the code i wrote pre-2020 / pre-chatgtp, and have just been maintaining since). But, u can check the code if u like, it is all on github github.com/lissy93/
Tone of the article is just my normal writing style. I am British, and dyslexic (not sure which one of those is a worse disability, lol).
Yeah, i know it's not very profesionally written, but I spend all day at work pretending to be profesional, so I enjoy having a break in the evenings 😅
Just to add just because i don't want to be mistaken for an AI, so some facts/stats:
Hey! I appreciate the very honest and real reply. You never know in todays world of AI slop. I of course don't make perfect articles or summaries either (and plenty of spelling mistakes). Congrats then thats very impressive and lots of dedication! I completely understand not caring as much about the blog as the real work. Its just like how comments and documentation are often overlooked among developers. Its true! It doesn't matter as much. But I sadly only have time to read this article. Deep diving into code would be the more proper way to handle my response but I appreciate you accepting criticism :)
Awesome overview! The "Stack Match" tool and the framework benchmarks repo are also impressive ...
"Which framework is truly the best?" - I think speaking for yourself that would definitely be Svelte?
And yeah, React is what we use because in many cases we "have to" ;-)
I do love me a nice bit of Svelte 😉
What an experience, thanks for sharing !
This is awesome! I’ll be referring to this post every time I want to start building something
Oh wow I am super inspired. I wish you the best!
how do you learn that many things ? cool as hell
By having no life 😅
Ha ha, but if you learn properly how the browser works, and the ins and outs of JavaScript, then picking up and using a new framework isn't much more complicated than just reading the docs. Most of them are actually quite similar!
thats amazing
This looks like a lot of work went into this comparison. Thank you very much for this! Well, and opinions can be discussed of course :-)
Commenting on my own post here, because I am anticipating people saying "Wait a sec mate, you've not included ____"
Unfortunately it wasn't really feasible to cover everything, and things which are either declining in usage, augment other frameworks, or take a completely different approach have been left off for brevity. Here's a summary, and my reasoning for this:
Older Frameworks
I do have to give a shoutout to these frameworks, which played their part in laying the groundwork for what we have now: Riot, Radi, Stimulus, Imba, AMP, Mithdrill, Hyperapp, Rax, dva, Omi, Neo.mjs, Crank.js, Polymer, Inferno, Ember, Hyperapp, Cycle.js, Stencil and Relay
This isn't to say that these project are dead, but more so that the features and notions have been further developed by the frameworks listed above.
Many of these I either used, or played around with (back in the day), and I see concepts that they've invented being refined and bought back by the modern frameworks we use and love today.
By it's very nature, frontend development changes rapidly, and as such so does the tooling that we use.
If you're concerned by the thought that something you learn today, may not be relevant tomorrow, here's my thoughts:
Meta Frameworks
I've not mentioned meta-frameworks (except Astro), which provide an additional layer of abstraction, giving you certain essential features like file-based + API routes, SSR, + SSG. If you're interested, let me know below as I'm happy explain more, and share my experiences of using these.
But in short, if you're building a larger app then using a meta-framework can save you time, give you an improved developer experience, simplified setup for larger projects and out-of-the-box performance optimizations and integrated best practices.
Though the extra overhead usually isn't worth it for mini apps and small SPA projects (IMO).
Some popular examples you may have come across include: Astro, SvelteKit (for Svelte), Nuxt (for Vue), SolidStart (for Solid), Next.js, Remix, Gatsby (for React) Analog (for Angular), Qwik City (for Qwik).
Non-JavaScript Frameworks
Using a frontend JS-based framework is not the only way to build web apps in 2026!
I didn't have time to go into these here, but if you're interested let me know and I'll write another post.
But in short, here are the main alternatives:
Wow great stuff!
And epic domain...
Bring more such articles!
Hi, this is absolutely awesome, i mean experiencing all these technologies, which seems to be like life-time to me.
Thanks for this post.
I am using react and vue, more skilled / experienced in react. Sometimes, if i have some gap time in developing in Vue, i find it cumbersome to get used to the differences between react and vue.
Imho, devs might have preferences and in regard to these, might be more skilled in one than the other, in parallel to the time they spend on these tech of course. On the other hand, it seems to me that, the selection of a tech (especially a JS framework) mostly depends on the experience and preference of the team or organization. I think that not many devs have the similar experience in working with so many variety of techs as you do.
Best,
Thanks for sharing and i totally agree with you on Angular i have been using it for large app is amazing everything i need in frontend is one place the Angular way,for large app standard structure and consistency matters as any one can onboard easily everything stay where they are suppose to stay hahaha, Angular is really give me a good developer experience,upgrade straight forward to large codebase hahaha thanks once again and Happy New Year
Ripple?
At first I felt a tiny bit of inner resistance - like, how can someone write such an insanely awesome post? 😄 And wait… that many frameworks? I thought I knew a lot, and it turns out I really know like four well!
Then I checked out your website and GitHub and just… WOW. Those frameworks are only a small part of your contribution to the community - that’s incredible!
You’re absolutely inspiring. Of course I’m hitting follow and I’ll be waiting for more posts! 😊
Thank you Sywia 🩷
I've followed you back :) x
Check streamlit, nicegui
Thank you!
Missing Phoenix framework.
That's awesome !!!
Love your website domain name. Awesome article.
This is great, thanks!
Wow I loved this article very much! Learned a lot of frontend frameworks!
Absolutely amazing. It's made me feel pretty lazy to only have learnt a few frameworks! Must have taken ages to put this together.
Super refreshing, no hype - just real-world builds + honest trade-offs.
The benchmarks + Stack Match make this insanely useful for anyone choosing a frontend stack