While 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.
[deleted]
Why we moved from Angular 2 to Vue.js and why we didn’t choose React
11–20 of 151 posts
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#12I've been attempting to learn Angular2 and React, but haven't delved into Vue. Angular2 is just different, but it makes more sense to me than 1 if you take the time to learn the concepts. If you go into 2 thinking your 1 skills will translate, then I get why you'd be frustrated. But I found 1 to be very vague conceptually, so many different ways to do the same thing that you end up with many bad implementations. And compared to React, Angular2 is cake imo. There's so much more materials to draw from, and ui libraries to use, and you have to import so much in order to do the same things in React. That may allow for more flexibility, but it makes the learning curve that much more difficult. I'm still not a fan of Typescript, but it seems important to get familiar with ES6.
Also angular-cli and create-react-app are both excellent tools that take a lot of the guess work out of the process, at the very least they show you how to do things right way and keep up to date with what's important.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#13While 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.
Not almost, it is exhausting to keep up [0].
[0] https://medium.com/@ericclemmons/javascript-fatigue-48d4011b...
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#142 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
Angular 2 kinda sucks. Simple oversights like not having a way to change focus on input fields leads me to believe it's run by crazy purists.
There's many other mistakes, like not having access to component state for custom validators and the infamous change detection errors. Sometimes the error messages border on horrific, reminds me of debugging assembly. Some of these issues don't have any good solutions.
The needless complexity is true. Like every bad framework it makes easy things difficult while at the same time piling on "magic" that's often not useful.
The author is dead wrong on Typescript. Typescript is the best tool I've added to my web development stack in years. Shortly followed by tslint. Once you get used to it the type inference is so good that you only need to even specify the type maybe 1/5 the time.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#15"We invested in a beta product and then shock horror - it changes before it's released. Let's blame the framework on that poor choice."
"We were unable to learn how to use TypeScript properly, so let's abandon gradual typing and suffer a net loss in productivity over the longer term."
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#16everybody who feels so strongly about separation of code from templates - do you realize that down there it's still just bunch of string concat calls? it's literally what ERB templates in Ruby compile to, and similarly in literally every other template language.
rather than focusing on "omg html in my js" you should focus on "omg presentation code in my business logic code" because that's when you realize where the real boundary is.
it's one of the reasons i love clojurescript's hiccup so much - i'm still clearly writing idiomatic clojure code but now the boundary is not some arbitrary "this file is named .html and this .js", but actual namespaces/functions, where it's obvious from scope and signature what data my templates depend on.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#17It's always a bit strange when someone chooses a framework based on how far they get in a few hours or days of testing. For medium sized or larger projects it's much more interesting how it will work long term with a large code base.
I'm not saying that Vue is no good or that it was not a good choice for the author, but the way he described their process makes me think that they optimized the wrong thing.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#18Earlier quoted context omitted.
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 overanalyzin…
> I bet there are a few people who'd like us to ditch that whole binary kerfuffle, too.
https://en.wikipedia.org/wiki/Setun
Knuth has also hypothesized that we may one day start producing ternary computers again due to their efficiency and elegance.
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#19Vue seems to be less taxing on the mind. Compared to React, I feel Vue is more easy to build with.
Just my 2 Cents
Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React
#20> 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…
> It should take no more than 20 minutes to learn JSX.
it should, but in practicality, for most front-end devs especially junior ones, it's not. Moving Angular 1 devs to Vue gets actual work going 3-4 times (anecdotal experience) quicker than with React. For most smaller shops/startups Vue is almost always a better idea - it's much easier finding devs (especially remote/<100k comp ones) with previous Angular 1 experience and the learning curve is alot nicer. React is overengineering for most web apps.