Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An experienced Javascript developer’s account of learning React

medium.com

Post reply on HN
Print view View original

151–157 of 157 posts

Re: An experienced Javascript developer’s account of learning React

#151

Post by balfirevic »

jaequery wrote: post #124

im going to just say whats on my chest. it makes me wonder if react devs who thinks react is the greatest thing since sliced bread are somewhat new to web development (less than 2-3 years or so). because im sure those who inherently know, would find that vuejs is just a superior framework (sans native). there will always be new frameworks that comes out and some will be better than the last. and vue to me is leading…

It would probably help if you provided any kind of actual argument for vue.js being so superior other than the head shaking and vague claims about react not having "patterns" and "elegance".

For the record, I have been in web development for as long as you are, so that alone does not seem sufficient to immediately see the of superiority of vue.js over everything else.

Re: An experienced Javascript developer’s account of learning React

#152

Post by Achshar »

tps5 wrote: post #114
Achshar wrote: post #34

Earlier quoted context omitted.

I have written relatively large (35k lines) project in pure JavaScript (without even jquery) and have never faced any of the issues mentioned by the parent, (Babel helped). I write native first and then run babel to appease my older browser faring users. The advantages of native are that it's extremely snappy to use and fast to load. Bears smaller memory footprint (have to use angular.js at work and god it's awful) a…

I have no idea what "native" means in this context, care to elaborate?

I beg your pardon, poor choice of words, native here means plain js. Nothing more.

Re: An experienced Javascript developer’s account of learning React

#154

Post by bigato »

danabramov wrote: post #153

I wrote a reply to address some of these points: https://medium.com/@dan_abramov/hey-thanks-for-feedback-bf95... Thanks for sharing!

I'd love to hear your reply to this:

"what do you expect from a framework with more than 1000 issues on github that will let you install alpha dependencies by default (React@16.0.0-alpha.6) to develop your native app?!?"

Re: An experienced Javascript developer’s account of learning React

#155

Post by danabramov »

bigato wrote: post #154
danabramov wrote: post #153

I wrote a reply to address some of these points: https://medium.com/@dan_abramov/hey-thanks-for-feedback-bf95... Thanks for sharing!

I'd love to hear your reply to this: "what do you expect from a framework with more than 1000 issues on github that will let you install alpha dependencies by default (React@16.0.0-alpha.6) to develop your native app?!?"

Thanks, I missed this one! I added a paragraph:

>The version of the the react package is generally not relevant because it contains very little code (Component and createElement). The reconciler code is synced to React Native separately. So this an artifact of the different release cycles of RN and React, and doesn’t at all mean that RN apps are using an unstable version of React.

Re: An experienced Javascript developer’s account of learning React

#156

Post by johnydays »

virmundi wrote: post #117
ckorhonen wrote: post #85

Switching to React definitely has a learning curve, especially if you are coming from old-stool JavaScript or just not used to some of the concepts in React or Redux themselves. That said, once you get your head around it things start falling into place. We're recently built a React Native app and I feel the benefits it brings to cross-platform development make that ramp-up worthwhile. A single iOS and Android codeba…

How much of your code is OS focused? When I tried other approaches such as Ionic, the views started to be come heavily OS focused. Do you just forgo the native appearance?

React native renders native views using native code, so you don't really have to forgo the native appearance

Re: An experienced Javascript developer’s account of learning React

#157

Post by darth_mastah »

chrisco255 wrote: post #100
darth_mastah wrote: post #84

I agree. React is a great rendering library which somehow became the core of a mix and match framework, plagued by backwards incompatibility and maintained by plethora of individuals. As a result upgrading dependencies is never safe and and each of tens of them is quite likely to introduce breaking changes or become obsolete, leaving you having to make unnecessary changes in your app. Don't get me wrong, I think Reac…

There are like 13 exposed functions in React: render, componentDidUpdate, componentWillUpdate...It's as simple as it gets. What breaking changes? The core API has changed little. And what they have changed is simple to adapt to. They've added stateless functions and switched to ES6 style classes and removed mixins.

I was talking about React ecosystem, rather than the library itself. The latter is solid, the former though... not so much.
Post reply on HN