I'm surprised by the conclusion that React is easier to learn. Svelte is way more straightforward in my opinion: about as close to writing native HTML, JS and CSS as any framework has come; and with minimal boilerplate...
For anyone who has learnt how to create web content the "old fashioned way" Svelte couldn't be easier. But maybe that's the problem: do people not learn the fundamentals these days and go straight into learning React?
I do totally agree on this. If have been doing regular HTML, JS and CSS then Svelte should be much faster and straight forward to pick up and start using compared to React, I know it was for me at least.
One of the things I like with Svelte is that u can basically do stuff the "old fashioned way" and it will work and at the same time u can also do it the "Svelte way" that is often an easier n less complicated way of doing the same thing while in React u basically need to do it "the React way".
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
It depends on your starting point. If you already work and know HTML, CSS, JS, the most shocking thing you'll face with react is to use className instead class html attribute, which is also easy to follow if you saw XML sometime in your career.
On the other hand, svelte has this template engine-like syntax that's something completely new to learn.
Either way, the "easier to learn" is always a subjective topic and depends on the previous knowledge so ain't gonna discuss that more in detail because it is a non sense. The same way "which is better" is totally dependent on the target, for some applications React may be better, for others Svelte may be better 🤷🏼♂️
do people not learn the fundamentals these days and go straight into learning React
100% agree on that, not only React but any other thing, you can replace React for Svelte, Angular, Vue or whatever is the current fashion in online bootcamps -trying to understand the business model, they need to sell a need at the end- or YouTube channels -they need to provide new content anyway-.
Personal anecdote
A couple of guys I had in projects (I work as tech lead/team lead) even came to me asking about a something I coded "Where's that in React documentation? We can't find it to understand what it does", I proceed then, to send them a couple of MDN links and they were visibly confused about it.
It took a couple of training meetings to make them reach the point of understanding that React is just a library for building user interfaces, the rest can be plain JS and the usage of more or less third party libs is up to the one defining the project, and that not every library with the word "react" in the name means it's included in react, nor that it's made by React devs and not that you must use this before any other approach...
At this point I understood why there are people out there arguing that React is a framework (despite react's homepage stating "A JavaScript library for building user interfaces"), because they use it the closest possible like it was, effectively a framework. They search "how to do [whatever] in React" instead "how to do [whatever] in JavaScript" and it's because they don't understand properly neither the language nor the tool and of course, they don't understand the web platform at all.
I did a test "Share your screen and tell me what the following code is doing, you can google whatever, of course":
/**
* Applies Function piping to an array of async Functions.
* @param {...Function} fns
* @returns {Function}
*/exportconstpipeAsync=(...fns)=>(input)=>fns.reduce((chain,func)=>chain.then(func),Promise.resolve(input));
Yes, including the JSDoc. The first search was "pipe async react", the second one was "Reduce React" 😂 Which of course lead them to more confusion.
I'm coming from the perspective that if you want to learn front end you should start with the basics of how to put an html page together. That means content + script and style blocks. And that's how svelte components are composed. No returning render output from a function; no mixing of JS and html; no useState etc.
You're right that it's just my opinion; but from my perspective there's so little difference from the basics you should know and a Svelte component it couldn't be any easier. The "template engine-like syntax" is trivial and can be learnt in 5 minutes...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm surprised by the conclusion that React is easier to learn. Svelte is way more straightforward in my opinion: about as close to writing native HTML, JS and CSS as any framework has come; and with minimal boilerplate...
For anyone who has learnt how to create web content the "old fashioned way" Svelte couldn't be easier. But maybe that's the problem: do people not learn the fundamentals these days and go straight into learning React?
I do totally agree on this. If have been doing regular HTML, JS and CSS then Svelte should be much faster and straight forward to pick up and start using compared to React, I know it was for me at least.
One of the things I like with Svelte is that u can basically do stuff the "old fashioned way" and it will work and at the same time u can also do it the "Svelte way" that is often an easier n less complicated way of doing the same thing while in React u basically need to do it "the React way".
It depends on your starting point. If you already work and know HTML, CSS, JS, the most shocking thing you'll face with react is to use
classNameinsteadclasshtml attribute, which is also easy to follow if you saw XML sometime in your career.On the other hand, svelte has this template engine-like syntax that's something completely new to learn.
Either way, the "easier to learn" is always a subjective topic and depends on the previous knowledge so ain't gonna discuss that more in detail because it is a non sense. The same way "which is better" is totally dependent on the target, for some applications React may be better, for others Svelte may be better 🤷🏼♂️
100% agree on that, not only React but any other thing, you can replace React for Svelte, Angular, Vue or whatever is the current fashion in online bootcamps -trying to understand the business model, they need to sell a need at the end- or YouTube channels -they need to provide new content anyway-.
Personal anecdote
A couple of guys I had in projects (I work as tech lead/team lead) even came to me asking about a something I coded "Where's that in React documentation? We can't find it to understand what it does", I proceed then, to send them a couple of MDN links and they were visibly confused about it.
It took a couple of training meetings to make them reach the point of understanding that React is just a library for building user interfaces, the rest can be plain JS and the usage of more or less third party libs is up to the one defining the project, and that not every library with the word "react" in the name means it's included in react, nor that it's made by React devs and not that you must use this before any other approach...
At this point I understood why there are people out there arguing that React is a framework (despite react's homepage stating "A JavaScript library for building user interfaces"), because they use it the closest possible like it was, effectively a framework. They search "how to do [whatever] in React" instead "how to do [whatever] in JavaScript" and it's because they don't understand properly neither the language nor the tool and of course, they don't understand the web platform at all.
I did a test "Share your screen and tell me what the following code is doing, you can google whatever, of course":
Yes, including the JSDoc. The first search was "pipe async react", the second one was "Reduce React" 😂 Which of course lead them to more confusion.
I'm coming from the perspective that if you want to learn front end you should start with the basics of how to put an html page together. That means content + script and style blocks. And that's how svelte components are composed. No returning render output from a function; no mixing of JS and html; no useState etc.
You're right that it's just my opinion; but from my perspective there's so little difference from the basics you should know and a Svelte component it couldn't be any easier. The "template engine-like syntax" is trivial and can be learnt in 5 minutes...