9 ms·
Has Vue passed React yet?
- stevev 8y agoWoot! Go Vue.
- dopamean 8y agoWhy should anyone care how many github stars one library has compared to another?
- deleted 8y ago[deleted]
- wmil 8y agoGithub stars are proportional to the size of the community. You don't want to bet your company on a project with only a few thousand stars, it could die quickly.
- beefsack 8y agoAngular has a monumental enterprise userbase, and I wonder what percentage of those developers even have a GitHub account. GitHub stars are a more a measure of hype than the size of the community.
- baybal2 8y ago>Angular has a monumental enterprise userbase, and I wonder what percentage of those developers even have a GitHub account. And much of it is still on 1.x
- atombender 8y agoAnecdotal counterpoint: I star projects to bookmark them, so that when I have a spare moment I can go through the list and find interesting repos that I might use. But I typically don't unstar later if I stop using something. I should, but I just don't "clean" my collection that often.
- Torn 8y ago+1 for this - I star things to come back to and try out. I've started Vue for this reason, unlike React which I use in working hours
- staticassertion 8y agoYeah, same way I 'favorite' something on Twitter. I might disagree with the tweet, but I want to come back to it later to read the conversation, etc.
- iliaznk 8y agoSecond that, and just like any bookmarks – I rarely return to them afterwards )
- danso 8y agoI agree there's a decent correlation. There are a few notable exceptions/edge cases. For example, Ruby's rake has just ~1,300 stars: https://github.com/ruby/rake https://github.com/ruby/rake It'd be an interesting project to compare frameworks/tools by aggregating the stars (or whatever metric) of its major (i.e. filtering out hobby forks and skeleton repos) dependent projects, e.g. the 22K stars of gatsbyjs/gatsby would count towards React's overall reach/popularity.
- khazhou 8y agoLoading... (iPhone safari)
- GameOfTrolls 8y agotime for an iphone X
- andyfleming 8y agoVue: 238,410 weekly downloads React: 1,596,809 weekly downloads (from npm)
- burlesona 8y agoYeah I think this is a much more relevant metric. But also, who cares? Both are good tools.
- andyfleming 8y agoYeah, I'm all for the growth of vue in addition to react. Just thought it was a relevant metric to share.
- devmunchies 8y agocombine that with number of projects with react or vue in the package.json in github.
- Reedx 8y agoI wonder though, how CDN links might mess with this comparison? And whether devs are more likely to use the CDN version with Vue vs React.
- deleted 8y ago[deleted]
- sotojuan 8y agoMicrosoft just announced they are betting big on React, and a quick search at JS/frontend job posts only show React and the odd Angular/Ember ones in my area. Stars might matter to some but it looks like React is here to stay and be the most supported and used library for some time.
- interlocutor 8y agoCan you point me to the announcement? Hopefully you're not referring to that recent weird tweet that has been disputed by several MS employees.
- phereford 8y agoYou can see the older HN article here: https://news.ycombinator.com/item?id=17310738 https://news.ycombinator.com/item?id=17310738 Looks like they are moving their office suite of software to React.js.
- WoodenChair 8y agoIt looks like it may only be a "thin veneer" on the top of it: https://twitter.com/migueldeicaza/status/1007016681426898945 https://twitter.com/migueldeicaza/status/1007016681426898945
- interlocutor 8y agoThat's based on a nonsense message posted by a rogue employee. https://mspoweruser.com/no-microsoft-is-not-rewriting-office-in-javascript/ https://mspoweruser.com/no-microsoft-is-not-rewriting-office...
- robotkdick 8y agoReact is the heavyweight, no doubt, but it also feels heavy for smaller projects. VUE is a great option and believe it or not Meteor just announced 1.7 with at least one killer feature: Babel-free JS for modern browsers. https://blog.meteor.com/meteor-1-7-and-the-evergreen-dream-a8c1270b0901?gi=c82300da60f4 https://blog.meteor.com/meteor-1-7-and-the-evergreen-dream-a... It's good to see Vue gaining steam as more options = better fit per project.
- matthoiland 8y agoReminds me of http://isitsnowinginpdx.com/ http://isitsnowinginpdx.com/. I'm rooting for Vue.
- deleted 8y ago[deleted]
- crooked-v 8y agoAs somebody who really likes Vue, I feel like it's hampered by comparison by not being able to use "real" JS in the bulk of the view templates. There's a lot of minor boilerplate annoyances in outputting stuff that go away when you can do array maps and Ramda functions as a direct part of your rendering.
- ineedtosleep 8y agoStars don't matter. If we want a measure that's actually meaningful to some developers, look at job postings. Anecdotally from my on and off job searching, React leads here by orders of magnitude. And unfortunately for me, my Vue personal experiments/side projects have to be put in the sideline for a bit. Many people I've talked to want direct React experience and not just experience in reactive frontend stuff.
- hashkb 8y agoI use React every day and haven't starred it. I star random stuff I want to come back to later (like Vue).
- Cofike 8y agoYeah it's tough. Do you go into a new technology and have issues finding jobs or do you use the tried and true, risk stagnating and costing yourself future jobs.
- optimiz3 8y agoMeanwhile we're still using ASP.Net MVC w/ a vintage 2008 web design. Could care less about $latest_web_technology, because having a viable business is more important than what the site is coded in or how it looks.
- paulie_a 8y agoWhile that is a valid point and a company should never leapfrog to the new hotness. Using outdated technology can have major pitfalls with technical debt. Also looks, ie ui/ux does matter greatly. A modern Android app wins vs something built for 4.0
- cyberferret 8y agoDo we consider js frameworks to have 'jumped the shark' when they descend to the same sort of popularity polling as a reality TV contest? :) (I am tongue in cheek here - I realise stars <> actual usage in the wild, and the results can be gamed). For what it is worth, as a 35+ year veteran in the software coding world, I tried dabbling in both frameworks, and Vue seemed to make more sense to me and fitted my mind's view of how things should work.
- interlocutor 8y agofitted my mind's view of how things should work Why so? Could you add some detail to this comment?
- deleted 8y ago[deleted]
- polymerase 8y agoProvocative and simply wrong.
- pwaai 8y agomeh, I've given up. At the end, it's whatever your client wants and will ultimately pay for. React is popular in enterprise circles, Vue.js is also popular amongst new front end developers and seasoned. In a few years it won't matter as deep learning will generate front end UI with just a wireframe sketch.
- Shank 8y agoI kind of think this herd mentality in the tech industry is annoying. There are a lot of people using React, but that doens’t make Vue a bad choice. Conversely, just because Vue is new and relatively popular doesn’t make it the “new React.” Pitting them against each other like this is disingenuous, as engineers will make choices and use both — it’s not like picking React will kill Vue or vice versa. That doesn’t say anything about the likes of Ember and Angular that are still in use. A good comparison is backend stacks. Rails exists, but so does Laravel and Django. If it were truly a big deal which was the biggest, then only one choice would remain. Instead, they all have healthy ecosystems with companies using all three. It doesn’t have to be a war.
- bmelton 8y agoI agree that they're very different, but at the same time, there's a non-trivial base of users who earnestly believe that when you're picking a JS framework to use for <insert whatever>, momentum is a meaningful factor in it. Obviously, it rarely makes sense to select a framework that is completely disused, or unsupported, but there are articles out there by reputable sources who assert that if you're not using the current hotness, you're going to miss out on every new tool that crops up in the ecosystem, and your startup will languish and die as a result of having to spend so many more cycles just to keep up with what other people can 'npm install'. What's worse is that they're not entirely wrong. Any good plugin for Vue right now is going to show up in React or Angular post-haste, if it doesn't exist there already. Edit: I also can't help but wonder how many people saw this article, clicked the link, realized it was based on stars, and then went and starred Vue (exactly as I did). Every time I refresh, Vue is closer to 'toppling' React (at least according to these nonsense metrics)
- taylorswift_ 8y ago> What's worse is that they're not entirely wrong. If your startup dies because of your choice in javascript framework, you were doomed from the get go.
- burlesona 8y agoI don’t think there’s a war. I think there’s a fanboy who was amused by this and took 5m to put a page together.
- threatofrain 8y agoTo me the most obvious technical competition for Vue is Angular, not React, and if Microsoft were going to choose something other than React, I would've presumed it would be Angular. Both Angular and Vue have a similar component DSL and contrasts from React by trying to have a complete out-of-the-box experience, rather than the build-your-own framework style of React. But Angular is backed by Google, and it supports TypeScript out of the box as well as RxJS, which is somewhat of a cross-platform API for async. Unfortunately I think the Angular reputation still suffers from its Angular 1 days.
- exclusiv 8y agoI think you're spot on about Angular 1. I really like Angular myself despite that transition issue but I also like React and Vue. I currently use Angular for larger web projects (it's more complete out of the box), Vue for smaller web apps and widgets and React Native for mobile.
- mmcnl 8y agoI disagree. Vue is just a view layer, as is React. Angular is much more. Also, a lot of people are saying Vue and React are so different, but to me they actually seem very similar. They require the same kind of component-thinking and they both let you declare your view as a function of state in a similar way (JSX vs DSL). They both have similar problems with similar solutions.
- aylmao 8y agoThis frames it a lot as a competition; it really isn't. Facebook Open Source is a contributor to Vue. I think it just resonates with the community that this is a Patreon-backed, very community-driven project, whereas React has Facebook behind it, and Facebook has been controversial. Not that that has much to do with React itself-- if anything it means it probably scales well. Either that, or it's another iOS vs Android situation, where people just like picking teams.
- projectramo 8y agoMicrosoft rewrote the whole thing in React Native! It’s like keeping score of the opposing team in the match when they have already qualified for the Olympics. Play the long game.
- bhouston 8y agoAccording to Google search traffic, React is 10x popular: https://trends.google.com/trends/explore?date=today%205-y&geo=US&q=%2Fg%2F11c0vmgx5d,%2Fm%2F012l1vxv,%2Fm%2F0j45p7w https://trends.google.com/trends/explore?date=today%205-y&ge... According to NPM download stats, React is 6x larger: https://www.npmjs.com/package/react https://www.npmjs.com/package/react https://www.npmjs.com/package/vue https://www.npmjs.com/package/vue For Vue to catch up to the number of React stars would mean that their rate of starring is significantly higher. I wonder if rate of new Github stars are a leading indicator of future popularity increases? Probably? Would be interesting if someone could study that. Weird thing, commits to Vue are decreasing over time and are mainly done by a single individual - I've never seen that pattern in a popular library: https://github.com/vuejs/vue/graphs/contributors https://github.com/vuejs/vue/graphs/contributors While commits to React are regular and come from a much wider base of contributors: https://github.com/facebook/react/graphs/contributors https://github.com/facebook/react/graphs/contributors The writing is clearly on the wall (or the stars are on github), Vue is definitely going to overtake React usage in the long run unless another new library appears or React changes significantly.
- mygo 8y ago> Weird thing, commits to Vue are decreasing over time and are mainly done by a single individual The Sistine Chapel was mainly painted by a single individual. (for the record, Michelangelo had apprentices to help him mix plaster, etc. But he phased them out when it came to painting. Traditionally master painters had apprentices which would paint with them, but he would rather avoid the differences in opinion and arguments while painting the chapel. He had the vision and the skill. I think that’s the case here as well. Not saying Evan is Michaelangelo, but he does have a good vision with his product and the skill to execute on it.)
- stevev 8y agoExactly, the dude has a background in arts and design. Something that I truly believe helped shaped vue.js to what it is.
- deleted 8y ago
- ggregoire 8y agoI often read “I chose Vue because it feels easier than React”. Programming in React requires some basics in JavaScript and functional programming. It helps if you already have a dev background, but if not, then you will learn things really useful for a developer. And not only for frontend dev. Then you just have to learn the React API: 4 concepts (component, state, props, render) & 3 functions (didMount, didUpdate, willUnmount).
- bhouston 8y agoEase of use matters.
- wetpaws 8y agoI found the biggest barrier with react in understanding concepts, not learning API. API is 3 methods as mentioned above. Once you got the concepts you will never go back to old ways.
- Kihashi 8y agoThat's why I started working with Vue. It seemed easier to approach for someone coming from a server-side language perspective (I'd mostly worked with Python/Flask and PHP/Symfony before). I could slowly ease into using pieces of it until I learned enough to write a whole project in Vue. You can probably do the same thing in React, but the Vue docs were written to address my use case.
- kbd 8y agoI wish Ebay's Marko got any mindshare. It'd be nice if our choices weren't limited to React and Vue. https://markojs.com/ https://markojs.com/
- bobjordan 8y agoThat link is blocked in China.
- ryanmarr 8y ago22...17...15.. It's about to happen.
- 6nf 8y agoIt's happening!
- internalfx 8y agoPeople are actually un-starring react.
- pdfernhout 8y agoI prefer Mithril.js, used from TypeScript, with Tachyons for inline-ish CSS. That is what I use when I have a choice like for personal projects that are single-page applications (e.g. StoryHarp, NarraFirma, Twirlip7 on github). That way almost all code is in one language and can be easily refactored. Mithril is most naturally used via a "HyperScript" API where you define DOM/vdom nodes via function calls -- e.g. m("div.ba.bw2", m("span.blue", "Hello World")). Templating systems (including JSX for React) are unfortunate crutches which ultimately make development harder because they get in the way of refactoring, modularizing, and testing. And typical semantic CSS use (e.g. .warning vs. .red) often ends up in a messy snowball where people eventually are too afraid to remove anything -- whereas if you make your components in JavaScript code, you don't need semantic CSS. It turns out that "best practices" for server-driven Web 1.0 applications (e.g. HTML-ish templates and semantic CSS) often are "worst practices" for JavaScript-first single-page applications. React also is overly complex because it tries to over-optimize redrawing speed through encouraging components to maintain a lot of local state using setState -- even though the increasingly popular Flux model encourages global-ish state for one-way data flow that makes the internal workings of UIs easier to reason about. Mithril is more Flux-ish out of the box in terms of the design patterns it encourages. Mithril's default behavior is based on rerendering the entire current vdom tree any time the user interacts with a DOM element or after a network request completes -- and the Mithril community only encourages optimizing beyond that if there is a specific performance issue. (You need to add your own redraw calls in callbacks for timeouts and a few other cases.) That said, I can understand how the herd mentality shapes the employment landscape for both programmers and their managers. It does in my own work life too -- where I have spent a couple of years working in Angular for my day job despite knowing what a mess of accidental complexity it is compared to something like Mithril. Angular was chosen years ago by other developers before I joined the project -- developers who mostly did not stick around to suffer the maintenance consequences. At least new projects may be in something other than Angular -- typically React (which is at least better than Angular). It's saddening how many times in my career I've ended up having to work with worse technology because of herd effects -- despite knowing better alternatives existed and having personal experience with them. For example, IBM chose to promote Java instead of Smalltalk in the late 1990s (despite having two Smalltalks it owned). Or Netscape ultimately foisted a Java-ish looking JavaScript on the world when Brendan Eich was originally recruited with the promise he could write a Scheme for the browser. Although, as with both Java and JavaScript, after a couple of decades, most of the worst rough edges are worn smoother and many of the worst bugs are fixed, and so the developer experience for both by now is finally not that bad.
- dzonga 8y agoIt will pass React, when they're more Job posting about Vue more than React. The market determines the winner not GitHub stars. Even here on the HN WhoIsHiring threads, React is miles ahead of anything. brutal law of the market, Vue is pleasurable to use, but the market doesn't care what you think or care about.
- mrath 8y agoI see a lot more jobs on Angular(2+) and React in Australia. Hardly ever do I see Vue mentioned in jobs and I don't even hear people talking about it. Even while starting a new internal project, people are just comparing React vs Angular. But my exposure to frontend stack is limited so I could be wrong.
- wcr3 8y agohttps://github.com/stursby/hasvuepassedreactyet/blob/master/yarn.lock https://github.com/stursby/hasvuepassedreactyet/blob/master/... > 6778 lines (5726 sloc) 239 KB awwwwww yeahhhhhhhhhhh
- tylerjwilk00 8y agoCompetitive angle aside, Vue deserves all the stars it gets. It's a pleasure to work with and a much needed tool in the frontend landscape. The more mindshare it gets the better for everyone. I'll keep on rooting for it!
- megaman22 8y agoMaybe people could just stick with one frigging thing for more than 12 months? I'm sick to death of Javascript churn. Polish one thing up until it is actually done before chasing some shiny new half-baked thing like a cat with a laser pointer. A slightly different spin on MVC concepts from twenty or thirty years ago doesn't get me out of bed, much less rewriting my front-end code more often than I file my taxes.
- xkcd-sucks 8y agoJob security
- stevev 8y agoProgress
- Apocryphon 8y agoDoes this mean Nativescript will be on the rise?
- Jonovono 8y agoBoth are outdated. Cycle.js is the new framework. :)
- breinhart 8y agoI just starred it, and moved it across the finish line! I actually do like Vue.js more than react, so it wasn't just for the fame!
- fowkswe 8y agoI just starred Vue to make it even with React at 98,564
- overgard 8y agoI'm always baffled by web developers constantly moving to new frameworks and toolchains. I can't really think of other sectors of development that chase as many fads. I mean its one thing if it solves a significantly new problem, but a lot of times it comes down to like "so and so likes gulp better than grunt or sass better than less and they're going to stall the project for two weeks while they switch the codebase over while pretending they're fixing tech debt". In game development, where developers are frequently on the cutting edge of things, the idea of switching engines and apis all the time for marginal benefits would get you a lot of raised eyebrows, and im guessing desktop app developers and people into scientific computing feel likewise. Don't get me wrong things evolve, but code in those fields doesn't seem to be treated as disposably.
- acdha 8y agoIt does in the web world, too, but you don’t hear about it as much because nobody writes self-promotional posts about how they decided not to switch because it wasn’t worth it.
- bobbytherobot 8y agoI counter that perhaps it feels like people are switching all the because there are more people and projects in web development than games or scientific development. Most all games have websites, whereas, few websites have games.
- arvinsim 8y agoResume Driven Development. No one wants to be left behind because it would hurt your chances of getting a new job.
- scabbycakes 8y agoAs a business owner I'd be VERY interested in something (fad or not) that cuts development time and complexity by a substantial amount. As a developer I want to use things that make my life vastly easier and lets me focus on the product rather than the programming. Trying new things and taking risks can yield huge rewards! Of course it can fail spectacularly as well but for those that worry about that a lot, jQuery UI still exists!
- keyle 8y agoI use Vue at work every day. We build large applications in it and it's extremely pleasant to use. That said, I wouldn't use a number of stars in Github as more than an indicator of people pushing a star button in Github. I've starred many things so that I can remember them some day. If I use something every day it's most certainly not starred.
- dylanhassinger 8y agoI love Vue!
- 1298471924 8y agoPeople say that "you only have to learn a few things to know react" and that with Vue you need to learn this whole API and well that is just too much to learn! These people are of course just trying to find an argument to match their emotional investment in a product. It isn't a real argument and can be refuted with logic and maths. I started a node/express/vue project about 6 months ago. Here are the APIs and syntaxes and so on I had to learn: Mongoose API MongoDb API Express API HTML5 Validation and Validity API Fetch API Bootstrap 4 API Flexbox some new javascript concepts like destructuring Webpack/source maps/hot modules Node The differences between importing/exporting modules in node and the browser Oh yeah, and the Vue API. You know what percentage of learning the Vue API was? About 0.01%. What is even more ridiculous is that it wasn't even the learning of the API that took the most time. All of the concepts in Vue/React take more time to learn than the API of Vue. The differences between data and props, what reactivity is, how single page routing works, how components work, and so on. In fact, as React is so barebones, it probably requires more learning than Vue because you have to find all the other libraries to make it the full product.
- jaequery 8y agovue makes coding so much more enjoyable than reqct for me that im glad to see it get more traction
- manigandham 8y agoGithub stars are a rather meaningless proxy. Many people like have all the major libraries starred but actual usage is quite different. Vue is great, but React has about 10x more libraries, frameworks, components and just general "stuff" built around it, along with the mindshare that it brings.
- sdnguyen90 8y agoQuestion for Vue users: whats the value prop over React? I haven't had a chance to look at Vue in depth but it seems to me that its useful for building apps where you don't need a build tool which makes sense to me. The main thing I don't get is why use Vue over React if you're going to use single file components with some kind of build tool?
- tomwilson 8y agoTo me it comes down to if you like the style of using a template language for the render or not. Someone will inevitably say you can use JSX in Vue but if you do that I don’t see the point in picking Vue.
- Kihashi 8y ago> Question for Vue users: whats the value prop over React? I'll paste my comment from another post in this thread: >> I hear a lot that "Vue is easy to learn"... > That's why I started working with Vue. It seemed easier to approach for someone coming from a server-side language perspective (I'd mostly worked with Python/Flask and PHP/Symfony before). I could slowly ease into using pieces of it until I learned enough to write a whole project in Vue. You can probably do the same thing in React, but the Vue docs were written to address my use case.
- vikaskyadav 8y agoBecause vue is Chinese and China has huge population of developers! lol Haha
- cvakiitho 8y agohehe, my star passed it.
- elygre 8y agoI just starred Vue to give it 100,000 stars. I'm feeling irrationally happy about that.
- luord 8y agoI used to hate react, but being forced to work with it for a while has helped me get used to it. I still very much prever vue so this is great news to me.