Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Svelte, and Comparing Svelte with React and Vue (2021)

joshcollinsworth.com

Post reply on HN
Print view View original

51–60 of 213 posts

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#51

Post by azangru »

mritchie712 wrote: post #41
yawnxyz wrote: post #3

I've worked with all three frameworks, but as a mostly single dev/engineer I very very much prefer Svelte because it lacks a lot of boilerplate that React has, and it's easier to think about than Vue's clunky way to write variables and functions. But I'm a "hacker type" and don't work in a large tech company. I haven't seen Svelte in any sort of "real tech companies", haven't seen it on job boards, and it doesn't see…

It's a case of "Nobody ever got fired for choosing X"[0]. No one would blame you for choosing React for a major project / new startup, but someone could definitely poke holes in choosing Svelte ("theres no package for X", "it doesn't scale", "we can't find devs that know it", etc.) 0 - https://www.quora.com/What-does-the-phrase-Nobody-ever-got-f...

> No one would blame you for choosing React for a major project / new startup

Oh, I know people who would. Especially if that choice was made mechanically, without proper assessment of project requirements and framework strengths/weaknesses.

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#52

Post by scrollaway »

mccorrinall wrote: post #30
pixard wrote: post #11

I work with React (Next.js) on my main project and while I don't appreciate some things generally I haven't had any issues and Next.js in particular has been great. I also find JSX stellar. I used Vue from 0.12 until around ~2.5, I really liked it at the beginning (coming from a jQuery only world) but I was forced into learning React for React Native and then I kind of standardized on it for a while and Vue fell off.…

I like NextJS too, except for the API part. The DX is so poor compared to e.g. fastify. Want to only allow a specific http method for this route? Have fun adding boilerplate. Want to throw a specific http error like 403? Have fun writing this by hand. It also lacks schema validation (I’d love to see ajv here) and openapi gen. You have to write everything. by. yourself.

I like NextJS for the frontend and django-ninja for the backend. django-ninja has all those things you mention and way more, and has a very rich backend ecosystem thanks to being in the django world. https://django-ninja.rest-framework.com/

FastAPI is also great but a little more involved. It's good if you don't want to be in the Django world.

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#53

Post by actionfromafar »

azangru wrote: post #51
mritchie712 wrote: post #41

Earlier quoted context omitted.

It's a case of "Nobody ever got fired for choosing X"[0]. No one would blame you for choosing React for a major project / new startup, but someone could definitely poke holes in choosing Svelte ("theres no package for X", "it doesn't scale", "we can't find devs that know it", etc.) 0 - https://www.quora.com/What-does-the-phrase-Nobody-ever-got-f...

> No one would blame you for choosing React for a major project / new startup Oh, I know people who would. Especially if that choice was made mechanically, without proper assessment of project requirements and framework strengths/weaknesses.

"Nobody ever got fired for X" is a rhetorical device which means "in most situations, you generally won't be faulted going with the most main-stream option on the market".

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#54

Post by mritchie712 »

azangru wrote: post #51
mritchie712 wrote: post #41

Earlier quoted context omitted.

It's a case of "Nobody ever got fired for choosing X"[0]. No one would blame you for choosing React for a major project / new startup, but someone could definitely poke holes in choosing Svelte ("theres no package for X", "it doesn't scale", "we can't find devs that know it", etc.) 0 - https://www.quora.com/What-does-the-phrase-Nobody-ever-got-f...

> No one would blame you for choosing React for a major project / new startup Oh, I know people who would. Especially if that choice was made mechanically, without proper assessment of project requirements and framework strengths/weaknesses.

I mean this from the perspective of a newly founded startup.

You're right that this doesn't hold true in a large corporation where they may already have a ton of code and preferred frameworks.

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#56

Post by zozbot234 »

msdrigg wrote: post #43
yawnxyz wrote: post #3

I've worked with all three frameworks, but as a mostly single dev/engineer I very very much prefer Svelte because it lacks a lot of boilerplate that React has, and it's easier to think about than Vue's clunky way to write variables and functions. But I'm a "hacker type" and don't work in a large tech company. I haven't seen Svelte in any sort of "real tech companies", haven't seen it on job boards, and it doesn't see…

I know svelte is a very common choice for larger news sites to build interactive stories. Ive specifically heart of NYT using it as well as pudding.cool. It makes sense for this small website extension because you can build and compile a small component without having to bundle the entire react runtime in.

> It makes sense because you can build and compile a small component without having to bundle the entire react runtime in.

Fixed.

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#57

Post by zozbot234 »

pixard wrote: post #11

I work with React (Next.js) on my main project and while I don't appreciate some things generally I haven't had any issues and Next.js in particular has been great. I also find JSX stellar. I used Vue from 0.12 until around ~2.5, I really liked it at the beginning (coming from a jQuery only world) but I was forced into learning React for React Native and then I kind of standardized on it for a while and Vue fell off.…

What's wrong with Svelte or SolidJS for "big things"? Do they limit scalability in some way?

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#58

Post by jdthedisciple »

thunderbong wrote: post #17

I've recently started working with Svelte and have been loving it compared to React. A lot of stuff flows through very intuitively. However, for any front-end framework, the UI is paramount, and the most full-fledged component framework I found was Carbon Components[0]. I've heard rave reviews about Quasar[1] for Vue 3. Are there any equivalent UI component frameworks for Svelte? [0]: https://carbondesignsystem.com/d…

Uhm, Carbon supports Svelte too ...

Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)

#60

Post by ricardobeat »

preommr wrote: post #16

My 2c: I think svelte is overhyped and a poor solution to the problem it's trying to solve. First of all, I am tired of ridiculous metrics like how small svelte is when it's a really small example, and it's one or two lines of initial boilerplate. The thing that really set svelte apart was it's better syntax and experience when it first came out. I think that was when react class components, and vue 2 was still promi…

> I am tired of ridiculous metrics like how small svelte is when it's a really small example, and it's one or two lines of initial boilerplate.

There is nothing ridiculous about it. Svelte has a tiny* runtime library by design, so naturally the code output will be much smaller. Also as a result of its design, you do end up writing less lines of code.

> That kind of performance is rarely going to matter before other bottlenecks

It matters a lot for complex apps. React is unoptimized by default, and the standard advice is to only "optimize when you need it", which more often than not is too late. By the time you have an app with 15 context providers and nested components hundred-levels deep, and you start noticing slowness, performance optimization is a gigantic effort.

> it's brining in custom syntax to really tackle the problems with reactivity

While Svelte uses a (tiny) bit of custom syntax, React makes you bring in a ton of DSLs. Hooks, the component lifecycle, and all the third party libraries you will need to build a functional app require a lot more effort. People forget just how much stuff they had to learn.

* fixed from 'no runtime'

Post reply on HN