Why we moved from Angular 2 to Vue.js and why we didn’t choose React
1–10 of 151 posts
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#2While we are at it - any success stories with Weex? (a la Vue.js native)
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#3We moved from Angular 1.3 to Vue.js. Vue came at a right time and I especially liked its ease of use, similarity to Angular and footprint. The most important thing to me personally was the speed and the development feedback cycle.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#4While we are at it - any success stories with Weex? (a la Vue.js native)
A few months later: "Try Weact, a Weex alternative."
The speed at which these frameworks pop up is almost exhausting.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#5We moved from Angular 1.3 to Vue.js. Vue came at a right time and I especially liked its ease of use, similarity to Angular and footprint. The most important thing to me personally was the speed and the development feedback cycle.
I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#62 flaws with this article.
1) Using a Beta product and complaining on Angular2. You could have waited till the product is matured
2) Blaming for the developers inefficiency on Typescript. If your developers coding speed is reduced blame on your developers.
Your title and article appears that something is wrong with Angular2 and moved to Vue.js. Before you post such articles make sure what your write makes sense
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#72 flaws with this article. 1) Using a Beta product and complaining on Angular2. You could have waited till the product is matured 2) Blaming for the developers inefficiency on Typescript. If your developers coding speed is reduced blame on your developers. Your title and article appears that something is wrong with Angular2 and moved to Vue.js. Before you post such articles make sure what your write makes sense
He cites two articles going into much more detail on the line of thinking regarding the tradeoff that is static typing. I realize this is one of those tab/spaces kinds of religious debates, but hopefully all sides can acknowledge that we are talking tradeoffs and not universal truths. Maybe one day we'll see loose typing as evil as "goto" statements, but the evidence isn't there yet. IMO.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#8We moved from Angular 1.3 to Vue.js. Vue came at a right time and I especially liked its ease of use, similarity to Angular and footprint. The most important thing to me personally was the speed and the development feedback cycle.
I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.
I like it, a mirror opposite of extreme "designed by committee" practices of big co. funded frameworks.
I feel purposefulness of Vue's design. There are no gigatons of features and behaviors which make you scratch your head and think "why it is there to begin with" like why Ang2 insists on using observer objects for HTTP responses, or why Ang1 had a such an extensive buildover around its component zoo to do just "new mySerice", or reasons for React's component rendering order peculiarities, or logic behind their choice of syntax.
Vue is very bare bones thing. It provides no reactive layer over complex object with non-primitive content. Lack of native support for maps or sets from ES6 is inconvenient a bit, but it is not hard to provide a function wrapper around any logic that uses them. I usually keep all business logic outside of Vue's instance and only wire though its inputs and outputs.
What I lack in all common frameworks is the ability to play smoothly with really complex DOM manipulations, like swapping prototypes of a DOM elements and mergings. Trying to do something like complex drag and drop logic usually means doing a lot of "do it within DOM element, or do it within framework's element" thinking
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#9> With Typescript things that were really easy to do on Javascript like defining a simple object were more complicated to do on Typescript.
TypeScript in no way prohibits you from defining a plain old untyped object. Just don't assign a type to it, and it behaves just as it would in plain JS. I wouldn't use Angular 2/4 either, because of its needless complexity and over engineering — but not because of TypeScript. If anything, TypeScript is a bonus.
> React mixes both JSX/HTML with JS code which I just don’t like since I strongly believe in separation of concerns and it looks ugly IMHO.
This is valid only if you think separation of concerns is the same as separation of technologies. I don't think so. It makes more sense to group code based on function.
In fact Vue.js allows single file components that mix HTML, CSS and JS in a way that would violate the author's definition of separation of concern. From Vue.js' documentation: "One important thing to note is that separation of concerns is not equal to separation of file types." [1]
> Coding speed was an area Vue.js won by far, not having to learn JSX was of huge help.
It should take no more than 20 minutes to learn JSX.
1. https://vuejs.org/v2/guide/single-file-components.html#What-...
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#102 flaws with this article. 1) Using a Beta product and complaining on Angular2. You could have waited till the product is matured 2) Blaming for the developers inefficiency on Typescript. If your developers coding speed is reduced blame on your developers. Your title and article appears that something is wrong with Angular2 and moved to Vue.js. Before you post such articles make sure what your write makes sense
He cites two articles going into much more detail on the line of thinking regarding the tradeoff that is static typing. I realize this is one of those tab/spaces kinds of religious debates, but hopefully all sides can acknowledge that we are talking tradeoffs and not universal truths. Maybe one day we'll see loose typing as evil as "goto" statements, but the evidence isn't there yet. IMO.
Goto statements still have their fans, and on the other end of the spectrum you'll find people arguing that things like multiple return statements and exceptions are basically the same. It's hard to find absolute truths in computing. I bet there are a few people who'd like us to ditch that whole binary kerfuffle, too.
But yeah, they're trying to be productive in the short term, so it's probably not worth overanalyzing whether a distaste of static typing isn't emblematic of other issues. Getting things rolling has a higher priority...