|3 days ago||4 days ago|
|MIT License||BSD 3-clause "New" or "Revised" License|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Angular vs. React vs. Vue.js: Comparing performance
16 projects | dev.to | 6 Sep 2023
Vue has a thriving ecosystem with a wide range of third-party libraries and plugins available for extending its functionality. These libraries cover everything from state management to routing, making it easy for developers to find solutions to common problems and enhance their development workflow. As of this writing, Vue has 200k GitHub stars.
Top 10 "Must Have" Repositories for Web Developers
6 projects | dev.to | 11 Jul 2023
Vue 2 vs vue 3 - The Differences
2 projects | dev.to | 5 Jun 2023
I have got the privilege of working on Vue 2 couple of months ago and its really amazing framework to work with .
Angular v16 Is Here
6 projects | news.ycombinator.com | 3 May 2023
Angular is as little innovative for web frameworks as Firefox-ESR is for browsers. It merely keeps copying features from other frameworks - just many years later. It is a chronically outdated framework that always struggles to keep up with its competitors. It would be ok if those were deliberate design decisions, but if the features get copied some day anyway, what is the point? Why not do it the right way from the start?
For example, this update brings us computed properties, an essential feature for any complex performant web application that was made popular by Vue.js 10 years ago . And now in 2023 we get it in Angular, essentially a confirmation by its devs that its lack has always been a design error.
I also cannot understand the "mature" argument. For example, it took five years for documentation on `` to arrive . This is something I'd expect from the side project of a lone programmer, not an enterprise-level framework.
The only upsides of Angular are its "batteries included" approach and the (debatable) default of RXJS, while the downsides are plenty.
What's happening with the forum?
2 projects | /r/vuejs | 13 Apr 2023
It's down since months. https://github.com/vuejs/vue/issues/11867
How to scrape the web with Puppeteer in 2023
5 projects | dev.to | 7 Mar 2023
What is Vue?
3 projects | dev.to | 6 Feb 2023
How worried are you about AI taking over music?
13 projects | /r/WeAreTheMusicMakers | 3 Feb 2023
Vue 356 contributors 202k stars
Which Framework is Most Suitable for Your Project or Learning in 2023: Angular vs React vs Vue
3 projects | dev.to | 3 Jan 2023
Please visit below link for various Vue Versions Vue Version Release List
15 Popular Github Repositories for the Modern Developer of 2023
15 projects | dev.to | 31 Dec 2022
Reddit just completed their migration out of React
2 projects | /r/reactjs | 8 Dec 2023
10 projects | news.ycombinator.com | 27 Nov 2023
I work on Lit, which I would hesitate to call a framework, but gives a framework-like DX for building web components, while trying to keep opinions to a minimum and lock-in as low as possible.
It's got reactivity, declarative templates, great performance, SSR, TypeScript support, native CSS encapsulation, context, tasks, and more.
It's used to build Material Design, settings and devtools UIs for Chrome, some UI for Firefox, Reddit, Photoshop Web...
https://lit.dev if you're interested.
HTML Web Components
14 projects | news.ycombinator.com | 13 Nov 2023
I am more a fan of the augmented style because it doesn't entrap you in dev lock-in to platforms.
The problem with frameworks, especially web frameworks, is they reimplement many items that are standard now (shadowdom, components, storage, templating, base libraries, class/async, network/realtime etc).
If you like the component style of other frameworks but want to use Web Components, Google Lit is quite nice.
Google Lit is like a combination of HTML Web Components and React/Vue style components. The great part is it is build on Web Components underneath.
Both follow the mental model of mapping a URL pattern to a component fairly intuitively.
> Finally, the last thing I would suggest is that writing an entire app in vanilla web components is kind of crazy talk in my opinion. For 5kb you can have a super nice developer experience using Lit (https://lit.dev)
I 100% agree with this. For me it was more of a question of "can I do it", and that was something I wanted to find out. You notice that I ended up having to recreate a significant chunk of lit-like functionality on my own via a base class: https://github.com/jjcm/nonio-frontend/blob/master/component...
I would very much recommend not going full vanilla. Using a library like lit will definitely help making things easier/more polished, and will integrate better with existing tooling.
From the comments I see here, it seems like people expect the Webcomponents API to be a complete replacement for a JS framework. The thing is, our frameworks should start making use of modern web APIs, so the frameworks will have to do less themselves, so can be smaller. Lit  for example is doing this. Using Lit is very similar to using React. Some things work different, and you have to get used to some web component specific things, but once you get it, I think it's way more pleasant to work with than React. It feels more natural, native, less framework-specific.
For state management, I created LitState , a tiny library (really only 258 lines), which integrates nicely with Lit, and which makes state management between multiple components very easy. It's much easier than the Redux/flux workflows found in React.
So my experience with this is that it's much nicer to work with, and that the libraries are way smaller.
Regarding the point you mentioned about not being able to pass objects via attributes, you can however pass them via properties on the element.
Also as for the state management side of things there is nothing at all stopping you from hooking up whatever state management solution you want. I’ve even seen a bunch of solutions that use the browsers built in event model as well if keeping dependencies to a minimum is your goal.
Finally, the last thing I would suggest is that writing an entire app in vanilla web components is kind of crazy talk in my opinion. For 5kb you can have a super nice developer experience using Lit (https://lit.dev)
Lit 3 Release Announcement
9 projects | news.ycombinator.com | 10 Oct 2023
Something that caught my attention is that, in their homepage (https://lit.dev), the list of organizations using Lit actually specifies where it is being used in each organization and even provides some links.
Framework Interoperable Component Libraries Using Lit Web Components.
8 projects | dev.to | 8 Oct 2023
Lit is having a moment, one would say it's on fire 🔥🤣. It's being used everywhere from the web version of Photoshop to Microsoft's new windows app store. I think something clicked for me recently as to why lit is the major choice when it comes to the future of the web, and web components overall.
Svelte 5: Runes
7 projects | news.ycombinator.com | 20 Sep 2023
That is exactly my experience after trying svelte/sveltekit for 2 months. Loved svelte at first sight but soon their own invented complexity (and a very confusing error log) made me realize that I was changing React for something quite similar (with a bunch of different problems). In place of going back to React tho, I tried the next one in my list: Lit. No regrets, found the (powerful) simplicity I was looking for. Give it a try before getting back to React: https://lit.dev/
What are some alternatives?
Svelte - Cybernetically enhanced web apps
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
vite - Next generation frontend tooling. It's fast!
htmx - </> htmx - high power tools for HTML
React - The library for web and native user interfaces.
Angular - Deliver web apps with confidence 🚀
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
Aurelia 1 - The Aurelia 1 framework entry point, bringing together all the required sub-modules of Aurelia.
awesome-blazor - Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.