5 ms·
Not to start an unholy flame war, but if you were to start a new project and didn’t need to worry about the ecosystem or workforce, what framework would you cho
by pupppet 4y ago
Not to start an unholy flame war, but if you were to start a new project and didn’t need to worry about the ecosystem or workforce, what framework would you choose? Vue? Svelte? Something else?
- taveras 4y agoSolidJS
- ctom96 4y agoSvelte for me
- runarberg 4y agoHonestly just use what you know. Unless your goal with the project is to learn new things or to have fun, than go with what is most interesting for you. Or if you are in a larger team, then talk to your teammates and try to get a consensus around what you are most comfortable with collectively. I only advice against using a niche framework if you suspect the project is gonna be long-lived and managed by a medium to a large team, in that case pick the one of the big ones—React, Angular, Vue, or Svelte—which your teammates can agree with.
- FractalHQ 4y agoSvelte is a no-brainer here.
- machiaweliczny 4y agoHow’s debugging?
- illiarian 4y agoSvelte or SolidJS.
- michaelchisari 4y agoI'm interested in what's happening in the MPA space. The Page and View Transitions API that the chrome team is working on, partial update libraries like htmx and unpoly, etc. If payloads are tight and servers snappy, many of the concerns that led to complex SPA architectures in the first place have begun to wither away.
- 0xblinq 4y agoHotwire and Stimulus are great. They’re widely used within the league of “sprinkles” libraries and it’s well maintained. You can use it with any backend framework. I use it with Laravel and it’s a pleasure to work with. But it’s not trendy or fashionable, so expect a lot of looking down at you for using it.
- darkhorse13 4y agoSvelte. If I really want JSX, then I would pick Solid.
- _s 4y agoDeno / Fresh. I despise what NPM has become, and how complex / time consuming the build pipeline of front end apps is. It’s still not a mature framework yet but hot damn does it excel at just getting out of my way and letting me ship stuff.
- norman784 4y agoI don't know about Vue3 (I used in the past Vue2 only), but Svelte is similar to React, I'm migrating a small/medium project from React to Svelte and it feels too easy most of the time to port component by component, also to me, at least to this point, Svelte feels more performant and you have 100% control over the reactivity without too much `use{function}`. I would recommend you to build a small project, maybe a Todo app in every framework you want to try, or maybe if you have a project, build a small part of it in each (I will pick the part that you think is the trickiest to build with React or the framework you are actually using). Also I'll recommend to also check Qwik and Fresh(deno).
- dgb23 4y agoI just started one small project that is a single component that talks to our API and is rendered on an external website. I used lit-html for it. Very small, very fast library for this kind of thing. No build tool required. I choose my own (smaller, simpler, more straightforward) way of managing state.
- pcthrowaway 4y agoI find Svelte phenomenal. But I'm also interested in trying Solid.js and Vue, and for some types of projects I'd likely even go Astro+Svelte or Astro+React. Hard to speak authoritatively on the matter though because over my career I've only done vanilla JS, jQuery, Backbone.js, React, and then Svelte, in that order, and each has felt like a leap forward in evolution
- amardeep 4y agoStandard ones I would like to try are Solid/Svelte/Vue - Lit if I wanted to share components with other teams - Marko if the site had lots of static content - Qwik if speed was paramount - Fresh too looks interesting
- quectophoton 4y agoMithril.js, without JSX.
- 0xblinq 4y agoStimulus and Hotwire (on top of Laravel or any other decent batteries included framework). Not a single one of the many projects I’ve worked on in the last 10 years needed such a level of interactivity that it justified the trade offs of using react or any other frontend-heavy frameworks. I’ve seen entire CRUD spas that would have been built in 20% the time if we didn’t have to build a graphql api, figure outs authentication and permissions, integrate that with a custom validation setup, integrate all of the above with the translations systems, coordinate deploys or do forward compatible migrations, etc, etc. so much energy (and money) wasted.
- gushogg-blake 4y agoSvelte
- citeguised 4y agoWC with LitElement (Shadow DOM disabled) for a SPA (if no SSR is needed).
- reverseblade2 4y agoWeb Components, Service workers, Lit.dev, htmx, declarative shadow dom. These are the modern tools you need.
- gg2222 4y agoSolid JS It will have a very easy learning curve for React users too.
- aquaductape 4y agoBe careful on spreading the statement "easy for React users", yes that's true for using JSX, but for React developers trying out SolidJS, make sure not to desctructure props, get rid of rerending function mental model, components only runs ONCE so reactivity works by tracking reactive elements(signals/stores) inside JSX or effects(createEffect, createMemo ect), that means no early returns. If a React developer (I've witnessed this with Twitch streamers), jumps into SolidJS blind without taking tutorial, they get lost into rerender mental model.
- satvikpendem 4y agoI'd still use React, purely to be able to use JSX without another templating language, and I think in its functional paradigm as well.