3 ms·
This is such a boring argument that both enforces gatekeeping, and lacks any idealism about the future of our industry. Perhaps CPU speed/memory is not quite t
by ramblerman 7y ago
This is such a boring argument that both enforces gatekeeping, and lacks any idealism about the future of our industry.
Perhaps CPU speed/memory is not quite there yet for Electron to be viable in most projects, but nobody is taking away your ability to fiddle bits. Why does it have to be one or the other?
A JS developer can get access to writing their first 'native' client. If it is too slow, perhaps she will investigate a more memory efficient way. Or perhaps its good enough for the current use case.
Some paradigms will be dead ends, but experimenting with higher level languages and libraries is what moves us forward.
It's equivalent to kicking and screaming in the late eighties that this 'Python' is not efficient and a waste of time.
- dgellow 7y agoI know it’s not your main point, but python wasn’t a thing until the nineties (released in 1991 if I trust Wikipedia) and would have been almost always not efficient and a waste of time and resources at that point in time given the state of hardware (also considering that python wouldn’t have been the optimized version that it is now)