vue

I see you have never had to implement Promises in userland. :) setImmediate is one of the more popular polyfills in fact, all the workarounds you mentioned either have downsides or are ugly hacks. It's useful to anything that has a scheduler. Like Vue for example. Maybe someone should tell Evan You that it doesn't make sense to need setImmediate? https://github.com/vuejs/vue/blob/b111de486b1bdc747fe0f5795f... Check the download counts: https://www.npmjs.com/package/setimmediate https://www.npmjs.com/package/next-tick https://www.npmjs.com/package/set-immediate-shim https://www.npmjs.com/package/core-js#setimmediate

Evan, if you are reading, I would like to say that I also fell in love with Vue, but I am frustrated that my feature request ( https://github.com/vuejs/vue/issues/8106#issuecomment-385367... ) was a little too quickly shot down, without much discussion or understanding. I understand that not every proposal can be accepted, but I think that the merit of the change wasn't even considered. I specifically designed the change to change as little as possible, and have as much power as possible. I think that specifically in the case of Vue, this hurts more because of the philosophy highlighted in the article- to not stand in the way of experienced developers who know what they're doing. (Edit: oh no, please don't come with the downvote train. This is a real issue, when you have something that solves 99% of your problems but you can't get it to 1

The only thing that bothered me was that there wasn't a way to tell Vue to disable reactivity with a clear pattern: see https://github.com/vuejs/vue/issues/1988 So e.g. if you want to have a Leaflet map i.e. `this.map = L.map(...);`, Vue will automatically add reactivity to this property. Sometimes I had big problems with this behavior (or it was simply annoying), so I wrote vue-static based on ideas of the core developers: https://github.com/samuelantonioli/vue-static Now I can have big objects in the Vue component which don't get automatically tracked using the reactivity system. - - - A problem for many beginners: Another problem with the reactivity system is that sometimes you have a route like `/employees/:id` and edit an object. But on abort, you want to rollback. One thing you always have to do is to copy the object you want to edi

I can vouch for the author's points on the good parts of vue.js. We've built our single page application (SPA) web app with vue.js and are very pleased with the results -- https://checkoutclip.com. We were able overcome most of the stumbling blocks by looking up https://vuejs.org/v2/guide/, https://github.com/vuejs/vue/issues and https://forum.vuejs.org. For server side rendered (SSR) pages, we're using nuxt.js, which is working out great as well. E.g. SSR page: https://video.checkoutclip.com/-LDQ5TtL_yywYCgUNb6K I would recommend vue.js for anyone building their first SPA even if they don't have prior experience building one...it's easy to pick up.

> Here's a discussion on class syntax in Vue: https://github.com/vuejs/vue/issues/2371 This is the typical answer from the Vue team. I've had a number of (civilized) discussions with them on other issues and it always ends up with "you are holding it wrong" or "this is not an issue". I won't argue classes vs objects, both have pros and cons, but locking the issue when there is clearly a boilerplate problem with Vue is bit ridiculous.

Gladly. With the data interface you can reuse or generate part or all of a component definition. A class declaration can only contain methods. The data object contains much more information. You could say both are descriptions that will be used to build an object, but the Vue API data object will be interpreted arbitrarily by Vue's runtime while the class declaration will be interpreted by the JS runtime and will only expose methods. You could use decorators or put properties on the class's constructor, but that has to happen outside of the scope of the class declaration and negates any cleanliness advantage. You can also put those properties in the constructor but then they are only available after instantiation. Here's a discussion on class syntax in Vue: https://github.com/vuejs/vue/issues/2371 I think that there's a temptation for cla

https://github.com/vuejs/vue https://github.com/facebook/react

According to Google search traffic, React is 10x popular: 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/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 While commits to React are regular and come from a much wider base of contributors: https://github.com/facebook/react/graphs/contributors T

It's how `vue-template-compiler` works to transform a template into render functions. checkout here: https://github.com/vuejs/vue/blob/dev/packages/vue-template-... also checkout last 'state of Vue.js' on YT where the creator talks about it ;)