Live data from Hacker News

Why I moved from Angular to React

robinwieruch.de

11–20 of 107 posts

Re: Why I moved from Angular to React

#11

All these discussions miss the point to me: React can be run natively on Android and iOS. Can Angular? Vue? Elm? It seems like there can't be any real competition when starting a large class of new projects until the answer is "yes." So I'm asking: what are the best real alternatives that work natively on mobile?

React Native is just a renderer https://github.com/angular/react-native-renderer

Re: Why I moved from Angular to React

#12

All these discussions miss the point to me: React can be run natively on Android and iOS. Can Angular? Vue? Elm? It seems like there can't be any real competition when starting a large class of new projects until the answer is "yes." So I'm asking: what are the best real alternatives that work natively on mobile?

Well, there's https://weex-project.io/ which claims to be easy the "React for Vue" you're asking about. The only caveat is that you'd better be reading Chinese version of documentation with Google Translate, English one is basically one huge "to be done" placeholder.

Re: Why I moved from Angular to React

#13
Only some of these are percieved advantages over Angular. Alot of them are advantages over AngularJS, meaning AngularJS 1.x

I'm obviously biased, but using Angular (2+) with typescript and ngrx (observable based redux, essentialy) has been really nice to develop with.

Re: Why I moved from Angular to React

#14
I find it hard to switch away from React to another similar library/framework simply due to the community that surrounds the "React ecosystem". Having worked on applications using Angular and Vue, I've just had such an easier time solving my problems when using React because there just seem to be more man-hours sunk into developing best practices, which naturally leads to more mature libraries, frameworks, solutions, etc.

There are many things that the "React ecosystem" has taught me that I can apply to any future application I build regardless of the stack, but many of my problems were solved in little time because the SO answer to my questions also used React, or the answer came in the form of a React component I could plug in and not worry about.

Maybe when Vue's community is as thoroughly developed I'll try that out again. Right now it's hard to find a reason to switch.

Re: Why I moved from Angular to React

#15
Just a bug report: In the end of the article Mr. Rwieruch offers a free ebook to those that join his mailing list, unfortunately that does not happen.

You are instead sent (after confirming your email) to a site that lists the 'minimum price' of the book as free, gives you a price slider that cannot go bellow 14.99 (and the "additional information icon" when hovered, shows a minimum price of 14.99, contradicting the page's own previous claim)

A resolution that allows other users to aquire the free ebook is preferred, but removing the offer of a free ebook would also solve the problem.

Re: Why I moved from Angular to React

#16
post #13

Only some of these are percieved advantages over Angular. Alot of them are advantages over AngularJS, meaning AngularJS 1.x I'm obviously biased, but using Angular (2+) with typescript and ngrx (observable based redux, essentialy) has been really nice to develop with.

Till you try to build a web c omponent or embed an agular2 app in an existent DOM (haha)

Re: Why I moved from Angular to React

#17
For me, the conceptual simplicity of React (and associated projects) makes it very easy to reason about code written with it. If you've worked on a larger Angular project, you know this is a huge win - keeping things simple there requires a disciplined developer with a good understanding of Angular (a rare combination.)

Re: Why I moved from Angular to React

#18

Just a bug report: In the end of the article Mr. Rwieruch offers a free ebook to those that join his mailing list, unfortunately that does not happen. You are instead sent (after confirming your email) to a site that lists the 'minimum price' of the book as free, gives you a price slider that cannot go bellow 14.99 (and the "additional information icon" when hovered, shows a minimum price of 14.99, contradicting the…

Hi josinalvo, can you try the page again? As a student, the eBook should be pay what you want. You are the first person who reports the issue unfortunately. Sorry for the inconveniences.

Re: Why I moved from Angular to React

#19
post #16
post #13

Only some of these are percieved advantages over Angular. Alot of them are advantages over AngularJS, meaning AngularJS 1.x I'm obviously biased, but using Angular (2+) with typescript and ngrx (observable based redux, essentialy) has been really nice to develop with.

Till you try to build a web c omponent or embed an agular2 app in an existent DOM (haha)

How are you going to embed an app in another app/DOM without using an iframe, and how is creating that iframe going to be any harder to accomplish depending on the technologies used inside of it?

I'm not sure what you mean about components...Angular is component based. Are you referring to native web components?

Re: Why I moved from Angular to React

#20
My experience with Angular has been very different. I never felt pain working with Angular. Most of the issues I saw, boiled down to bad code. And I think those issues would still be there irrespective of framework used.

I also don't get why two way binding is difficult to reason about. Can somebody please give me an example?

Post reply on HN