4 ms·

I think electron is a step into the right direction. Let's assume for a moment there weren't the problem with JavaScript performance (because, for example, web

by sddfd 9y ago

I think electron is a step into the right direction. Let's assume for a moment there weren't the problem with JavaScript performance (because, for example, web assembly can replace it). Then electron is a platform everyone can build his applications on. And once that happens, operating systems are free to shed the library cruft. This is just one possible migration path, and I am not saying it's going to happen or that it is even a good idea. But if you have to write cross platform apps it seems, that this has clear advantages.

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.
Ezhik 9y ago
People were saying this about Java in the 90s

by sddfd 9y ago

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.

Ezhik 9y ago

People were saying this about Java in the 90s