Re:Introducing Atom-IDE
by anderspitman on Tuesday September 12, 2017 @03:47PM
(#15231526)
You could do X forwarding
[ Parent
| on HN ]
Electron apps are terrible with X forwarding. Even locally, on your own LAN.
It's all rendered bitmaps getting sent over, causing much lag and terrible performance.
Not recommended.
Surprising, considering it's origin from web tech.
Re:Introducing Atom-IDE
by oneweekwonder on Wednesday September 13, 2017 @01:40AM
(#15235839)
> Surprising
Or not, your forcing rendered html/dom over the x window protocol. What web tech is in this stack? Only your rendered app on a gtk/qt/wtk(not sure what atom is using, etc) window. Nothing on the network side.
Re:Introducing Atom-IDE
by oneweekwonder on Wednesday September 13, 2017 @09:35AM
(#15238058)
mmm I wanted to edit my post but it seems to get locked after time. So just adding a comment with some info and corrections on the topic.
- Atom on linux uses GTK+[0].
- GTK+ uses XLib[1].
- From the wikipedia link "Xlib makes the client synchronous with respect to replies and events." so much for js being async ;)
- Do anybody know how workable chrome or even firefox is over the x window protocol?
[0]: https://electron.atom.io/docs/development/build-instructions...
[1]: https://en.wikipedia.org/wiki/X_Window_System_core_protocol#...