Hacker News Reader

Comment by pcwalton | Hacker News Reader

Separate per-thread GL contexts, with texture sharing via EGLImageKHR on EGL, pixmaps on X11, and IOSurface on Mac.

WebGL and content display lists are proxied to a separate process for security (in the multiprocess branch).

I feel like an idiot after reading that, and I'm studying EE hoping for a career in firmware/low-level programming. Good luck to me :)

You shouldn't. They're specifically titled data structures and functions inherent to various specific (some to a given platform) compositors, display servers and graphics libraries. You memorize them as you go, but it's the ideas that are more important.

Wayland might be taking over from X11 on a widely used Linux desktop as early as 6 months from now (Fedora 23):

https://blogs.gnome.org/mclasen/2015/01/19/gnome-wayland-por...

Obviously X11 will not just disappear, but is targeting Servo at X11 at this early stage in it's development like writing a Python library targeting Python 2?

X11 won't be going away any time soon.

Also, the EGL backend should work just fine in Wayland.

Well, when I wrote this stuff for the first time a couple of years ago, NVIDIA's official position was "we have no plans to support Wayland". Even now I suspect X will be around for years.

I will be the first to cheer X's demise, as we've had so many problems with multithreading and X, but we have no choice right now.

Here's an overview from last year showing nvidia's wayland support under way:

https://www.phoronix.com/scan.php?page=news_item&px=mtgxmde

And it's working? All my experience with multiple threads on different contexts is crash, crash, bug bug bug. I'm surprised it's stable at all on any platform.

Reply on news.ycombinator.com