Everybody knows non-alcoholic beer is not actually beer because of the fact is doesn't contains alcohol. Despite that we all call it non-alcoholic beer instead of soft drink or lemonade.
So we all know that for example Vue.js is a Javascript framework (beer) and React.js is a Javascript library (non-alcoholic beer). But in everyday life or at blog posts like this, it doesn't matter people call it a library or framework.
So don't make a point of it and cheers. Thank you :)
Well, let’s take your analogy. Who is all? Adults?(exp devs) Children?(newbies). I would argue that a child does not know any better and will take this as a fact and therefore go order a BEER and get drunk (failed because he got confused).
That's what we call 'learning'. A newbie doesn't know anything a about the programming and have to learn how it is structurized, how it works etc. So the child wouldn't even get a beer because of his or her age. And the adult that starts drinking has already heard a lot about what it can do and what it can't do. But does not know how it tastes etc.
So stop making a problem of a small thing like this. Everybody knows how to use the Pythagorean theorem but a small part of the people that uses it knows how it actually works.
I think your missing the point. React itself doesn’t even carry themselves as a framework so why should we? In addition, by calling it a framework your taking away the core of what React is, a lightweight, flexible JavaScript library. So no, is not a small thing, it’s makes a HUGE difference.
No you're missing the point. Read this post again. Does it matter in this post that React is a library or a framework?? No it doesn't. It's just about it's popularity. Think about it. I can guarantee that I can find at least one spelling mistake in every Dev.to blog post. Does that matter? No because it is not a dictation.
So focus on the meaning of this post instead of crawling just to one mistake or one misunderstanding.
Spelling mistake haha..This is more than a spelling mistake lol. So I guess to you, referring Mars as Venus makes no difference since they are both planets right?(even though there huge obvious differences). This Somewhat shows your understanding of things.
If we're comparing mars and venus no XD. But in this post we're not talking about comparing mars and venus. And woooh this post is also not about the differences between Libraries and Frameworks. So if you said that China is not equal to Japan. And red is not equal to green.
Then it would have meant just as much, just saying React is not a framework but a library.
Beside that "Wrong! React is NOT framework please stop spreading this nonsense" is not the most commenly way of commenting blog posts. Just a tip for next time.
I started programing when I was 15. For 3 years I was focused on learning as much as I could. After that I tried to get into freelancing, but didn't have much success there. Currently I am 20.
Well react is more a framework then a library. The distiction between the two terms can be looked from multiple persectives. But it doesent really make a difference call it what you want. No need to be mad about it.
While this might be accurate, if you're suggesting React be excluded from this list, that would be a disservice to both React and the reader. Does changing the section title to "JavaScript Frameworks and Libraries" resolve this? The problem with that is that this opens the scope to thousands of useful JavaScript libraries, while the focus of that section is on those providing that list of important framework-like packages available to the developer. Excluding React here because it doesn't actually provide a framework is worse.
To give my 2 Cents to that Topic aswell -
As an React Expert myself - i do not care if its called Jquery 2.0, Library, Framework whatever.
But if i would starting learning React i would like to have the right Term - therefore "Library".
What? What’s in dispute is not an opinion, it’s a fact. It’s literally on the homepage banner of reactjs.org. Also, it’s not an accusation but a fact that this is spreading misinformation
Okay, let me rephrase, instead of calling it nonsense and just declaring "Wrong!". Maybe take a kinder approach of directing people to the correct information so people can learn for themselves.
It's not very helpful to people who trying to learn and make themselves better engineers and developers when you just declare them wrong, if anything it makes the writer feel worse about what they wrote.
Constructive criticism is a great way to learn, but also a great way to teach.
That’s the problem, it is not “technically” a framework, it’s just simple not. People that refer it as a framework heard it from somewhere and it confuses people as to what React actually is. NextJs is a framework that uses React library. This is how it should be informed. I guarantee newbies are getting confused as to…”well, should I use NextJs or React and what’s the difference?”
That's a bit harsh, and a bit of semantic nitpicking as well ... if you take React, and then (as almost everyone does) you install a few other tidbits alongside it (like react-router and a couple of other standard packages), well, then by all means you've got a "framework".
Having had this debate a hundred times and done research into the matter I have come to the conclusion: who bloody cares? Like it couldn't possibly be less relevant to this article. This whole debate is just semantics
I think you could find a much more tactful way of going about this. But, whatever. You seem like the type that absolutely NEEDS to show they are right. So, congratulations on proving that, while also looking like a complete ass. Yes, React IS a library and NOT a framework. But, constantly needing to point this out to people must get tiring.
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.
Wrong! React is NOT framework please stop spreading this nonsense
Everybody knows non-alcoholic beer is not actually beer because of the fact is doesn't contains alcohol. Despite that we all call it non-alcoholic beer instead of soft drink or lemonade.
So we all know that for example Vue.js is a Javascript framework (beer) and React.js is a Javascript library (non-alcoholic beer). But in everyday life or at blog posts like this, it doesn't matter people call it a library or framework.
So don't make a point of it and cheers. Thank you :)
Well, let’s take your analogy. Who is all? Adults?(exp devs) Children?(newbies). I would argue that a child does not know any better and will take this as a fact and therefore go order a BEER and get drunk (failed because he got confused).
That's what we call 'learning'. A newbie doesn't know anything a about the programming and have to learn how it is structurized, how it works etc. So the child wouldn't even get a beer because of his or her age. And the adult that starts drinking has already heard a lot about what it can do and what it can't do. But does not know how it tastes etc.
So stop making a problem of a small thing like this. Everybody knows how to use the Pythagorean theorem but a small part of the people that uses it knows how it actually works.
I think your missing the point. React itself doesn’t even carry themselves as a framework so why should we? In addition, by calling it a framework your taking away the core of what React is, a lightweight, flexible JavaScript library. So no, is not a small thing, it’s makes a HUGE difference.
No you're missing the point. Read this post again. Does it matter in this post that React is a library or a framework?? No it doesn't. It's just about it's popularity. Think about it. I can guarantee that I can find at least one spelling mistake in every Dev.to blog post. Does that matter? No because it is not a dictation.
So focus on the meaning of this post instead of crawling just to one mistake or one misunderstanding.
Amen :)
Spelling mistake haha..This is more than a spelling mistake lol. So I guess to you, referring Mars as Venus makes no difference since they are both planets right?(even though there huge obvious differences). This Somewhat shows your understanding of things.
If we're comparing mars and venus no XD. But in this post we're not talking about comparing mars and venus. And woooh this post is also not about the differences between Libraries and Frameworks. So if you said that China is not equal to Japan. And red is not equal to green.
Then it would have meant just as much, just saying React is not a framework but a library.
Beside that "Wrong! React is NOT framework please stop spreading this nonsense" is not the most commenly way of commenting blog posts. Just a tip for next time.
One fact and one opinion out of all this.
Fact:
React is not a framework
Opinion:
“Is not the most commenly (whatever this means) way of commenting blog posts. Just a tip for next time”
Well react is more a framework then a library. The distiction between the two terms can be looked from multiple persectives. But it doesent really make a difference call it what you want. No need to be mad about it.
nah - non alcoholic beer is not beer, its a mistake!
XD
en.wikipedia.org/wiki/Software_fra... from this perspective any one can call react as framework.
While this might be accurate, if you're suggesting React be excluded from this list, that would be a disservice to both React and the reader. Does changing the section title to "JavaScript Frameworks and Libraries" resolve this? The problem with that is that this opens the scope to thousands of useful JavaScript libraries, while the focus of that section is on those providing that list of important framework-like packages available to the developer. Excluding React here because it doesn't actually provide a framework is worse.
You should look up the word "pedantic" in a dictionary.
To give my 2 Cents to that Topic aswell -
As an React Expert myself - i do not care if its called Jquery 2.0, Library, Framework whatever.
But if i would starting learning React i would like to have the right Term - therefore "Library".
In fact, the creators of React (Facebook or Meta) call it a library
Instead of screaming "wrong". Maybe use this forum to explain why you think its not a framework rather than accuse people of spreading nonsense.
What? What’s in dispute is not an opinion, it’s a fact. It’s literally on the homepage banner of reactjs.org. Also, it’s not an accusation but a fact that this is spreading misinformation
Okay, let me rephrase, instead of calling it nonsense and just declaring "Wrong!". Maybe take a kinder approach of directing people to the correct information so people can learn for themselves.
It's not very helpful to people who trying to learn and make themselves better engineers and developers when you just declare them wrong, if anything it makes the writer feel worse about what they wrote.
Constructive criticism is a great way to learn, but also a great way to teach.
With all this great researched information, your problem is a nitpick. Even if it's not technically a framework, many people refer to it as such
That’s the problem, it is not “technically” a framework, it’s just simple not. People that refer it as a framework heard it from somewhere and it confuses people as to what React actually is. NextJs is a framework that uses React library. This is how it should be informed. I guarantee newbies are getting confused as to…”well, should I use NextJs or React and what’s the difference?”
And Nuxt js is a framework that uses the Vue.js framework
Well, I think you failed to read correctly, I said NextJs not Nuxtjs.
I said Nuxt.js :). Just saying that you also can make frameworks on top of frameworks like Vue.js and not only on top of libraries like React.js
Gotcha, point taken.
Chuy, this is such a poor way of communicating your thoughts/feedback on a public platform. You can do a lot better!
Perhaps, I’ll take your advice and I hope you take mine as well.
Seriously…. someone needs to pump the brakes on their ego
That's a bit harsh, and a bit of semantic nitpicking as well ... if you take React, and then (as almost everyone does) you install a few other tidbits alongside it (like react-router and a couple of other standard packages), well, then by all means you've got a "framework".
Having had this debate a hundred times and done research into the matter I have come to the conclusion: who bloody cares? Like it couldn't possibly be less relevant to this article. This whole debate is just semantics
I think you could find a much more tactful way of going about this. But, whatever. You seem like the type that absolutely NEEDS to show they are right. So, congratulations on proving that, while also looking like a complete ass. Yes, React IS a library and NOT a framework. But, constantly needing to point this out to people must get tiring.