4 ms·
Electron solves nothing, it's a prime example of the Inner Platform[0], it will go through all the growing pains of solving the "library cruft" inside it, and w
by contras1970 9y ago
Electron solves nothing, it's a prime example of the Inner Platform[0], it will go through all the growing pains of solving the "library cruft" inside it, and will still require all the "cruft" below it.
BTW, you say you think electron is a step in the right direction, and follow it with "I am not saying [...] it is even a good idea." it can't be a step in the right direction and a bad idea at once, so which is it? is it a good idea or not?
[0] https://en.wikipedia.org/wiki/Inner-platform_effect https://en.wikipedia.org/wiki/Inner-platform_effect
- sddfd 9y ago> right direction, vs not even a good idea I think it is a step in the right direction because it allows you to build platform independent software today, with a relatively defined interface to the system (dom + JavaScript). This is a great opportunity to gain experience about the requirements for systems like electron. So I think it is good that electron exists, and would like to see it improved to address the issues that are discovered by using it. On the other hand, I am not sure if developing application software in JavaScript is a good idea. I am not sure if compiling to webassembly just to have it execute in another virtual machine is a much better idea. I don't know if the dom abstraction is a good idea in the long run (it seems to work for the web though). And I am not sure if there is another less popular technology around that should be used instead electron.