3 ms·
If some of these native toolkits had a decent track record of producing not-hideous and usable cross-platform apps, maybe we would. That devs with real cross p
by gedy 10y ago
If some of these native toolkits had a decent track record of producing not-hideous and usable cross-platform apps, maybe we would. That devs with real cross platform needs have been using solutions like Java Swing, Flash, Electron, etc since the 90s should be a pretty big hint.
- sho_hn 10y agoNo, in the real world you use Qt.
- kps 10y agoI may be misunderstanding the top-level comment, but xkbcommon is not a cross-platform toolkit — it's an implementation of keyboard layout, derived from X11 XKB, so it's in contrast to other system-level layout systems like those of Windows and OS X. (Personally, I think XKB is an over-complicated product of the second-system effect applied to X11 keymaps, and the NeXT/Apple approach is the least bad of the common ones.)
- gedy 10y agoThanks, yeah even more applicable in this case - Electron is not perfect, but hand-crafting Atom for every native platform and toolkit is not feasible.
- zeveb 10y ago> hand-crafting Atom for every native platform and toolkit is not feasible. Somehow both emacs and vim exist, and run on more platforms than Atom! It's not a bad thing that Atom exists, although I think it's sad that folks who care about extensibility and flexibility don't just hack on emacs. But I think that if they wanted to, they could support as many platforms as emacs and vim do.
- GuiA 10y ago...what? The poster linked to a library implementing a way to interface keyboard events with the Linux kernel input subsystem, to show how one might solve the problem the posted blog post attempts to solve from within a web browser when one is writing native code. You're talking about cross platform GUI development toolkits. The two things are just 2 completely and utterly different topics.