Originally posted by brent
View Post
Announcement
Collapse
No announcement yet.
Another Intel 4K + GNOME Optimization Yields 5% Faster Render Times, 10% Lower Power Use
Collapse
X
-
- Likes 3
-
Originally posted by AnAccount View Post
And yet, you obviously haven't been able to do it.
Comment
-
Originally posted by brent View Post
That's sarcasm for sure, but I do wonder how GNOME developers managed to make everything so slow and inefficient and why it took so long to find out. Maybe it's a good idea to browse through the shaders generated for mutter and look for more.
- Likes 3
Comment
-
Originally posted by 240Hz View Post
Are you dumb or just trolling? I never said DdV is the sole contributor to gnome, but without him its performance and usability would be pre alpha stage. What are other gnome devs going besides writing garbage for others to fix?
- Likes 5
Comment
-
Originally posted by AnAccount View Post
So, you are not only unable to read code, you are also unable to recollect what you wrote 5 minutes ago. You wrote "Without Daniel there would be no Gnome Shell or Mutter", which in fact implies that he is the only contributor that does anything that matters.
Comment
-
Originally posted by 240Hz View Post
The majority of Gnome devs do not use Linux or the Gnome desktop enviroment. Majority of them use macbooks. They dont care since they dont need to live with the consequences of bugs in software that they dont use
- Likes 5
Comment
-
Originally posted by 240Hz View Post
The majority of Gnome devs do not use Linux or the Gnome desktop enviroment. Majority of them use macbooks. They dont care since they dont need to live with the consequences of bugs in software that they dont use
they might have macbooks. But you know that the intermediate linux user is able to install linux on those machines
Last edited by CochainComplex; 26 June 2020, 02:45 PM.
- Likes 4
Comment
-
All these optimizations are issues that people who understand how programs run. People who have worked with asm more than 5 seconds and saw how even a few more routines in a loop bog their processors down would have kept that in mind and known not to fall in to these issues because of it. When you program willy nilly to a goal on machines with so much hardware that even your mistakes don't manifest easily, and also don't exactly understand how the code you wrote actually works on a low level leads to these situations. And as you see, there's been tons of them that piled up. Just not good coding. It's fixed now, so "no harm done" except, you know, years of it sucking for no reason except ineptitude.Last edited by abott; 26 June 2020, 03:49 PM.
- Likes 2
Comment
Comment