Linked by Kroc Camen on Thu 20th Aug 2009 09:43 UTC
Podcasts What else would we talk about other than the massively [popular|controversial] article about X.org last week. We try and address a number of concerns about the article and common lines of reasoning / misunderstanding. Lastly, we move onto something completely different with topics on Google Chrome on Linux, IE6 and the two details we know about RockMelt: Rock. Melt.
Thread beginning with comment 379791
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Ha
by somebody on Thu 20th Aug 2009 21:18 UTC in reply to "RE: Ha"
somebody
Member since:
2005-07-07

Since original article was complete bull... that is probably sanest option.

Thom was more or less bullshiting about his unstable hardware, not X. Any even a little technical person will conclude the same on every OS when user has complaints like that. I would even go as far as to bet that he uses proprietary NVidia driver and then blames free software.

About restoring the state on crash? THERE SHOULDN'T BE CRASH AT ALL... EVER... and in that case... who cares about restore (I don't... for 5 years not even one X/kernel crash for me).

About Thom...
He is more than occasionaly quite interesting to read... If you exclude times when he starts thinking he is a technical person (it would be time for him to finally decide on which pill he will swallow, if only he will realize the truth after... HE IS NOT TECHNICAL PERSON).

Reply Parent Bookmark Score: 4

RE[3]: Ha
by sbergman27 on Thu 20th Aug 2009 22:17 in reply to "RE[2]: Ha"
sbergman27 Member since:
2005-07-24

Since original article was complete bull... that is probably sanest option.

Strongly agree. And exactly what I'm doing. Pointless editorial begets pointless podcast. Pointless film at 11.

Edited 2009-08-20 22:17 UTC

Reply Parent Bookmark Score: 2

RE[4]: Ha
by Thom_Holwerda on Thu 20th Aug 2009 22:52 in reply to "RE[3]: Ha"
Thom_Holwerda Member since:
2005-06-29

So, the original article as bullshit? so, the answers to the following two questions are "no" in your world?

Does X, or does it not, take down all the application an data within them when it crashes?

Does X, or does it not, crash when a video driver misbehaves?

If you answer these questions with "yes", then you agree with the original article. If not, then you are using a special version of X that is better than what the rest of the world is using.

Reply Parent Bookmark Score: 2

RE[3]: Ha
by pdunning on Fri 21st Aug 2009 14:11 in reply to "RE[2]: Ha"
pdunning Member since:
2009-06-11

In my experience nVidia is the only card that has never given me problems beyond trying to find the driver. my intel open source driven card has problems and I hear ATI is worse.

Arguing that handling crashes is unneeded as there shouldn't be any is like saying we do not need a fire service because houses should not burn down.

There are problems with the current graphical stack, even when using only open source software. The important question is how do we improve it.

Reply Parent Bookmark Score: 2

RE[4]: Ha
by somebody on Sun 23rd Aug 2009 12:27 in reply to "RE[3]: Ha"
somebody Member since:
2005-07-07

In my experience nVidia is the only card that has never given me problems beyond trying to find the driver. my intel open source driven card has problems and I hear ATI is worse.

Arguing that handling crashes is unneeded as there shouldn't be any is like saying we do not need a fire service because houses should not burn down.

There are problems with the current graphical stack, even when using only open source software. The important question is how do we improve it.


I wasn't arguing that handling crashes is not needed. I was arguing that X is the wrong place for that. X provides very good framework for that already, shame... almost no software uses it.

Ati drivers are still in development while Intel... those drivers are going trough a lot of changes just to provide exactly what you are asking for.

If only people would read plans...

Reply Parent Bookmark Score: 2