<div id="readability-page-1" class="page"><div>
<section data-height="100" data-opacity="0.3">

<header>
<p><a href="https://jaigouk.com/"><img src="https://files.jaigouk.com/2018/08/jaigouk-blog-logo.png" alt="Jaigouk.Kim"></a>
</p>
<nav>
<ul>
<li>
<a href="https://jaigouk.com/">Home</a>
</li>
<li>
<a href="https://jaigouk.com/about/">About</a>
</li>
<li>
<a href="https://jaigouk.com/tag/posts-tag/">Posts</a>
</li>
<li>
<a href="https://jaigouk.com/projects/">Projects</a>
</li>
<li>
<a href="https://jaigouk.com/contact/">Contact</a>
</li>
</ul>
<ul>
<li>
<span>
<svg>
<use xlink:href="/assets/svg/icons.svg?v=546e9e9eb5#menu"></use>
</svg>
</span>
</li>
</ul>
</nav>
</header>


</section>
<section>
<p>
Learn once, write anywhere
</p>
<h4 id="motivationtostickwithit">Motivation to stick with it</h4>
<p>I picked up ruby language in 2008 and I fell in love with it. The philosophy was "Programming languages must feel natural to programmers." instead of hammering my head to figure out how to write codes in proper way. And that sparked various open source projects. I see the similar thing is happening in JS community. Lots of mobile devs are suffering because of iOS / Angular. React Native is trying to tackle that problem.</p>
<blockquote>
It's worth noting that we're not chasing “write once, run anywhere.” Different platforms have different looks, feels, and capabilities, and as such, we should still be developing discrete apps for each platform, but the same set of engineers should be able to build applications for whatever platform they choose, without needing to learn a fundamentally different set of technologies for each. We call this approach “learn once, write anywhere.”
<cite>— Tom Occhino, "React Native: Bringing modern web techniques to mobile", Facebook Code Blog, (Mar. 26, 2015)</cite></blockquote>
<p>It's expanding beyond web and mobile. VR is the next thing they are working on now.</p>
<p><img src="https://cdn.jaigouk.com/2016/10/react-vr.png" alt="react-vr-tweet" loading="lazy"></p>
<h4 id="resources">Resources</h4>
<p><a href="http://reactjsprogram.com/">http://reactjsprogram.com/</a></p>
<p><a href="https://github.com/transistorsoft/react-native-background-fetch">https://github.com/transistorsoft/react-native-background-fetch</a></p>
<p>vr related - <a href="https://www.udacity.com/course/vr-developer-nanodegree--nd017">https://www.udacity.com/course/vr-developer-nanodegree--nd017</a></p>

</section>

<div>
<p><a href="/author/jaigouk/">
<img src="https://www.gravatar.com/avatar/dfa5114caa61dd2b010e998cff905d73?s=250&amp;d=mm&amp;r=x" alt="Jaigouk KIm">
</a></p>
</div>


</div></div>

Jaigouk.Kim

Motivation to stick with it
I picked up ruby language in 2008 and I fell in love with it. The philosophy was "Programming languages must feel natural to programmers." instead of hammering my head to figure out how to write codes in proper way. And that sparked various open source projects. I see the similar thing is happening in JS community. Lots of mobile devs are suffering because of iOS / Angular. React Native is trying to tackle that problem.
— Tom Occhino, "React Native: Bringing modern web techniques to mobile", Facebook Code Blog, (Mar. 26, 2015)
It's expanding beyond web and mobile. VR is the next thing they are working on now.
Resources
http://reactjsprogram.com/
https://github.com/transistorsoft/react-native-background-fetch
vr related - https://www.udacity.com/course/vr-developer-nanodegree--nd017

reactjs

댓글