3 ms·
I don't know how I feel or what I think about running mission control from a browser. Seems like it'd probably lead to lower defects to build something very si
by zeveb 8y ago
I don't know how I feel or what I think about running mission control from a browser. Seems like it'd probably lead to lower defects to build something very simple very close to the metal — and probably not at a prohibitive level of cost, either. The advantage would be cutting out the OS, the desktop environment, the fancy GPU software, the browser, the JavaScript interpreter, the JavaScript dependencies &c. from the critical path. The disadvantage of course would be running homegrown software which performs some (but not all!) of those functions.
Maybe I'm wrong, though. I'm certainly open to being persuaded.
- rcv 8y agoI made the transition from writing native QT applications in C++ to javascript front ends (generally React) a few years ago. In my experience, writing robust front-end applications was much harder in C++ than it is in javascript. The memory management in QT can get pretty complicated for large applications, and a single mistake can get you a segfault crash. Not to mention that it's much easier to hot-patch a javascript file on the server and then ask everyone to please hit CTRL-R on their browsers than it is to recompile and redistribute a binary to all my clients. At this point, all of the UI components at my company are js based and I couldn't be happier.