4 ms·
> as a non-native developer I think the implication is as much that developers who label themselves like you have as "non-native" or "JS" or "web" developers d
by mi100hael 10y ago
> as a non-native developer
I think the implication is as much that developers who label themselves like you have as "non-native" or "JS" or "web" developers don't have the perspective to make an informed decision on the matter.
Many of the rest of us know how to build React SPAs (and have been doing it long enough to have used Angular 1, Backbone, Sproutcore, ...) but "JS + Framework of the Week" is just one of the many tools we could turn to when building a UI. Many of us have also used cross-platform native libraries like QT or GTK, or platform-specific toolkits like Cocoa or .NET.
Basically, if the only tool you have is a hammer... it might be time to learn to use some new tools.
- jmagoon 10y agoAre you saying that building a web version and two (or five) native versions of an application is equivalent to building a single JS codebase and having it just run? It certainly sounds wonderful to learn new tools, but how does that stack up from the engineering (cost-benefit) side?