141–145 of 145 posts
Earlier quoted context omitted.
> Nvidia users are shitty consumers and I don’t even want them in my userbase. Good Lord. I get that the EGLStream vs GBM thing is controversial, but this is childish. How are you supposed to discuss anything with someone who thinks like this.
Not an isolated incident. I had this exchange with him: https://news.ycombinator.com/item?id=15511570
Earlier quoted context omitted.
Not an isolated incident. I had this exchange with him: https://news.ycombinator.com/item?id=15511570
How is your exchange indicative of a behavioral trend? I find no fault with his words or tone in that thread...
Knowing that, some people are going to appreciate eg If you can't set an environment variable then power user tools probably are not for you while other people are going to be needled about it.
Earlier quoted context omitted.
Yep, utterly backwards. That kind of thing should be purely in driver space where it belongs, hooked on a driver model and not a kernel upstream model. It's funny that Microsoft learned this problem and fixed it back in 2007-ish. Well, in another 30 years Linux will catch up. Maybe.
MS didn't fix it. They simply froze their abstraction and everyone expects it to be the same. Linux supports kernel modularity for a long time already. The only difference - they don't guarantee interfaces to be set in stone. So clearly they aren't interested in "catching up", since they do it on purpose. I don't necessary agree that it works for their goals (preventing messed up un-upstreamable kernel modules), but…
Linux can't lose the GPU without taking the entire system or the program it's operating down. Windows can have the entire subsystem crash and come right back up almost instantly without loss of screen data, including active game windows.
Microsoft most certainly fixed their graphics problems that were rampant from NT4 through Vista.
Earlier quoted context omitted.
The Intel one has a known technique to disable the ME, the AMD one does not (for the moment).
However, disabling it is not trivial, needing to open your laptop and solding skills, also special equipment to read/write modified firmware.
Earlier quoted context omitted.
Yep, utterly backwards. That kind of thing should be purely in driver space where it belongs, hooked on a driver model and not a kernel upstream model. It's funny that Microsoft learned this problem and fixed it back in 2007-ish. Well, in another 30 years Linux will catch up. Maybe.
Meanwhile windows is able to restart the entire graphics subsystem with a new driver without losing apps. I doubt linux will ever reach these levels.