Earlier quoted context omitted.
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.
Introducing Svelte, and Comparing Svelte with React and Vue (2021)
111–120 of 213 posts
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#112Earlier quoted context omitted.
One of React's competitive advantages is React Native. That's hard to beat.
there is svelte-native based on Nativescript. it is similar fast or faster[1] and provides the ability to directly use every native function in JS without having to rely on new interfaces or build versions (e.g. you can directly access new APIs from JS). beeing able to use Svelte makes it sooo much easier to develop mobile apps. [1] https://blog.nativescript.org/perf-metrics-universal-javascr...
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#113Earlier quoted context omitted.
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.
The guy who created it, Rich Harris, used to work for the New York Times and developed it while he was there. So it's not a big surprise that NYT use it. I'm not sure about many other 'larger news sites' using it, but one place I have seen it out in the wild in a big production app is the Apple Music web app.
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#114I 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.…
almost with many things in software development to be honest.
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#115I'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…
[0]: http://daisyui.com
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#116I'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...
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#117I 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.…
Svelte is a solution to a problem that doesn't need to be solved. almost with many things in software development to be honest.
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#118Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#119Earlier quoted context omitted.
Just throwing this out there, but have you considered that React and Vue in fact also have custom non-JS syntax? JSX is not valid JS, parsers had to be written to work with it. And Vue uses templating syntax in HTML, just like Svelte. Svelte doesn't have any non-native syntax in the JS parts, just the templating.
> but have you considered that React and Vue in fact also have custom non-JS syntax? I 100% agree, and I never fully got this argument. But my God do people love to repeat it. So much of react's initial fervor was around "it's just javascript". I write a lot of vue code and I only use like half a dozen directives and learning all of them should take less than one afternoon. And yet, the number of people that don't li…
I also use about 30 different `v-` components from Vuetify, which come with so many properties, events and slots that it might as well be a giant DSL.
Re: Introducing Svelte, and Comparing Svelte with React and Vue (2021)
#120I'd really like to hear more from Svelte devs about what non-happy paths look like. I specialise in React.js and there are any number of escape hatches to make sure you can get something working just the way you want. What I fear about Svelte is getting to 95% complete and finding the one obscure thing a stakeholder will not budge on is not possible.
I have a lot of experience with React, Vue, and Angular and I have moved completely over to Svelte if the client will allow. Since it uses normal Javascript, normal HTML, and normal CSS it also doesn't seem to suffer as much regarding the ability to find other people to support it. If they can use normal JS, HTML, and CSS the "Svelte" part of it can be learned in a couple of hours max.
Early on, there was a custom component shortage, but it is so easy to wrap plain vanilla JS components in Svelte components that this is has mostly disappeared as well.
If I where going to point out anything negative about it, I would say that if you are used to developing by just plugging in pre-built components (very common in React development) then it won't be as easy.