5 ms·

And instead we have a 1 bloated codebase that is slow on 3 platforms and doesn't provide native features? The fascination with 1 codebase doing multiple things

• fastball 8y ago
  You're acting as if React makes it impossible to do anything else. As needs to be iterated every time we have one of these threads: you're still free to do it the "old way" -- writing your backend in X lang, your iPhone app in Swift, your Desktop apps in C++, your Android app in Java, and your web frontend in HTML/SASS/JS/jQuery. Nobody is stopping you. The truth is that people want their apps on multiple devices these days, and many apps wouldn't exist without react, at least not a port for your platform of choice. Yes, React sacrifices convenience for performance, but that has always been a trade-off. You'll notice very few people writing apps in C these days. That being said: What native features are you lacking? What apps are you using that are noticeably slower than native alternatives? My main complaint with React Native is the memory usage, but that is getting better and better and my computer has tons of RAM these days.
  • mosdl 8y ago
    React (or vdom in general) has high memory costs and won't be close to native performance anytime soon (or ever). As long as you are cognizant about the trade offs it can be the right choice, but never blind. People forget the old applet days.
• Scooty 8y ago
  > The fascination with 1 codebase doing multiple things is funny. Isn't it baked into most programmer's best-practices? Don't repeat yourself? Writing two programs that do the same thing doesn't sound very DRY.
  • mosdl 8y ago
    Each solution has pros and cons, and engineering is really about making those choices and dealing with the repercussions.