I definitely agree with most of your points, however, a few need commenting on.
Second, cutting and pasting has never been a problem in the X environment with *any piece of software* but KDE 1 and 2.
I pretty much think that that guy had more in mind that just plain text cut-n-paste. For plain text, I agree, with X it's more convenient than most other OSs.
"Re: Authors Device drivers": That's funny...I can't find anything in my kernel source tree grepping for your name. What exactly was it that you wrote, again?
I'm sure there are several times as many device drivers never included into the standard kernel than ones that are. There are even many that are never released to the public, or only released in binary form (Just today I made a winmodem work with such a driver), for whatever reason you can think of.
"Re: Killing processes without windows": This is the most idiotic suggestion I've heard in some time. Not all apps have a window. What about xbindkeys? There's a damn good reason for this. What about programs (such as daemons on Windows) that just occasionally pop up a warning dialog? You going to kill them off as well?
Rather unreflected reply I think. Its obvious the original author does not want this for every process, but only those started by the WM. You do not start xbindkeys from the WM. What you do is "xterm -e xbindkeys". And Im sure youll agree that an xterm without a window is a pretty good candidate for a kill action.
> NASA's Hubble Space Telescope may have, for the
> first time, provided direct evidence for the
> existence of black holes by observing the
> disappearance of matter as it falls beyond
> the "event horizon."
I doubted this from the beginning, as Relativity Theory clearly predicts that external observers cannot watch anything fall beyond the event horizon. It's only in the time-frame of reference of the falling object that eventually it'll cross the event horizon. In the time-frame of reference of any external observer the object will need infinite time to reach the horizon. This is because object time goes slower and slower as the object dives deeper and deeper into the gravity field. This is associated with the object becoming shorter and shorter (Lorentz contraction). All as seen from an external observer of course.
Reading through the entire article, I finally found:
> Because of the gravitational stretching of
> light (an effect called redshift), the fragment
> disappeared from Hubble's view before it ever
> actually reached the event horizon. The
> pulsation of the blob - an effect caused by the
> black hole's intense gravity -- also shortened
> as it fell closer to the event horizon.
Which basically does not say that the object ("fragment") was observed to fall beyond the horizon, what it says is that is was observed to approach the horizon ! Note it also observed "shortened pulsation" which is a direct consequence of the time slowing down.
So again a headline that's plain wrong. I really wonder if the author knew that.
Re:A lovely summary of all that's wrong with X
on
X Windows Must Die!
·
· Score: 1
> There you go: the X windows disasater >... > Really, it's solid stuff.
You must be kidding. In his "paragraph size" footnote that guy openly explains that he hasn't understood the meaning of the words "server" and "client". You call that solid stuff ?
Slashdot Mirror
Could please anybody explain to me why some moderator would rate this "funny"? It's sad truth!
Let's face it: Every government on earth is more or less corrupt )*. The US' is one of the worse. They're good at hiding that fact, though.
)* "corrupt" refers to more than accepting bribes. For instance campaign sponsoring is just as bad.
I definitely agree with most of your points, however, a few need commenting on.
Second, cutting and pasting has never been a problem in the X environment with *any piece of software* but KDE 1 and 2.
I pretty much think that that guy had more in mind that just plain text cut-n-paste. For plain text, I agree, with X it's more convenient than most other OSs.
"Re: Authors Device drivers":
That's funny...I can't find anything in my kernel source tree grepping for your name. What exactly was it that you wrote, again?
I'm sure there are several times as many device drivers never included into the standard kernel than ones that are. There are even many that are never released to the public, or only released in binary form (Just today I made a winmodem work with such a driver), for whatever reason you can think of.
"Re: Killing processes without windows":
This is the most idiotic suggestion I've heard in some time. Not all apps have a window. What about xbindkeys? There's a damn good reason for this. What about programs (such as daemons on Windows) that just occasionally pop up a warning dialog? You going to kill them off as well?
Rather unreflected reply I think. Its obvious the original author does not want this for every process, but only those started by the WM. You do not start xbindkeys from the WM. What you do is "xterm -e xbindkeys". And Im sure youll agree that an xterm without a window is a pretty good candidate for a kill action.
Cheers Peter
> NASA's Hubble Space Telescope may have, for the
> first time, provided direct evidence for the
> existence of black holes by observing the
> disappearance of matter as it falls beyond
> the "event horizon."
I doubted this from the beginning, as Relativity Theory clearly predicts that external observers cannot watch anything fall beyond the event horizon. It's only in the time-frame of reference of the falling object that eventually it'll cross the event horizon. In the time-frame of reference of any external observer the object will need infinite time to reach the horizon. This is because object time goes slower and slower as the object dives deeper and deeper into the gravity field. This is associated with the object becoming shorter and shorter (Lorentz contraction). All as seen from an external observer of course.
Reading through the entire article, I finally found:
> Because of the gravitational stretching of
> light (an effect called redshift), the fragment
> disappeared from Hubble's view before it ever
> actually reached the event horizon. The
> pulsation of the blob - an effect caused by the
> black hole's intense gravity -- also shortened
> as it fell closer to the event horizon.
Which basically does not say that the object ("fragment") was observed to fall beyond the horizon, what it says is that is was observed to approach the horizon ! Note it also observed "shortened pulsation" which is a direct consequence of the time slowing down.
So again a headline that's plain wrong. I really wonder if the author knew that.
> There you go: the X windows disasater ...
>
> Really, it's solid stuff.
You must be kidding. In his "paragraph size" footnote that guy openly explains that he hasn't understood the meaning of the words "server" and "client". You call that solid stuff ?
Cheers Peter