Well, nothing prevents you to put reflective materials *under* the stealth layer.
If a missile is detected even though it has a "stealth layer", and a laser tries to destroy the missile, first the laser will burns the stealth layer, but then it will be reflected by the reflective layer.. Of course the reflective layer will be much less effective than the mirrors used in lasers for example.
But still, if the mirror reflects only 90% of the energy, you need a laser ten times more powerfull to destroy the missile than what is necessary to destroy a "normal" missile.
If you want to learn more about CPU architecture trade-off, the best book I know is "Computer Architecture: A Quantitative Approach" by Hennesy-Patterson.
I'm wondering how asynchronous logic stand up against transiant errors induced by a cosmic ray?
On a synchronous circuit most of the time such glitch won't do anything because it won't occur at the same time the clock "ring" so the incorrect transient value will be ignored.
As the "drawing size" of circuits gets lower and lower, every circuit must be hardened against radiations, not only circuits which must go on space or in planes..
I'm not saying that VNC is fast, I'm saying that you can have a very fast & responsive "single node" GUI as BeOS and implement on top of it a remote GUI layer as VNC does.
When you have a remote GUI, it won't be as responsive as a local app anyway, so why not add the burden there instead of paying it also for local application?
I'm not saying that the "remote GUI functionnality" should be optionnal: I use it everyday at work, I mean that it should be at the right place so that we could have fast local GUI and export display.
> X11 has great performance. Unfortunately, few toolkits use it well. It works best when you think of it as a stream: you send asynchronous requests to the display server and it handles them, responding with asynchronous events.
Asynchronous request are good for performance, but bad for responsiveness. A Berlin-like scheme where the server can show the pop-up etc should have better responsiveness.
> 99% of all apps don't require anything more fancy than 2D drawing primitives and a few icon pixmaps.
What's your point ? The idea is to be able to have real transparency, independency of resolution GUI not especially fancy effects.
As for Berlin not taking over the world: why are you using Linux? It is not currently taking over the world!
> client/server is fundamental to the design of both Unix and X11. Try this: administer your parent's Windows or Mac machine from your home 100 miles away, as though you were sitting right there. Can't do it?
AFAIK remote GUI can be done in Windows with VNC, so it shows that you can have fast,responsive local GUI and remote GUI at the same time. Just don't use X11.
We're talking about the same thing: "Proceed" or "Do an action".
You're right that in this case, there is an additional Cancel button, it helps desambiguate the two usage, but I think its better to use a different word.
Well, the case is not clear-cut, so the best thing to do is to respect the UI guidelines and do what it says.
I disagree: the way you talk depends on the medium: if there is a misunderstanding with another human due to ambiguous wording, you can talk with him and solve the confusion.
A button OK might means two things depending on the context: - an acknowledge (as is the case here) - Do an action
To prevent confusion, I prefer very much having two separate button for two different action: - Close button to acknowledge. - OK to do an action.
If you want to use OK, you must end the message with "Close window [OK]" which is more verbose than the simple "[Close]" button.
>Use strong typing (if your language doesn't >support it, fake it with explicit sanity checks, >boolean isSane()), always check inputs for sanity, >check your outputs are plausible at least,
Funnily in the first part what you described is Eiffel contracts programming, now who is using Eiffel here? Nobody! The worst part is I don't know of any other language which use so heavily assertionw, pre-conditions, post-conditions, etc..
> get good peer review on everything, KISS[]
I would also add: use unitary test and non-regression tests. And if you're manager make sure that everyone is testing properly their software.
Incredible as it seem many manager make their team skip the unit test part because "unit test are too costly"!!!
> Multiple inheritance has major problems (if both superclasses have the same function, which one do you use?).
Well, in well-defined language (Eiffel), this isn't a major problem: the developer have to solve by hand the conflict and that's all.
> >Pointers and direct memory access: > Ye gods. No. The moment you start doing this is the moment Java stops being cross platform.
Pointers and direct memory access are two different thing. Pointers in themselves can be used without preventing cross platform portability. As for direct memory access, it's true that it is against portability, so what? JNI are also non-portable but it doesn't mean that we should totally get rid of JNI.
As for the end, I agree: the lack of template in Java is quite annoying.
> The DJs with the MP3 players are acting more like > radio DJs- they're programming the night with a > list of songs, not cutting up raw material into a > performance.
It is a bit harsh, I think: a good DJ will adapt the songs played to the mood of the crowd whereas radio DJ only have a static list of songs to play.
It is the main componant of the human interface to drive a car, I expect the steering to stay long after we've switched to drive by wire, hydrogen power,etc..
It would be very hard to retrain people to use a joystick and think about the legal problems when there is the first accident..
I'm not a die-hard ecologist basically he says that it doesn't water if we switch to H2 cars today or in fifty years because eventually there won't be any oil left, so we'll have to make the switch anyway.
It's true of course, but he ignores a major point: the sooner we will get rid of oil, the less CO2 will be released in the air and the less hot the earth will be for our children.. NOT A DETAIL, I THINK!!!!
The thing is: it's true Microsoft bought some patents from SGI. But maybe not all SGI's patents were released in an open manner, or Microsoft may have some other patents.
As the shaders are a new feature for OpenGL, I'm not sure at all that SGI have already granted open access to its patents which cover this part..
Now OTOH, Microsoft know (I hope) that they need also OpenGL for professional app. (CAD,..).
And it's funny how Bush said that the US cannot afford to comply with Kyoto's restriction (limitation of CO2 rejects) while at the same time the US is one of the richest country.
At least, radioactive wastes will quite difficult to handle are on a solid state so they do not pollute everybody..
> Well, now that someone has provided the Sorenson > codec through emulation, people will realize > that it doesn't make much of a fucking > difference either way, does it? I guess that > means some people will have to find something > better to whine about...
The thing is: playing Quicktime movie alone doesn't make much a difference, but improving Linux's credibility on the desktop is a set of these "little" step: - playing "Quicktime" movies: partially done - interoperating with Microsoft Office: OpenOffice (even if the compatibility needs improvements) ...
I think that improving X or getting rid of X would be a major point to improve Linux's presence on the desktop, and also lots of polishing..
> While especially anisotropic filtering is > nice, it's not that big of a deal. The game > would look better, but not stunningly so, and > I'm not actually sure if you'd notice the higher > quality in the low res movies that are available > on the net.
But I noticed that the shadown had some annoying stair-step effect! I wonder if anistropic filtering would have corrected this (it depends how it's applied of course)..
Anyway, I was trying to analyse the way it looks, I suspect that when you're playing the game, you're much less sensitive to such details.
It really feels like a kludge: why attributes doesn't inherit the namespace of the element?
I think it's because of "backward compatibility", which is too bad, because it's obvious that they would need something like namespace to prevent clashes.
In France, Valentin Lacambre provided a free hosting website (altern.org).
Then a user put nude picture of a French topmodel Estelle Haliday. Her lawyer asked the picture to be removed, which was done (the account was closed). Nevertheless the lawyer made a lawsuit which found Valentin Lacambre guilty. To summarize, he would have to check everything posted on the thousand of website hosted, clearly it was impossible so he closed shop.
Slashdot Mirror
Well, nothing prevents you to put reflective materials *under* the stealth layer.
If a missile is detected even though it has a "stealth layer", and a laser tries to destroy the missile, first the laser will burns the stealth layer, but then it will be reflected by the reflective layer..
Of course the reflective layer will be much less effective than the mirrors used in lasers for example.
But still, if the mirror reflects only 90% of the energy, you need a laser ten times more powerfull to destroy the missile than what is necessary to destroy a "normal" missile.
If you want to learn more about CPU architecture trade-off, the best book I know is "Computer Architecture: A Quantitative Approach"
by Hennesy-Patterson.
A really good book, not too hard to read..
I'm wondering how asynchronous logic stand up against transiant errors induced by a cosmic ray?
On a synchronous circuit most of the time such glitch won't do anything because it won't occur at the same time the clock "ring" so the incorrect transient value will be ignored.
As the "drawing size" of circuits gets lower and lower, every circuit must be hardened against radiations, not only circuits which must go on space or in planes..
I'm not saying that VNC is fast, I'm saying that you can have a very fast & responsive "single node" GUI as BeOS and implement on top of it a remote GUI layer as VNC does.
When you have a remote GUI, it won't be as responsive as a local app anyway, so why not add the burden there instead of paying it also for local application?
I'm not saying that the "remote GUI functionnality" should be optionnal: I use it everyday at work, I mean that it should be at the right place so that we could have fast local GUI and export display.
> X11 has great performance. Unfortunately, few toolkits use it well. It works best when you think of it as a stream: you send asynchronous requests to the display server and it handles them, responding with asynchronous events.
Asynchronous request are good for performance, but bad for responsiveness.
A Berlin-like scheme where the server can show the pop-up etc should have better responsiveness.
> 99% of all apps don't require anything more fancy than 2D drawing primitives and a few icon pixmaps.
What's your point ?
The idea is to be able to have real transparency, independency of resolution GUI not especially fancy effects.
As for Berlin not taking over the world: why are you using Linux?
It is not currently taking over the world!
> client/server is fundamental to the design of both Unix and X11. Try this: administer your parent's Windows or Mac machine from your home 100 miles away, as though you were sitting right there. Can't do it?
AFAIK remote GUI can be done in Windows with VNC, so it shows that you can have fast,responsive local GUI and remote GUI at the same time.
Just don't use X11.
We're talking about the same thing: "Proceed" or "Do an action".
You're right that in this case, there is an additional Cancel button, it helps desambiguate the two usage, but I think its better to use a different word.
Well, the case is not clear-cut, so the best thing to do is to respect the UI guidelines and do what it says.
I disagree: the way you talk depends on the medium: if there is a misunderstanding with another human due to ambiguous wording, you can talk with him and solve the confusion.
A button OK might means two things depending on the context:
- an acknowledge (as is the case here)
- Do an action
To prevent confusion, I prefer very much having two separate button for two different action:
- Close button to acknowledge.
- OK to do an action.
If you want to use OK, you must end the message with "Close window [OK]" which is more verbose than the simple "[Close]" button.
Apparently Microsoft is lobbying specifically against the GPL license for products made with tax dollars.
BSD or LGPL would be fine as far as I'm concerned.
Let's not be GPL integrist.
>Use strong typing (if your language doesn't
>support it, fake it with explicit sanity checks,
>boolean isSane()), always check inputs for sanity,
>check your outputs are plausible at least,
Funnily in the first part what you described is Eiffel contracts programming, now who is using Eiffel here?
Nobody!
The worst part is I don't know of any other language which use so heavily assertionw, pre-conditions, post-conditions, etc..
> get good peer review on everything, KISS[]
I would also add: use unitary test and non-regression tests. And if you're manager make sure that everyone is testing properly their software.
Incredible as it seem many manager make their team skip the unit test part because "unit test are too costly"!!!
> The K&R C to ANSI C transition broke many of my programs
Uh? Many compilers had a switch which allows you to stay in compatibility mode in K&R.
-> No need to modify the programs.
As for the C++, there are some compatibility modes but I'm not surprise that you still had to make modifications: this language is really messy.
> Multiple inheritance has major problems (if both superclasses have the same function, which one do you use?).
Well, in well-defined language (Eiffel), this isn't a major problem: the developer have to solve by hand the conflict and that's all.
> >Pointers and direct memory access:
> Ye gods. No. The moment you start doing this is the moment Java stops being cross platform.
Pointers and direct memory access are two different thing.
Pointers in themselves can be used without preventing cross platform portability.
As for direct memory access, it's true that it is against portability, so what?
JNI are also non-portable but it doesn't mean that we should totally get rid of JNI.
As for the end, I agree: the lack of template in Java is quite annoying.
> The DJs with the MP3 players are acting more like
> radio DJs- they're programming the night with a
> list of songs, not cutting up raw material into a
> performance.
It is a bit harsh, I think: a good DJ will adapt the songs played to the mood of the crowd whereas radio DJ only have a static list of songs to play.
This happens under Solaris too.
I think that it is a bug so it should go into the 1.0.x release, but I'm not sure that there will be one.
I hope that it will be fixed in the 1.1 release..
I doubt that it can be doable easily.
It is the main componant of the human interface to drive a car, I expect the steering to stay long after we've switched to drive by wire, hydrogen power,etc..
It would be very hard to retrain people to use a joystick and think about the legal problems when there is the first accident..
I'm not a die-hard ecologist basically he says that it doesn't water if we switch to H2 cars today or in fifty years because eventually there won't be any oil left, so we'll have to make the switch anyway.
It's true of course, but he ignores a major point: the sooner we will get rid of oil, the less CO2 will be released in the air and the less hot the earth will be for our children..
NOT A DETAIL, I THINK!!!!
The thing is: it's true Microsoft bought some patents from SGI. .
But maybe not all SGI's patents were released in an open manner, or Microsoft may have some other patents
As the shaders are a new feature for OpenGL, I'm not sure at all that SGI have already granted open access to its patents which cover this part..
Now OTOH, Microsoft know (I hope) that they need also OpenGL for professional app. (CAD,..).
Hmm, saying that "a virus follows a strategy for its own survival" is a bit too anthropomorfic(sp?) for me.
I agree with LS here the definition of life is too fuzzy to judge if a virus is alive or not.
And it's funny how Bush said that the US cannot afford to comply with Kyoto's restriction (limitation of CO2 rejects) while at the same time the US is one of the richest country.
At least, radioactive wastes will quite difficult to handle are on a solid state so they do not pollute everybody..
Mmm, do you realise that a large part of Europe just changed their currency unit?
And no, it isn't easy: in my mind I still use the old one, but I hope that in 2 years or more, I'll get used.
As for being stubborn, which contry has refused to use meters as their standard unit for decades?
:-)
> Well, now that someone has provided the Sorenson
> codec through emulation, people will realize
> that it doesn't make much of a fucking
> difference either way, does it? I guess that
> means some people will have to find something
> better to whine about...
The thing is: playing Quicktime movie alone doesn't make much a difference, but improving Linux's credibility on the desktop is a set of these "little" step:
- playing "Quicktime" movies: partially done
- interoperating with Microsoft Office: OpenOffice (even if the compatibility needs improvements)
...
I think that improving X or getting rid of X would be a major point to improve Linux's presence on the desktop, and also lots of polishing..
> While especially anisotropic filtering is
> nice, it's not that big of a deal. The game
> would look better, but not stunningly so, and
> I'm not actually sure if you'd notice the higher
> quality in the low res movies that are available
> on the net.
But I noticed that the shadown had some annoying stair-step effect!
I wonder if anistropic filtering would have corrected this (it depends how it's applied of course)..
Anyway, I was trying to analyse the way it looks, I suspect that when you're playing the game, you're much less sensitive to such details.
It really feels like a kludge: why attributes doesn't inherit the namespace of the element?
I think it's because of "backward compatibility", which is too bad, because it's obvious that they would need something like namespace to prevent clashes.
*Sigh*
Mod the parent up!
The sideline of CmdrTaco is definitely stupid..
In France, Valentin Lacambre provided a free hosting website (altern.org).
Then a user put nude picture of a French topmodel Estelle Haliday.
Her lawyer asked the picture to be removed, which was done (the account was closed).
Nevertheless the lawyer made a lawsuit which found Valentin Lacambre guilty.
To summarize, he would have to check everything posted on the thousand of website hosted, clearly it was impossible so he closed shop.
[]
:-)
>mostly local interactions
[]
you're right to say "mostly": the Einstein-Podolsky-Rosen experiment is a nice way of Nature to thumb its nose at locality
A non-locality which can not be used to send data faster than C..
*sigh* Nature is a weird beast.
Now if cellular automata can explain this, I'm eager to hear for the explanation!