3 ms·
I'd take the overhead of a client-server architecture over the overhead of rendering the whole UI in HTML (electron apps) any time. Also I think that the marsh
by captainmuon 10y ago
I'd take the overhead of a client-server architecture over the overhead of rendering the whole UI in HTML (electron apps) any time.
Also I think that the marshalling you need for IPC is not so different than the boxing and conversion that you have under the hood if you write in an interpreted language, e.g. Python or JavaScript.
- hamstergene 10y agoSerialization alone is like, at least one order of magnitude slower than dynamic typing, and IPC has other os-specific overheads on top of that. Remote calls are so costly the whole architecture of a system has to be designed with them in mind.
- baldfat 10y agoI was 100% in your boat after experiencing Atom. I have a 8 year old re-purposed Linux box (OpenSUSE) for work. That took a LONG time to be okay with our Windows based IT Department. I changed my mind over two electron editors/IDE. I use RStudio and it is really been getting so fast on my old computer that I can't tell anymore. VS Code by Microsoft is so fast and nimble that I have been using it 75% of the time with no felt overhead. It really is an amazing piece of software in terms of speed, now the ram usage is still much higher but for my uses I don't notice it at all on my 8 year old Dell corporate computer.
- flukus 10y ago> I'd take the overhead of a client-server architecture over the overhead of rendering the whole UI in HTML (electron apps) any time. It's not an either/or problem though.