If find some of the parts of your post quite weird: you're talking about the size of the 'dedicated fan base' but that's not a factor to decide if the show worth the money or not, what matter is the total number of viewers (and their age/income composition).
>To add insult to injury, Stern refuses to let MGM court other TV networks for a new home for SG-1. Well, that's a logical decision, otherwise SG-1 on the other TVnetwork might have competed with their own offering. Sure it probably upset even more fans but as they are probably upset already by the end of SG-1 on NBC, it doesn't really matter.
I fully agree since the open source nv driver didn't work for my GeForce6600 (Kubuntu 6.06TS).
As an aside, I wonder why there isn't some kind of 'backup X' configuration with the vesa driver for those who have a problem with their driver? At first I made a mistake and used fbdriver instead of the vesa driver trying to have X running to be able to use a web browser to get the closed source driver, this was frustrating, especially as Kubuntu starts with some kind of image during the boot, so I knew that it was possible to have X running, but finding how wasn't fun: Kubuntu (and Linux distrib in general) still lack polish..
Well compare the current numbers of Perl programmers to Lisp programmers and ask yourself which is the most succesful now? In the future do you expect the number of Lisp programmers to go up or down (and I mean real programmers, student using Lisp for 3 month then forgetting it do not count)?
Sure Lisp has been extremely successful, and you could say it's still successful because it has introduced many concepts which are used now. But the syntax == AST central to Lisp has clearly failed to catch on and has been probably the main reason of its current downfall.
I didn't say it was hard to learn, I said that it wasn't pleasant to read.
The complicated syntax present in the other languages is here not just to be hard to parse by the compiler but to try to make class, arrays, etc easier to grasp by the programmers: a good example is Perl! And the success of Perl compared to the failure of Lisp show quite clearly that I'm not alone for which syntax matter..
Now I don't like at all Perl, but Ruby or its twin Python are good.
But the thing is: with Linux, you still have to care about which hardware you have, check if the printer works with Linux before buying it, etc. With Windows, mostly you don't.
So as long as you can't swap OS easily, the OS is relevant.
Uh in which class Lisp is taught to beginners? I learned Lisp at the end of my scholarity and hated it.
"Lisp hate" is pretty easy to understand: Lisp syntax is aimed at making it simple to process by a Lisp program, this is quite useful for a programing point of view, but this doesn't mean that it is easy to understand for mens.
In much the same way that assembly language is the natural language for computers, Lisp is the natural representation of an AST, and both language aren't easy to read by humans.
>Without a hardware firewall, they don't even get a CHANCE to secure their systems before someone else takes over.
That's not true with Windows XP: it comes bundled with a firewall.
Sure it is required (pre-SP2) to activate manually Window's firewall *before* activating your network connection (never connect your network cable before activating the firewall).
But once this is done the firewall should be good enough to protect the computer for the time needed to patch Windows.
When I was looking at the research papers, the worst offenders of over-using acronyms were americans.
To add insult to the injury, not only did they used lots of acronyms, but they didn't even clearly defined them the first time they used a new acronym, grrr..
> it might lead to unexpected but cool developments.
You can say the same things about *any* research! The GP is right, finding materials with the correct strength is a huge problem, the biggest problem for the space elevator, divesting money on climbers is just stupid..
While I agree that it's a shame that BeOS died (applications were *much more* responsive and for a bonus a stock BeOS booted in 14s while Kubuntu on a 10* times more powerful computer takes 1min17s!), BeOS would not be able to use efficiently 80 FPU cores, these are not general purpose CPU you know..
All the apps must be recoded to use a beat like this efficiently.
> Every programmer should know Lisp, Smalltalk, and either C or some dialect of assembly language (ideally both)
At school we learned Lisp (among other languages), I have never used it afterwards and frankly while I understand that a language with such simple syntax is very powerful, its current impopularity is probably because programmers prefer programming langage with human friendly syntax so it will probably remain a "mostly-dead" language forever so I'm not convinced about the usefulness of learning it.
Also why only Smalltalk? Me I learned OO with Eiffel: Meyer's book is very good.
Well embedded PowerPC are not exactly the same price than a G5, you know.. So it's quite normal than Apple didn't sell a lot of PPC.
What would be interesting to know is what share Apple had of the 'high end PPC', I mean who cares about embedded CPU.. I'm sure the volume of Z80 sold is huge, yawn.
Except that the article also said that many tricks currently used on games renderers wouldn't work with ray-tracing: I'm thinking about bump-mapping.
To compensate the loss of these tricks, you need to add a *huge* amount of geometry to get the same result, so it's not so obvious that realtime raytracing will arrive fast..
So Egyptians used nanoparticles, but does-it mean that those nanoparticles were safe? We don't know.. Romans's use of lead doesn't mean that lead is safe, just that they haven't linked it with the illness created.
Also even if the nanoparticles used by Egyptian were safe, does it means that other nanoparticles are safe either? No way!
Note that nano or not, ideally we should test every components (especially new one, new molecules or new shape/size of the particles) to avoid asbestos|lead like problems.
Of course the problem is finding a test suite which is able to show the problems these component could create..
Agreed, and to add insult to the injury the LDAP ugly & weird syntax 'dn,cn,dc,etc' is *never* explained.. And when it is the explanation is incomprehensible.
If we'd classify tools by their elegance, LDAP would be well down the bottom:-( , too bad as it is supposed to be the replacement of NIS..
>But a "sci-fi" is called a "sci-fi" since it's based on a scientific probability.
Well more like it has 'science buzzwords' sprinkled here and there: I still remember the movie Stargate, where they detect instantly where a probe is and the probe has just been teleported several light years away..
That plus learning to speak egyptian in one week was a bit too much for me.
I disagree about your logic, sure Mac are quite identicals but there as so few of them that if you were randomly trying to access a computer, you'd have much better odds of finding a PC with a specific software version too say WindowsXP+IE for example than finding a Mac at all. So Mac doesn't make an interesting target because of their number.
Their security model is much better than Windows, that's true, so it helps but an interesting question is: what is the percentage of the users getting security updates on the computer? Because in case of remote exploitable vulnerabilities, the security model does'nt matter.. On Windows, people know that they have an insecure piece of crap so since broadband became common, a big number of people apply the OS update (application update is another thing unfortunately), it is possible that the security of MacOS X lure the users in not caring about patches..
Much like having a BMW tend to make you think you're safe, even though you're not that safe..
>And this is a problem to the end user because....?
He claimed that there was a common API, this is false. Whether this is a problem to the end user or not is irrelevant.
As for the copy/paste, first 3 years is not a lot (the KDE version at work is at least two year old: the one in RHE3), second I have some copy/paste issue from time to time with mozilla to KDE, they are very rare but it happened to me so it's not bullshit.
Slashdot Mirror
If find some of the parts of your post quite weird: you're talking about the size of the 'dedicated fan base' but that's not a factor to decide if the show worth the money or not, what matter is the total number of viewers (and their age/income composition).
>To add insult to injury, Stern refuses to let MGM court other TV networks for a new home for SG-1.
Well, that's a logical decision, otherwise SG-1 on the other TVnetwork might have competed with their own offering. Sure it probably upset even more fans but as they are probably upset already by the end of SG-1 on NBC, it doesn't really matter.
I fully agree since the open source nv driver didn't work for my GeForce6600 (Kubuntu 6.06TS).
As an aside, I wonder why there isn't some kind of 'backup X' configuration with the vesa driver for those who have a problem with their driver?
At first I made a mistake and used fbdriver instead of the vesa driver trying to have X running to be able to use a web browser to get the closed source driver, this was frustrating, especially as Kubuntu starts with some kind of image during the boot, so I knew that it was possible to have X running, but finding how wasn't fun: Kubuntu (and Linux distrib in general) still lack polish..
Well compare the current numbers of Perl programmers to Lisp programmers and ask yourself which is the most succesful now?
In the future do you expect the number of Lisp programmers to go up or down (and I mean real programmers, student using Lisp for 3 month then forgetting it do not count)?
Sure Lisp has been extremely successful, and you could say it's still successful because it has introduced many concepts which are used now.
But the syntax == AST central to Lisp has clearly failed to catch on and has been probably the main reason of its current downfall.
I didn't say it was hard to learn, I said that it wasn't pleasant to read.
The complicated syntax present in the other languages is here not just to be hard to parse by the compiler but to try to make class, arrays, etc easier to grasp by the programmers: a good example is Perl!
And the success of Perl compared to the failure of Lisp show quite clearly that I'm not alone for which syntax matter..
Now I don't like at all Perl, but Ruby or its twin Python are good.
But the thing is: with Linux, you still have to care about which hardware you have, check if the printer works with Linux before buying it, etc.
With Windows, mostly you don't.
So as long as you can't swap OS easily, the OS is relevant.
Uh in which class Lisp is taught to beginners? I learned Lisp at the end of my scholarity and hated it.
"Lisp hate" is pretty easy to understand: Lisp syntax is aimed at making it simple to process by a Lisp program, this is quite useful for a programing point of view, but this doesn't mean that it is easy to understand for mens.
In much the same way that assembly language is the natural language for computers, Lisp is the natural representation of an AST, and both language aren't easy to read by humans.
>Without a hardware firewall, they don't even get a CHANCE to secure their systems before someone else takes over.
That's not true with Windows XP: it comes bundled with a firewall.
Sure it is required (pre-SP2) to activate manually Window's firewall *before* activating your network connection (never connect your network cable before activating the firewall).
But once this is done the firewall should be good enough to protect the computer for the time needed to patch Windows.
When I was looking at the research papers, the worst offenders of over-using acronyms were americans.
To add insult to the injury, not only did they used lots of acronyms, but they didn't even clearly defined them the first time they used a new acronym, grrr..
So this means that the next time one's wife has the hiccup, you can suggest to her anal sex to cure the hiccup?
This would work best!
> it might lead to unexpected but cool developments.
You can say the same things about *any* research!
The GP is right, finding materials with the correct strength is a huge problem, the biggest problem for the space elevator, divesting money on climbers is just stupid..
While I agree that it's a shame that BeOS died (applications were *much more* responsive and for a bonus a stock BeOS booted in 14s while Kubuntu on a 10* times more powerful computer takes 1min17s!), BeOS would not be able to use efficiently 80 FPU cores, these are not general purpose CPU you know..
All the apps must be recoded to use a beat like this efficiently.
> they are nevertheless a bunch of young amateurs.
Amateur? Wasn't she payed? I thought so.
I've never heard of her before the 'scandal', but abusing people credulity is wrong whatever you do.
>inspections at great expense to himself. I'm sorry, no argument about government protecting people can justify that kind of behavior.
Somehow, I think that those who suffered from food poisoning would disagree with you.
As for the reset, oversimplifying problems is not a good way to discuss.
> Every programmer should know Lisp, Smalltalk, and either C or some dialect of assembly language (ideally both)
At school we learned Lisp (among other languages), I have never used it afterwards and frankly while I understand that a language with such simple syntax is very powerful, its current impopularity is probably because programmers prefer programming langage with human friendly syntax so it will probably remain a "mostly-dead" language forever so I'm not convinced about the usefulness of learning it.
Also why only Smalltalk? Me I learned OO with Eiffel: Meyer's book is very good.
I disagree: if you have a contract with someone and you violate the terms of the contract, you can be sued. How is playing at a casino different?
Well embedded PowerPC are not exactly the same price than a G5, you know..
So it's quite normal than Apple didn't sell a lot of PPC.
What would be interesting to know is what share Apple had of the 'high end PPC', I mean who cares about embedded CPU.. I'm sure the volume of Z80 sold is huge, yawn.
Thanks for your correction, the parent was so wrong, it's not funny..
Complex scene, but static scene, in mosts games you need dynamic scenes so building the 'acceleration structure' is much more difficult.
So I expect raytracing to come first to 'flyby' games, *yawn*, doesn't seem very exciting.
Except that the article also said that many tricks currently used on games renderers wouldn't work with ray-tracing: I'm thinking about bump-mapping.
To compensate the loss of these tricks, you need to add a *huge* amount of geometry to get the same result, so it's not so obvious that realtime raytracing will arrive fast..
So Egyptians used nanoparticles, but does-it mean that those nanoparticles were safe?
We don't know..
Romans's use of lead doesn't mean that lead is safe, just that they haven't linked it with the illness created.
Also even if the nanoparticles used by Egyptian were safe, does it means that other nanoparticles are safe either?
No way!
Note that nano or not, ideally we should test every components (especially new one, new molecules or new shape/size of the particles) to avoid asbestos|lead like problems.
Of course the problem is finding a test suite which is able to show the problems these component could create..
Agreed, and to add insult to the injury the LDAP ugly & weird syntax 'dn,cn,dc,etc' is *never* explained..
:-( , too bad as it is supposed to be the replacement of NIS..
And when it is the explanation is incomprehensible.
If we'd classify tools by their elegance, LDAP would be well down the bottom
>But a "sci-fi" is called a "sci-fi" since it's based on a scientific probability.
Well more like it has 'science buzzwords' sprinkled here and there: I still remember the movie Stargate, where they detect instantly where a probe is and the probe has just been teleported several light years away..
That plus learning to speak egyptian in one week was a bit too much for me.
I disagree about your logic, sure Mac are quite identicals but there as so few of them that if you were randomly trying to access a computer, you'd have much better odds of finding a PC with a specific software version too say WindowsXP+IE for example than finding a Mac at all.
So Mac doesn't make an interesting target because of their number.
Their security model is much better than Windows, that's true, so it helps but an interesting question is: what is the percentage of the users getting security updates on the computer? Because in case of remote exploitable vulnerabilities, the security model does'nt matter..
On Windows, people know that they have an insecure piece of crap so since broadband became common, a big number of people apply the OS update (application update is another thing unfortunately), it is possible that the security of MacOS X lure the users in not caring about patches..
Much like having a BMW tend to make you think you're safe, even though you're not that safe..
>And this is a problem to the end user because....?
He claimed that there was a common API, this is false.
Whether this is a problem to the end user or not is irrelevant.
As for the copy/paste, first 3 years is not a lot (the KDE version at work is at least two year old: the one in RHE3), second I have some copy/paste issue from time to time with mozilla to KDE, they are very rare but it happened to me so it's not bullshit.
If you told RMS this, he'd probably slap you (or at least verbally abuse you): remember RMS == Free Software, not open source.