@Hunterrules0_o @hanser @nblr Bottom line is: FOSS...

All posts ~n's posts Post Back to profile

Bottom line is: FOSS has to do it's glyp rendering on CPU and either transfer the whole rendered text for each content change (more resource efficient) or has to upload humongous font atlases – good look if you want to render logographic script. So that's inducing a bottleneck.

The lesson here is: The graphics related resource constraints of 40 years ago never went away. They just bode their time, and now are rearing their ugly heads again.

Like 19 June at 19:41 | Wall-to-wall | Open on chaos.social

2 comments

datenwolf

@Hunterrules0_o @hanser @nblr

So in conclusion: Of course a graphics system developed with the constraints in mind (because it wouldn't have worked otherwise) will perform a lot better on modern systems, than graphics systems designed toward the needs of 15 years ago.

/fin

19 June at 19:43 | Open on chaos.social

Hunterrules

@datenwolf @hanser @nblr and is still more stable than modern wayland. in fact when wayland crashes it takes all your programs down with it, The devolpers who designed wayland cant do what x did 20 years ago.

19 June at 22:13 | Open on techhub.social