r/javascript • • Jun 19 '18

Github Stars !== Usage: React is still blowing Vue and Angular Away

https://zendev.com/2018/06/19/react-usage-beating-vue-angular.html
361 Upvotes

127 comments sorted by

266

u/zulkisse Jun 19 '18

It's kind of sad that we always come to the same point : Trying to explain that OUR language, OUR framework, OUR library is better.

Of course the ton of posts "Which framework should I use" or "Is JavaScript a good language to start" are not helping. But could we avoid saying that X language or X framework is better without specifying a use case. And could we stop judging technologies we never really used (no a side project is not enough to conclude that React > Vue or Angular > 13" Peperoni Pizza).

Maybe I'm just being utopist :/

282

u/Drunken__Master Jun 19 '18

I like Angular, but there's no way that it's better than a 13" Pepperoni Pizza.

Pizza is the correct call in nearly 100% of it's use cases, hundreds of years have gone into engineering pizza, it has a very easy to use testing suite, you get the exact same result with loose or static typing and it doesn't ever need additional dependencies or libraries.

14

u/nwayve Jun 19 '18

Here's a use case to help support your claim:

describe('Pizza', () => {
    it('should be the first choice to throw on a roof in anger', () => {
        const pizza = new Pizza('Venezia');
        const person = new Person('Walter', 'White');
        person.hands.push(pizza);

        person.experience({
            emotion: 'rejection',
            from: 'spouse'
        });

        person.hands.should.be.empty;
        pizza.location.should.equal('roof');
    });
});

source

5

u/k3liutZu Jun 19 '18

“tasting suite”

9

u/ogurson Jun 19 '18

That was unfair comparison, there are only a few things better than pizza.

4

u/[deleted] Jun 19 '18

How can there be anything better than pizza?

7

u/ogurson Jun 19 '18

You know, two pizzas are better then one, right?

3

u/gabboman Jun 19 '18

easy: add pinneaple to pizza

-1

u/[deleted] Jun 19 '18

Pepperoni and pineapple is definitely the best pizza.

3

u/[deleted] Jun 19 '18

Lasagne?

7

u/Headpuncher Jun 19 '18

No, but Japanese girls.

3

u/jhanschoo Jun 20 '18

Not really; while testing, I found that fails inexplicably on the vegetarian pipeline when I replace the mock pepperoni libraries with the actual components.

3

u/Drunken__Master Jun 20 '18

Have you considered splitting the pizza component into "left" and "right" components and only importing the pepperoni library to the "left" component and then testing the "right" component with the vegetarian parameters ?

1

u/FabianDR Jun 19 '18

You, sir, clearly have never made a single pizza on your own.

2

u/Drunken__Master Jun 19 '18 edited Jun 19 '18

Why roll your own when there are so many turnkey solutions available ?

3

u/nathancjohnson Jun 19 '18

Right, you just gotta npm install the pizza.js package with its 1,000 dependencies.

3

u/Drunken__Master Jun 20 '18

yarn add pizza-to-my-mouth

1

u/[deleted] Jun 20 '18

I recently learned about the 'soured cream' package. It's really popular in a remote corner of northern Germany.

1

u/[deleted] Jun 25 '18

Can pizza scale?

0

u/[deleted] Jun 19 '18

[deleted]

30

u/Drunken__Master Jun 19 '18

Anchovies were deprecated though, so there has been some amount of progress.

13

u/apatheorist Jun 19 '18

The "oh gross, why would you eat that" warning doesn't work when you can use the --ignore flag in the linter.

5

u/SparserLogic Jun 19 '18

fish pizza fan for life. I wish places kept carrying them

2

u/tontoto Jun 19 '18

I've had spicy fish sauce instead of marinara and it was awesome

4

u/SparserLogic Jun 19 '18

A delicious polyfill

1

u/falcon_jab Jun 20 '18

That time when someone deleted the pepperoni module and broke the pizza bake system worldwide.

31

u/[deleted] Jun 19 '18

PINEAPPLE IS DELICIOUS AND YOU KNOW IT

11

u/Eeems_ Jun 19 '18

Yes, just not on pizza.

2

u/wicho91 Jun 20 '18

Try it on tacos.

2

u/Eeems_ Jun 20 '18

That also sounds terrible

3

u/wicho91 Jun 20 '18

Tacos al pastor with pinneaple is a really tasty meal

2

u/[deleted] Jun 20 '18

Pineapple Salsa is the stuff of dreams

2

u/wicho91 Jun 20 '18

You know your shit.

3

u/[deleted] Jun 20 '18

Especially on pizza, you monster!

2

u/Eeems_ Jun 20 '18

Are you calling me a monster? I agreed with you about it being horrible on pizza!

1

u/[deleted] Jun 20 '18

No, pineapple is especially delicious on a pizza!

1

u/Eeems_ Jun 21 '18

I'm sorry you feel that way

1

u/falcon_jab Jun 20 '18

Along with all the other fruits we put on pizza and... OH WAIT

1

u/[deleted] Jun 20 '18

Yes. Tomato.

1

u/falcon_jab Jun 20 '18

Depends if it's a botanist making your pizza

1

u/[deleted] Jun 20 '18

When it comes to plants, I would trust a botanist over the US government any day. Especially since Obama wanted to make school lunches healthier, and congress retaliated by defining pizza as a vegetable too.

4

u/sacrich_cc Jun 19 '18

Well, if there’s a userbase willing to pay for it ¯_(ツ)_/¯

13

u/LimbRetrieval-Bot Jun 19 '18

You dropped this \


To prevent anymore lost limbs throughout Reddit, correctly escape the arms and shoulders by typing the shrug as ¯\\_(ツ)_/¯ or ¯\\_(ツ)_/¯

^^Click here to see why this is necessary

1

u/xemasiv Jun 22 '18

Not a bad bot, but a dick bot.

1

u/itsmoirob Jun 20 '18

Pineapple module is my go to module.

35

u/stolinski Syntax.fm / Level Up Tutorials :upvote: Jun 19 '18

Right on. I 100% agree. React & Vue are both amazing and we as devs should be happy to have either of them.

18

u/[deleted] Jun 19 '18

It's kind of sad that we always come to the same point : Trying to explain that OUR language, OUR framework, OUR library is better.

OP's post doesn't make any claim about which library is better. It's addressing another post about GitHub stars being used to measure Vue's adoption rate when in fact GitHub stars do not measure usage. NPM install rates are a better measure for that.

On a side note, it's not that case that all libraries are equally as good as each other. It's popular to say that the quality of a tool or library is a matter of personal opinion. While there is plenty of room for subjectivity, there are often libraries which are simply better than others.

For example, you might happen to like Grunt as a build runner and be able to state a "use case" for it. But you would absolutely be doing someone a disservice by recommending it over webpack.

17

u/Poltras Jun 19 '18

If anything, npm downloads are only valid to know which framework has more CI...

3

u/davesidious Jun 19 '18

And less caching.

16

u/[deleted] Jun 19 '18

NPM install rates aren’t even a good metric. I use Vue just by including a script tag on a couple sites at work. Chinese people don’t even use NPM. Everyone knows React is more used and has more job postings. Having more GitHub stars only means you have more GitHub stars, just a fun metric without much real world implication after a certain point.

5

u/[deleted] Jun 19 '18

Chinese people don’t even use NPM.

Could you elaborate on this. How do they package and distribute modules?

11

u/nmarshall23 Jun 19 '18

The great firewall of china means that your access to a western CDN, or NPM might go down. On one project that I worked on I was told to use an approved Chinese CDN, or ship the project with all of the NPM packages in the repo.

0

u/[deleted] Jun 19 '18

[deleted]

1

u/Maswor Jun 20 '18

This one is funny, why the down vote??

2

u/zulkisse Jun 19 '18

And I agree at 100% with everything you say.
I have nothing against this article, it's quite interesting and not at all what I am talking about here.

And of course not all libraries are eqully good. That's why I was only talking about global judgment without a use case. React is not better or worse than Vue, but yes there are enough points to differentiate them and to have a winner in certain scenario (Vue for HTML templates if your designers modify them directly a lot for instance).

1

u/Buttershine_Beta Jun 20 '18

Where is a link to NPM install rates?

Edit: nvm found it... :)

0

u/[deleted] Jun 19 '18

[deleted]

6

u/[deleted] Jun 19 '18

You can replace all of them with a fairly simple script that just calls the dependencies instead.

This might be true if you're developing a library but it's absolutely false when developing an app. Webpack can automatically chunk and code split your code in locations that are unknowable a priori, import file types differently based on context, etc. These are not things that can be easily done with npm scripts. If you manage to get it working with scripts then you'll end up reinventing a bad version of webpack.

but I think you're looking at them from the wrong height because there is nothing inherently bad about recommending grunt over webpack.

I can't stress enough how much I disagree with this. In fact, the entire point of my previous post was to reject exactly what you're claiming. I think that view is really quite harmful to new developers.

I don't think I lack perspective. I've used all of the tools that you mentioned and understand the problems they solve. I'm also familiar with their deficiencies. I wouldn't recommend using grunt over webpack/npm scripts in a new project.

2

u/newmediapilot Jun 19 '18

You're right, all frameworks can do everything and the all have pros and cons, choose wisely and be a master of something.

2

u/MatthewMob Jun 20 '18

They're tools, and all tools should be used for different cases.

It's impossible, as you say, to make a judgement of its general usage in any situation. Use the right tool for the right job, you don't judge a hammer on its ability to saw wood.

1

u/BigJono42 Jun 20 '18

I'm of the opinion that every single statement is completely bunk without a side-by-side comparison of relevant code.

I don't give a shit how well your library "scales" unless you can show a concrete example from a large project.

1

u/DerNalia Jun 20 '18

Speaking of not judging technologies that haven't be used, looks like this recently posted blog article is trying to address that a bit https://twitter.com/nullvoxpopuli/status/1009120627939307522

There is a crazy amount of tribalism in the javascript world... and I think that part of that has to be due to just how long it takes to learn and get good at a particular ecosystem. People who learn React may look at how Angular structures things and immediately write it off as weird, on un-ergonomic, when in reality, dependency injection is the best developer experience missing from React at the moment. :-\
idk

1

u/greg5ki Jun 20 '18

You sure are. It's human nature to compare and make oneself feel better by belittling and bullying inferior frameworks such as Vue and React... ;)

0

u/8412risk Jun 22 '18

Personally I hate the entire JS “community”, but not as much as they hate each other.

-2

u/skytomorrownow Jun 19 '18

Maybe I'm just being utopist :/

I think so. Humans are like water, we seek the path of least resistance. Who wants to dig into first principles, and truly understand a problem domain when you can just ask what everyone else is doing? Human nature.

102

u/evilpingwin Jun 19 '18 edited Jun 19 '18

I posted something similar over in the React sub but I don't think anyone really thought the star thing did mean Vue has more users. Certainly no-one with half a brain thought this was the case, Evan even tweeted something to that effect. Dan was just congratulating the Vue team on what they'd built.

Yet, even in the comments here, more library tribalism:

I would think that this is common sense, but that doesn't seem to be the case among Vue's fans.

Apparently a few people who don't know what they're talking about overreacting to Vue's star count means that Vue fans don't have common sense and think stars === usage.

We've created this weird situation in front-end dev where you have to be in a library/framework camp and once you go in that is what you will forever be associated with. Gary Bernhardt has spoke in the past about emotional/ moral attachment to tools in software, and he's so right its not even funny. For a discipline defined by (and that constantly goes on about) logic and critical thinking it's alarming how little some developers show when it comes to their tooling or challenging dogma.

Can we not just build cool stuff.

39

u/Pleochism Jun 19 '18

A well-argued point. Now, if you'll just step over here onto the bonfire, we can begin the burning.

10

u/[deleted] Jun 19 '18

No kidding, it's one thing to get these generalizations about 'fanbases' on sports and entertainment subs, but do we really need to do that here? I use Vue for some projects and React for others depending on who I'm working with and what the project needs, does that mean I'm a Vue fan or a React fan? Why would you even want to choose a side when these libraries change so often?

It's such a weird need for people to be 'us vs. them' that it bleeds into things like this where it really shouldn't apply at all.

5

u/atubofsoup Jun 19 '18

No need to learn new tools when you already learned the best ones. \s

15

u/Kavec Jun 19 '18

But the reaction is normal. If you are proficient in framework A, probably you are not as proficient in framework B. If A is stablished as the dominant framework, you will be ahead in the job market race. If B becomes the standard, you will be a bit behind in that race. Your bread and butter is directly related to that, so for the people that is not a top-tier programmer it make sense to cheer on A and boo on B.

3

u/AceBacker Jun 19 '18

Well to be fair. The star count is not meaningless. It's a good framework.

1

u/Treolie Jun 20 '18

I’m not in a camp. I’d love to use any which is something i always bring up on interviews. In the end they’re not that different anymore and i put more weight on what the project tries to solve.

42

u/stolinski Syntax.fm / Level Up Tutorials :upvote: Jun 19 '18

While this is true, I'm not a fan of this whole React vs Vue, us vs them kind of conversation. Just having the option for either of these amazing frameworks is what matters. Cheers to both React & Vue teams.

14

u/brianvaughn Jun 20 '18

We're not fans of it either. 🙂

React and Vue (and Svelte and Angular and others) are collaborating more than we're competing. We share the same basic goals (and a lot of overlapping community as well).

-13

u/dardotardo Jun 19 '18

There’s a serious lack of angular mentioned in your comment...I dig it.

20

u/DanijelH Jun 19 '18

I don't think anyone actually said that this is the case, I mean NPM alone is not the way to show which one is being used more but I think that React still has the edge here obviously.

But there is something else that is interesting for me.

React who has Facebook and millions of dollars behind them for development, marketing etc vs. Vue and one guy (in the beginning) with limited budget. Also, Vue exists shorter but nevertheless here we are. This is what fascinates me, the growth that Vue has.

24

u/ShortSynapse Jun 19 '18

stars !== usage

We know. The star tracking was a fun little event to watch. Sometimes it's okay to have a little bit of fun and not take everything so seriously. Yes react is more popular, yes Vue is rising in popularity, yes it still has a long way to go before matching react. I can't help but feel that articles like these are a waste of time considering they only reiterate what everyone already knows.

8

u/ib4nez Jun 19 '18

I’ve never met someone who’s worked on a production level project in all mainstream JS frameworks and come to a conclusion about which is best, because it’s simply an impossible question to answer. It’s the wrong question to ask

4

u/jkoudys Jun 19 '18

I have! At least of React, vue, ng. Which is my favourite to work with? React by far. Which is "best"? It really depends who's asking, and what you value on that particular project. I like React because it's just a vdom and a handful of lifecycle methods, and doesn't bog you down with a bunch of v- or ng- prefixed attribute microlanguage. You barely even need to "learn React", really; if you can write good presentation logic compositionally, you can write good React. It's Array methods instead of v-for, and an actual if instead of ng-if.

That said, there are lots of devs who like that kind of thing, and if you're moving a team that's had plenty of experience on some late-binding jQuery app over, React may be too big a jump for them to do well, but vue a good fit. You could be perfectly happy binding a little vue logic into an existing html-heavy codebase, and generally moving some existing html elements into vue/angular bindings is a lot easier than totally replacing them with React components.

4

u/spryes Jun 19 '18

I used to enjoy Vue, but once you realise how JSX works and the goal of a VDOM, you'll come to prefer React instead. The view is "just JavaScript" (function calls) disguised as XML tags. This means you can just use regular JavaScript logic to construct views rather than proprietary attributes: .map instead of v-for, conditional expressions instead of v-if, etc.

Also, Vue has many caveats because of its mutation detection. This can leave you wondering what's going on when updating the data of a component, since it embraces mutation instead of purity. Even Dan Abramov said in a tweet this is the biggest downside of Vue's architecture. Rather, you should call something like this.updateData() that does a partial merge with the current data and enforce you to keep the data pure to prevent strange cases like this. I had so many issues with this when learning Vue.

Vue is really accessible and has the appeal of separating HTML, JS and CSS, but I think it encourages bad practices. React seems really foreign and strange, but I believe its architecture is the best we have currently to develop reactive apps. (Or Hyperapp, a lightweight version of React that is even better imo).

4

u/jkoudys Jun 20 '18

While I've been doing the views with xml-ish syntax since even before react (in xhp), I've recently moved away from JSX and see it as superfluous. Ecma is a plenty good declarative language on its own. Implied prop names and trailing function args make it very clean. Especially as we get more stateless in our child components, I find we're more frequently passing down the same prop name over and over. We can spread our jsx props, but that's basically extra syntax just to use vanilla ecma.

<Foo bar={bar} baz={baz} />

Doesn't feel any cleaner than

h(Foo, { bar, baz }),

I think I mostly just liked jsx because it felt familiar, but when I really challenged my beliefs there's nothing objectively more clear about it.

2

u/BusStation16 Jun 19 '18

You seem to imply React does not encourage bad practices, in my experience it encourages the worst of the three.

11

u/spryes Jun 19 '18

Okay, but an explanation of why would be nice?

1

u/drdrero Jun 20 '18

Try to set CSS dynamically. As a designer, not programmer.

"This" binding on every event listeners. I thought we were over that kind of stuff already.

Conditionally render a simple text:

{1 > 0 &&  
    <p>You && an element!</p>  
} 

Silly React.

8

u/brianvaughn Jun 20 '18

Care to elaborate? 😊

1

u/[deleted] Jun 20 '18

One programmers best practice is another programmers WTF.

I don't disagree with you, because everyone has their own opinions about what something a "best practice". Time also erases those best practices almost without exception.

1

u/eloc49 Jun 20 '18

Yep, different use cases. Vue is better for somewhat static stuff, React is better for logic driven apps. Are we all writing the same thing? No!

8

u/OrangePhi Jun 19 '18

npm downloads are not a good indicator of usage since a significant amount of vue users don't use npm to pull the framework.

One of the nice things about vue is that you can just edit your html file to include vue from a cdn and get to work instantly without additional tools. I've seen projects on GitHub that import vue like this and then use npm for other smaller libraries. You can't really do this with React since you need to run babel and webpack on node to compile JSX.

7

u/[deleted] Jun 19 '18

I wish these tredy==technically good articles would be kept to /r/webdev. Or else, I wish there was a sub where you could discuss building things instead of thousands of framework popularity contest articles.

27

u/tacobooc0m Jun 19 '18

Who cares tho? This preoccupation with using popular tools has always baffled me. I can understand the perception that popularity might be a proxy for support, but these discussions always lean sorta religious.

0

u/[deleted] Jun 19 '18

[deleted]

2

u/CaptainShaky Jun 19 '18

Absolutely this. When getting started it's nice to have a big, active community to help with the learning process. More users = more guides, articles, cheatsheets etc...

4

u/thebasher Jun 19 '18

more stackoverflow questions and answers is big for me. always helpful to see an answer with a high vote count and comment discussion to acknowledge that 'this is the best way of using X tool'

2

u/tacobooc0m Jun 19 '18

I may be showing my age but I learned prior to these resources so I have a different perspective on what's good or bad to use. I learned thru books and school, where longevity was measured in years. It's so easy to flood the sites and search results with answers so maybe that is why everything can move so fast; so many resources to help those completely new.

1

u/[deleted] Jun 19 '18

Who says you have to use a framework at all? They slow down a site a lot, and are almost always used for what could be done with a very small amount of Javascript and a couple small modules.

6

u/waczdraco Jun 19 '18

I have tried those three js framework react, angu and vue all of them are great. But, I still prefer Vue due to three simple things like easy implementation, lighter size and very fast. Learning curve is much shorter especially to those coming from native js or jquery as an example.

4

u/Georgegriff25 Jun 19 '18

React !== The whole JavaScript community. For me, React has too much "baggage" of tools that do this and that just doesn't work for me. Though I'm often coming from a standpoint of updating and maintaining legacy applications, persuing libraries that are built more closely on top of Web standards makes more sense for long standing applications with a long shelf life.

4

u/SentientPeach Jun 19 '18

Not too long ago the web community would've killed to get just one of today's amazing frameworks. Now we have fights over which amazing framework is the amazing-est.

3

u/gabdelacruz Jun 20 '18

I smell insecurity on that kind of titles.

6

u/magenta_placenta Jun 19 '18

It doesn't matter, people will chase trends and biases. People will make choices and will possibly use both (or something else), it’s not like picking Vue will kill React or vice versa.

9

u/coskuns Jun 19 '18

NPM !== usage either.

There are plenty of CI/CD environments out there running thousands of times a day and downloading packages from NPM.

That being said, it is normal that React has more downloads since it has been popular for a longer time than Vue and Vue recently got some traction.

I, as someone having approximately 20 years of web development background, find that Vue has a shorter learning curve than React.

Apart from that they are almost one and the same. Neither one is better or worse. Vue is just simpler and lighter.

2

u/dardotardo Jun 19 '18

All things equal, CI / CD pulling from NPM would still be a decent gut check since downloads would be high, yes, but normalized out, it’d still say that React is used in more projects overall.

That or vue devs build less than react devs, or are just better coders...or both!

2

u/[deleted] Jun 19 '18 edited Jun 19 '18

Vue and React have almost the same age. The rules that apply to npm apply to both of course. That goes to CI environments and script-imports. The same proportion is reflected everywhere: npm dependents (libs that include Vue/React in package.json), eco system, github dependents, job market, and so on.

The impression i have is that Vue, either by intent or accident, used gorilla type marketing, or "hype", and some of it quite artificial in that opinions sometimes seem uninformed bordering false (small learning curve, easier, ...). Some false advertising as well if you remember the old Vue docs. It just didn't translate into growth.

Considering that both almost started out at the same time, React, from the get go, shot through the roof by innovation and a clear cut vision of where it wanted to be, and they've followed it through, even if that meant making unpopular decisions like the refusal to cater to the webs artifacts.

I'm obviously biased, though i do know both by heart and use both at work, but to me there's about no surprise as to how the market's panned out. That said, it is still amazing that one developer has single handedly made something that now rivals Angular, and if you like that approach there's now arguably a better option, which is fantastic.

2

u/jkoudys Jun 19 '18

gorilla type marketing

That's how they promoted Donkey Kong!

2

u/ben_oftheuniverse Jun 20 '18

lol nobody thought this but thanks for highlighting your insecurities

the real question is why capitalize Away? is that a react thing? hahah

3

u/coskuns Jun 19 '18

NPM !== usage either.

There are plenty of CI/CD environments out there running thousands of times a day and downloading packages from NPM.

That being said, it is normal that React has more downloads since it has been popular for a longer time than Vue and Vue recently got some traction.

I, as someone having approximately 20 years of web development background, find that Vue has a shorter learning curve than React.

Apart from that they are almost one and the same. Neither one is better or worse. Vue is just simpler and lighter.

2

u/ataraxy Jun 19 '18

I like how OP took the bait.

1

u/achillean Jun 20 '18

Here is a ranking based on the number of websites using Angular, React or Vue:

  1. AngularJS (~192,000 results): https://www.shodan.io/search?query=http.component%3Aangularjs

  2. React(~122,000 results): https://www.shodan.io/search?query=http.component%3Areact

  3. Vue (~35,000 results): https://www.shodan.io/search?query=http.component%3Avue.js

This doesn't take into account projects that use React Native, vhosts etc but it still shows the usage difference between the various JS frameworks. Personally, I'm surprised how many websites still use Angular - looks like it is a lot more popular/ common than one would imagine from Github stars/ npm downloads.

1

u/silversik Jun 23 '18

Fucking javascript create modern javascript framework

-5

u/[deleted] Jun 19 '18 edited Jun 19 '18

I would think that this is common sense, but that doesn't seem to be the case among Vue's fans.

Personally, I star projects that I want to keep an eye on, not projects I use every day. I don't even use Vue, but I've got it starred because I think it's interesting and I want to watch it's growth. I don't have React starred, though, because it's a foregone conclusion that I'm going to stay up to date with it, as I'm pretty heavily invested in it at this point.

edit: Uh-oh, I think I might have offended some Vue users! Better downvote me, that will really put me in my place ;)

6

u/LetReasonRing Jun 19 '18

Yeah, I tend to treat stars more as bookmarks than as a vote. I don't know know that I have any of my favorite or most-used starred, but I have plenty of "I need to come back and check this when it's matured a bit more" or "that's a nice style guide, I'll star it so I can refer to it later" stars.

10

u/d_abernathy89 Jun 19 '18

doesn't seem to be the case among Vue's fans.

Maybe some of them. I'm all-in on Vue, have never written a thing in React, and I'm well aware that React is dominant in real-world usage despite the Github stars. I think most users agree.

9

u/[deleted] Jun 19 '18

edit: Uh-oh, I think I might have offended some Vue users! Better downvote me, that will really put me in my place ;)

These edits are always hilarious, you're giving yourself too much credit. You didn't 'offend' anybody you're just one of those weird 'pick a side' people that attaches the framework they use to their self-identity so you say things like "Vue's fans" and "offended Vue users". It's strange because it's like you're trying to create conflict where there is none. I think most people just use the best tool for the job instead of sticking to something because you're a 'fan'.

0

u/[deleted] Jun 19 '18

I really don't give a shit what people use. Vue is great, it's just not my preference. I'm not trying to "create conflict", I'm just poking a little fun at people like you who take this stuff waaaay too seriously. Lighten up!

7

u/PissBlaster2k Jun 19 '18

but that doesn't seem to be the case among Vue's fans.

Why you gotta bash a huge group of people because of a few loudmouths?

-11

u/[deleted] Jun 19 '18

Why you gotta be so sensitive over something that has approximately zero impact on your day-to-day life?

10

u/PissBlaster2k Jun 19 '18

I'm not, just feel like theres no need for this "us vs them" mentality. I guess no point in trying to talk sense to a React user... /s

-5

u/[deleted] Jun 19 '18

I don't feel that way at all. I've got nothing against Vue, I just think some of it's users have been getting a little carried away with the fact that Vue has more stars than React.

1

u/Siliticx Jun 19 '18

If React is Summit1g, Vue is Ninja.

3

u/[deleted] Jun 19 '18

An odd reference, but ok.

1

u/roger_comstock Jun 20 '18 edited Jun 20 '18

Read as: "If, as an investment, I only learn one, should I learn React or Vue?" The article says "React, because usage is higher."

Whether this is a good investment in the long run is hard to say. There is going to be lots of React to support in the future. There might be lots of new React projects in the future.

My personal recommendation to someone thinking about it this way:

  • You will be able to very quickly pick up Vue on the job when you encounter it.

  • React will take longer. Learn React at home in case you need it. Also, it's fun.

  • Pick Vue for new projects.

Addendum: It might be safe to assume that React's acceleration is comparable to Angular's a few years ago. I don't know what that would make Vue, but I'm pretty sure it's not Knockout or Ember.

1

u/[deleted] Jun 20 '18

Who are the sociopaths who put a star on her favorite framework?

I put stars on things that I can contribute to, or I don't want to forget where the repository is, like a bookmarks system.

Are these people really read the frameworks source code before going to sleep? Are they re tripping looking at the code?

Star a repository with many stars does look cool in your github profile?

So many questions.

-2

u/[deleted] Jun 19 '18

I think the community is slowly going back to basics like jQuery and vue.js because of how unnecessary complex it is to configure these frameworks from scratch. Why the fuck do JavaScript frameworks have more configurations than my web.config.

0

u/[deleted] Jun 19 '18

[deleted]

4

u/fyzbo Jun 19 '18

More that people started using SPAs for EVERYTHING without regard of the project requirements.

  • GMail === SPA good choice

  • Wikipedia === SPA bad choice

Hopefully we will see a normalization where SPAs are used where appropriate. Which can often be a hybrid approach (browsable pages == traditional, admin center === SPA)

-10

u/eggn00dles Jun 19 '18

Angular is such a fucking shitshow now.

They should be on Angular 2.6 now instead they think companies can hire someone to exclusively focus on keeping track of their constant version breaking changes.

As soon as I can be I'm done with it.

3

u/[deleted] Jun 19 '18

I could be wrong because I don’t keep up with angular anymore, but aren’t their major versions on a schedule?

-2

u/[deleted] Jun 20 '18

They all suck equally.

16

u/[deleted] Jun 19 '18

[removed] — view removed comment

6

u/fyzbo Jun 19 '18

Then after writing it they have to downvote anyone pointing it out. Here is +1 to compensate.