I'm under the impression, in Udacity's case especially, that part of the problem stems from asking native engineers to use a language and ecosystem that they're not used to working with, and then trying to get them to integrate RN code into an established, brownfield native codebase.
As a sole dev in a 3-person startup, I’ve managed to build a pretty large app with React Native, having zero prior native experience (although, that’s not to say that I haven’t had to learn a _lot_ about Xcode!)
Check out the landing page at https://vue-native.io/ at the bottom, "Compiles to React Native". It's important to note that "Vue Native" isn't officially endorsed by Vue.js.
Training budget for confs/courses/books is a big one for me, it shows that a company is invested in you and helping you further your career.
Another one is relaxed working hours and having a culture of trust with regards to when you're actually in the office. It shouldn't be a big deal if I need to leave early one day, or if I decide to do reduced hours but work flat out during the time I'm in the office, as long as the work gets done - who cares when?
I really disagree that it's a "waste of developer time" to use React for projects like this.
`npm install next react react-dom` takes an insignificant amount of time and gives you an extremely efficient developer experience immediately, with automatic code splitting, server side rendering and great modern CSS support. Compared to the amount of time I've spent over the years fiddling with gulp/grunt configuration files for "static websites", it's a no brainer for developers who are already productive in React.
React Native. Write the React we all know and love, be supported by a huge ecosystem and community, and leverage the power of OS level UI components and libraries whilst enjoying the ease of writing in JS. It’s making the production of a truly native-feel app completely painless and with little learning curve for an existing React/JS developer
I've been using Vue.js on large scale projects for a while, but for a greenfield project I'm choosing React instead. React has better support for SSR which is still really important for public facing websites, JSX feels much more natural to me than the v-* directives, not to mention React's incredibly large ecosystem. That being said, I really like the way Vue handles CSS in single file components, and the simplicity of Vuex compared to Redux. I'm still struggling to find a styling solution for React that I'm completely happy with. As with everything, it's about choosing the right tool for the job.
Allows you to create custom MacOS menubar items from the text output of any script.