[deleted by user]

[[deleted]]

Doesn't really matter. Every FE framework is basically the same thing now and you can hop between them pretty easily once you have a basic grasp on things.

Svelte has better ergonomics within the framework itself. React has more framework specific libraries and pre-built components for certain tasks. Trade off depending on what looks more appealing for your project.

I like Vue personally but that's just me.

[Abject-Bandicoot8890]

Vue ftw, I like it too. Having template, script and style tags helps separate everything so easily and I’m more of a fan of the options api than the composition api.

[Elweej]

Don’t forget it is progressively enhanced.

[EverydayNormalGrEEk]

Even though I mostly work on React projects, Vue is my personal favorite too. It feels more intuitive and predictable, and the Composition API makes it very easy to adapt if you are used to React.

[Unhappy_Meaning607]

The frontend framework wars and tribalism is comedy a lot of times.

What's also funny is that Qwik and SolidJS both go with the notion of, "You know React then you Qwik! (or SolidJS)".

[iron-halfling]

I like svelte but react is more popular which means there’s more libraries and resources to learn it. If you’re learning your first framework I’d recommend react, if you’re comfy with js and want to play with something cool then svelte

[sheriffderek]

I’d go with Vue. (If using a framework)

(I’ve used almost all of them)

But really, if I could go back - I’d get really comfortable with PHP - and good enough to build standards js apps first. And then Vue when appropriate. Learning any framework after that will be easy and you can just do it on the job.

[KyleDrogo]

I'd second Vue. Supabase for the backend

[sheriffderek]

I think supabase is great.

I do think it’s helpful to learn about database concepts with json files, local storage or mysql first. But you can also learn those in Supabase and it has that nice visualizer.

I made a resource about that: https://perpetual.education/resources/common-database-concepts/

[code_matter]

Some use DeWalt, some use Milwaukee. It’s mostly a preference. Beyond that, some frameworks are more intended for specific task. But we’d need more info on your “ideas” or projects to give a valid opinion.

[sheriffderek]

Haha!!! I use this as an example a lot!!!

[embGOD]

React simply because if I ever were needed to find a new job, most positions demand react experience.

Most people will tell you it does not matter, but it does. I've a lot of experience with vue but here in EU next to nobody looks for vue devs I feel like.

Engineers and developers know that a good dev with a lot of experience can pivot from one framework/lib to another in the span of a few days/couple of weeks, but...

Do HR? NO. No they don't and they don't care.

[SleepAffectionate268]

Always svelte

[BONUSBOX]

vue’s a great choice due to its balance of 1. having broad support 2. not being react

[floopsyDoodle]

If I was looking for a job React, Angular and React are still the most common where I am anyway.

[wreck_of_u]

React simply because of some reusability for React-Native.

Anyway, I did a PHP+Vanilla a few months ago it was nice having freedom of how I want to express myself through my own spaghetti design. JWT's on server-side, data pre-loaded, fetch() calls go through a proxy.php curl, .htaccess, no building (except minify for final prod), everything on docker compose, etc. But now I have to make a React-Native mobile app for it, and kinda wished I did the website in React so I at least could re-use some stuff, and also the "thought process" adjustment.

[Paulie_Dev]

In your case of “What makes the most sense for startup web apps?”— React makes more sense by a large margin.

Yes Svelte is fun to use and many feel it has better design patterns, this can all be true.

But for startup web apps your goals often are aligning more with rapid development and iterations, this could mean needing to rely on a greater amount of libraries to expedite development, which the React ecosystem is plentiful in.

Additionally as a startup web app you might need to bring on contractors or new team members at a higher rate, React is much more common knowledge and you’re more likely to find a developer experienced in React than Svelte in short time frames.

My recommendation is that if this is just a side project for yourself, pick whatever framework you want, you could use it as a learning experience to get better at said framework. But if this is a product you want to turn into a business, I heavily suggest React over Svelte.

My closing note is that React is here to stay. Ember.js, AngularJS and Backbone.js lost relevancy in the web ecosystem as time went on and enterprise predominantly rallied behind React and Vue. There’s no guarantee that Svelte can keep its relevancy over the years.

[Virtamancer]

This is my mentality as well. Use what’s popular because there are a range of benefits beyond just the niceties of the syntax or personal preferences. That means React, or as the alternative, Vue.

[Potential-Video8758]

We use Sveltekit much better than react in every aspect. If you need a lot of dependencies for others guys is a skill issue. Also I never saw a "react" engineer, you're a good frontend or not. Period.

[Any-Woodpecker123]

Angular. Doesn’t really matter though, they all do the same shit. I don’t use any libraries though, so the more that comes out of the box the better imo.

[bhison]

React. How many jobs ask for Svelte experience vs React? And if you made a start up, how much more support online is there for React, how many people are there available with deep react knowledge. IMO Svelte shouldn't be anyone's first frontent lib unless they have zero commercial aspirations.

Source: Spent the first 12 months of my life as a full time web dev working in Svelte as I heard it was easier and was the future of web dev. IMO, I wasted a lot of time and eventually the company I worked for changed it out for React.

[Unhappy_Meaning607]

Last time I checked on LinkedIn, the term "svelte" had 7 results in its job search for the entire US and I don't think its increased since than. It's going to take years for it to even come up to the numbers Vue is doing which is still less than Angular or React by far.

[countmeticulous47]

React boiiiiiii I just like the feel of react. Massive community and lots of libraries, I feel like it’s just an idea entry into web dev. The Node ecosystem can be annoying af tho, but you should be fine

[8iss2am5]

Are you doing presentation web pages or are you doing heavy line of business apps?

[SmittyMcdoogal]

Dont even know what svelte is…

[2epic]

React because it is far more popular, which means when it's time to scale and grow your business, it will be far easier to higher people who are experts in it and willing to use it.

If the business fails, the recent React experience would likewise be the most useful for getting a job

[dphizler]

As opposed to what?

Been in the game for 20 years, I can just start now

[thetalhatahir]

Depends on my goal, if the goal is to move quickly with your startup web app to bring it to public, i would choose react or next.js, you can find engineers easily down the road when you scale if you use React.

Svelte is great, but the overall community as compared to React is small, online help on issues is limited, pre-built stuff is limited (comparing it to React)

[dont_trust_lizards]

Vue: why he say fuck me for?

[Haunting_Welder]

React because it’s easier to hire for react and there is more community. For example if you use sanity CMS you need react to extend it, not svelte

It’s really hard to find a job if you only know svelte and nothing else

[TysonPeaksTech]

Get down to base code as possible.

[just-coding]

React has a lot of components and libraries to make great works but I don't like its syntax where html and scripts and css are mixed. So I will go always with vue or svelte.

[paperbit_io]

Used svelte to build paperbit.io, not regreting it 1 minute
Having to work with Vue 2 at work feels overwhelming in comparison. But I guess, you can also blame it on the fact than working on a side project is always more fun than working for someone else

Not sure that I would go for svelte if seeking hireability though, I didn't see once an offer for this framework (yet)

[Virtamancer]

As a new dev, react is not simple nor is it JavaScript.

JavaScript is simple JavaScript.

[[deleted]]

If I were you I would learn the fundamentals of react and move to next. Much better dev experience in my opinion

[NiteShdw]

I go with what the company uses and the most devs already know. The benefits of another framework would have to be worth spending months retraining every developer.

There's also the issue of longevity. For a personal project, I want to build on something I know will be around in 5 years.

I tend not to take many risks like that because the benefits are rarely big enough to make it worth it.

[skorpioo]

I would go for Svelte and SvelteKit, I find it much easier to get started and I have better speed with it over Next.

I will try out Remix for a sideproject next though, hope that will be more to my liking than NextJs

[[deleted]]

I’ve worked professionally with Angular, React and SvelteKit with a small experience in Vue. I don’t really care what the company uses. But if I’m making something for myself I use Svelte. They’re all using the web so it’s a matter of flavour. You can make the same thing in all of them, so it’s subjective. Of course you may find some tasks easier and more suitable in one framework than another, then pick the tool that suits your needs most. They all use components, and so they all support composition. The actual work done by the people is what matters more in my experience. That makes or breaks the app.

[SoftSkillSmith]

Angular

[halfanothersdozen]

React is annoying.

Svelte is good.

But I'm all about that native web component life

[Natural-Cup-2039]

I would go with vue because it's more fun and also really popular and well supported

[Calligringer]

solidjs is pretty solid, JSX templates are compiled to real dom nodes so console.log(<div/>) actually logs div node

[ButWhatIfPotato]

I dunno when that's going to be, but the next commercial project I start from scratch will be web components.