Reduced input in the latency stack?
Announcement
Collapse
No announcement yet.
Chrome OS Switches To "Freon" Graphics Stack To Replace X11
Collapse
X
-
I honestly suspect things that have been done for past few years will keep happening: HTML(5)+CSS for defining presentation, native code for application logic so heavy routines can be implemented in efficient fashion and JS for binding presentation and application logic together
Comment
-
HTML5 as a base for apps? it's a "no" for me.
Java, Python, Ruby, C# - it's a "no" for me again.
I do nto want any heavy browser engines, any scripts, any garbage collectors on computers and mobile devices as a base for apps. That's primarily why Windows Phone, Android or FirefoxOS suck - they use havy stacks for developers, because they are simply too lazy to learn C++, Swift or something "closer" to the metal.
And believe me - modern C++ is a modern, high-level, partially declarative language. You just need to learn something beyond classes and pointers.
Comment
-
Originally posted by Pepec9124Why not fork Weston ? It's light as hell, eats almost no CPU. Loads in max 2s.
Comment
-
Originally posted by giucam View PostThere'd be no point, Weston is a display server, and they don't need one. They have only one app running, the browser, and that can run directly sitting on the drm layer.
Comment
-
Originally posted by scionicspectre View PostHonestly, I've been hoping people could ditch GTK and Qt for a few years now in favor of HTML5 frontends. I know that's a crazy idea, but in the near future it may make a lot more sense than what we've been doing.
Style in GTK are declared in a CSS dialect.
Firefox is a incoherent mess with no native-look-and-feel and where every app looks alien. It has no consistency.
Application user interfaces in HTML should be easier to do right now with CSS flexbox (which is like of like hgroup and vgroup in GTK).
Comment
Comment