Comparing React to Angular is...
... you know... They are not aiming for the same niche. And they both are aiming for just a niche are of software development. That's why they won't impact neither the JavaScript world, nor the web world overall.
Facebook's React Native framework is hot. The question is, for how long? After all, while Facebook-born React is smoking, it wasn’t very long ago that Google-spawned AngularJS had the web world all a’flutter. Before that, it was Backbone, SproutCore, and a variety of other hot-until-not JavaScript frameworks. On the one hand …
This article seems like a mash up between something about react native (a thing that lets you write native apps with react) and a comparison of web frameworks. Are these 2 things related? Not really. Does react native deserve an article? probably not. There are other frameworks that do exactly the same thing, except without react. Its not new(s)
Without SALES people, none of you developers would have any stable jobs.
Complaining about the sales department is just so much "sour grapes". Rather than complain all the time, you should try it. It's not very easy to sell your shitty product!
"Complaining about the sales department is just so much "sour grapes""
Well there's a problem for starters, though not a complete surprise.
A salesperson who has no idea what "presentation layer people" means, and doesn't think to look it up before spouting off (hint: nothing to do with Powerpoint, not really related to 7 layer OSI model either).
I've worked with some fantastic sales folk in my time. The best ones tend to be the ones that know what they don't know, and therefore if in doubt seek advice before opening their mouths (and thereby removing any doubt about their cluelessness).
"Rather than complain all the time, you should try it. It's not very easy to sell your shitty product!"
Been there done that, but from a sales+profit point of view things work better when sales and tech are on the same wavelength, and when the product can do more than impress the PHB with its shininess. Maybe stuff that can actually do what it says on the tin.
Well, at least I now have heard about the MEAN stack: MongoDB, Express.js, AngularJS and Node.js. The mind boggles. What the fuck is that shit and how is it of any use to anybody?
Converting to the MEAN stack gives your development team a number of benefits, the three most significant being a single language from top to bottom, flexibility in deployment platform, and enhanced speed in data retrieval.
More like barely able coders falling over themselves, unable to get any meaningful work done while the applications blow up left and right.
Without SALES people, none of you developers would have any stable jobs.
Because all software is written to be sold, as any fule kno. Companies never develop software for internal use. No one in academia creates software. There's no free software.
As already mentioned, this article is weird. ReactJS doesn't compare directly to Angular (for obvious reasons, if you know a little about each of them) and ReactNative is even less comparable, as it's for building native apps with. Why is Angular even being mentioned here?
If you're going to put CSS in JS code - it's foo bar
If you're going to put HTML in JS code - it's foo bar
If you're going to make me write or call a render() method - it's foo bar
If you're going to make me write a "view" object it's foo bar
Yet another ill conceived re-invention of the wheel;
Just what are all these frameworks for, other than to consume bytes and processor cycles? Seems to me that mostly they are to facilitate incompetents to copy and paste code that they really don't understand in order to produce web sites and applications that really don't work very well. The briefest of visits to stackoverflow and its ilk confirms this to be so.
-A.
I've written apps with AngularJS and Meteor and React Native now. I was hesitant to go the RN route, but I thought I'd take a couple of days and try to do something.
After a few days, I dumped both AngularJS and Meteor - not because they aren't great solutions with an incredible ecosystem, but rather because I wanted to be as "native" as possible and RN provided that avenue.
Though RN JSX appeared to be an ugly red-headed stepchild at first, I soon realized it was a total mind shift on what makes a "component". I think Facebook has got this right. When I wrote Angular directives and such, if I stepped away from the code for a month or more I couldn't remember all the magic pony tricks it performed. Not so with React Native.
Having no experience with native mobile development, it's daunting to come up to speed on how to actually build an app that can be deployed to your device. It took me a long time and lots of searching to effectively do this. The result is a "starter app" that I've written called Snowflake which I'd like to share with your readers in case they, like I, want something more then a toy todo example yet again.
Snowflake, https://github.com/bartonhammond/snowflake, is an open source, free, React Native iOS/Android "starter app" which uses a single code base that runs on both platforms.
The application is tested using Jest, Facebooks official testing framework, and has over 86% code coverage. Snowflake demonstrates hot reloading and has a code walk through explaining those concepts. It also has Continuous Integration using Bitrise.io so that the final apps are built in the cloud.
Accompanying the CI code and docs are 7 videos of over 45+ minutes of instruction. The code is fully documented (http://bartonhammond.github.io/snowflake/snowflake.js.html)
If your readers have interested in React Native example they might want to look at Snowflake.
Thanks for the article, I believe RN will be hot for a long time...possibly contributing to global warming! ;) -barton
Being a mediocre javascript programmer. I found maintaining and tuning my React stack taking too much time. Having several projects in various lifecycle stages on the same server, I always have problems when node.js is being updated.
I then moved to meteor. For me I had to switch to mongoDB from Redis. I find it a bit slower, especially on grapic intensive apps when doing changes. But 'meteor update' has saved me much time and hazzle. and the meteor.is_server() and meteor.is_client() separation is easier for a javascript novice to understand :-)