Slashdot Mirror
Facebook Brings React Native To Native Mobile Development
the_insult_dog writes Despite a lack of dev tools, samples, tutorials, documentation or even a blog post or press release, Facebook's announcement that it's bringing the popular React.js JavaScript library to iOS and Android native mobile development stirred up comments like "groundbreaking" and "game changing." In a series of videos from the recent React.js Conference 2015, Facebook engineers said they're rejecting the "write-once, run-anywhere pipe dream" in favor of a "learn-once, write-anywhere" paradigm. All efforts to duplicate native performance and look-and-feel actually feel like "s__t", an engineer said in explaining the company's new approach to native development in a conference keynote video. Yet to be proven, with tools in the works, it's supposedly a huge success internally at Facebook and experts said the new approach could shake up the whole mobile dev industry.
Hype much? If your JavaScript isn't portable enough to run on a modern mobile browser than you suck. The fact that they can make something happen that is supposed to happen by default doesn't exactly excite me.
Better known as 318230.
Judging by the Facebook App. This react is a piece of shit. Just use Objective C or Swift and stop wasting everyones time.
Facebook engineers said they're rejecting the "write-once, run-anywhere pipe dream" in favor of a "learn-once, write-anywhere" paradigm
I'm sure that is Facebook's dream: an oversupply of software developers with the skills required for employment at Facebook.
I think you missed the point. The article is talking about running javascript without the browser layer (i.e, "native" on the OS) and getting better performance out of it. This has nothing to do with javascript browser compatibility.
If the code is written in JavaScript, and if "anywhere" involves a compiler, not just an interpreter, then the performance of the software should be nearly optimal anywhere. And, somewhere along the years, I got the impression that JavaScript compilers were becoming rather popular. I might be mistaken about that, but the notion should still be true, that if every platform included a JavaScript compiler, write-once/run-anywhere could work.
I'm still baffled at how piss-poor Facebook's apps are. I think it's less a "pipe dream" in general and more a "pipe dream" for them in particular. They need to stop pretending everyone else is at fault and smell the coffee - you guys suck, not the tools you're complaining about. Your fault if you gave up on them, if you couldn't get such a simple service working in a browser. Stop bolting on extra shit before you get your core app right, that's the lesson to take home here. If I can write a cross-platform, cross-browser, multi-resolution app UI which many actual workers don't complain about, you should be able to get your glorified yearbook-with-distractions working for people who just want a pretty UI instead of a functional one. Stop bitchin' already and do your jobs.
It's interesting technology (both react and react native). But the javascript ecosystem and tooling is a bag of shit. People put up with it on the web because you don't have a choice. The only reasonable explanation for node.js to exist is that some people are too stupid to learn php. javascript on the server or desktop or pocket is a massive step backwards. But this caters to people who are too stupid to understand that so I'm sure it will be wild success. Sometimes I think intel is bankrolling the javascript hype to sell faster processors to compensate for slower and dumber code. I also wonder if wonder if wearing skinny jeans causes mind-numbing crotch pain to the point that, relatively speaking, javascript is a pleasure to use.
Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
I used React.js, then I dropped it in favor of html, because after all, html is how you build UI in... ...html. Sure I use templates, I use client-side javascript view-model binding, but I found React.js over engineered and not worth using. To me it's always screamed "flavor of the month" against other, more mature javascript libraries like Backbone and Ember. But to each their own I guess.
There's already a ReactiveCocoa, I wonder how the Facebook framework differs? Apart from being able to be used cross platform that is...
The cross platform stuff I try off and on through the years, but it always leaves be cold compared to whatever tools exist specifically for each platform.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Search engine wise, it's innocent enough, to prove your account; I've yet to give it to any of them.
I read an article that said Facebook wanted into the mobile market, well here they are.
Block JavaScript from unwanted sources like Facebook I don't care what they do!
-The wise argue that there are few absolutes, the fool argues that there are no probabilities.
React isn't a standard, it's a GUI framework. They're proposing compatibility layers for other GUI frameworks on other platforms, with no intention of replacing those other frameworks. Of course it's possible, because other such compatibility frameworks are available and quite successful. What React offers that the others do not is that the development environment is familiar to web developers.
This article should be entitled "Will Facebook's Reactive Native shake up the whole mobile industry?". This story is in need of a textbook application of Betteridge's Law.