First, the suers should be liable to be sued back if their claims are shown to be unsubstantiated, to avoid this 'buy-a-lottery-ticket-suits'.
Second, what about the modern warranties, those that say 'This product is sold in hopes that it will be useful, but we don't claim anything about it, particularly fitness for any particular purpose'? Maybe if you put a marketroid and a lawyer in the same room, they will cancel each other in an explosion of hype/downplay reaction. Wouldn't that be nice? Less marketroids, less lawyers, more energy! (not necessarily fit for any particular purpose)
Or Debian, for that matter. For one, they don't get much mainstream coverage. Then, they require you to know what you're doing, or at least the names of the programs you want. A newbie unfortunate enough to be faced with these distros(my information is more than two years old, beware) would just run back to his W98 CD... As for the problems that the users have, expect to see more and more from the more popular distros, because that's where the newbies will be.
"Linus' needs are what drive kernel development, not overall needs and issues."
Well I sure want to have 'needs' like those... As for the PCMCIA and IP implementations, I dunno: did you actually do better and got your changes rejected?
They don't do anything in TeX either, but it's not what THEY can do with it... I guess they really should have included the free software version of Qt.
The advantage of using Slackware is that you tend to be more in control over what you actually have installed on your system. I used to be a Slackware user, then tried Redhat, now SuSE, and the latter take care of many things for you; if that is good or bad depends on your personal taste.
What you fail to see is that the people who might believe this kind of crap is not reading Slashdot. The target audience seldom finds out about how gross the misrepresentation is, and we already know... The fact that we can read the article does not mean it's intended for us.
A full-time job, maybe. But dangerous? And for NT, you don't get specific patches, so if you have ONE problem which is addressed by a SP, you are playing Russian roulette, as maybe more bugs will be 'created'. You can't get very surgical with 4 service patches^H^H^H^H^Hcks...
Maybe what they should do is send people over to TEACH them how it is done. Show them the how so there comes a time in which users actually care for their system's security, [not to mention the systems programmers]. In the meantime, we will live in interesting times, but then again, don't we now?
You are right about the BSD license. That much is true. So, why in hell must you go calling names? If you are right but clueless, it leads one to wonder whether you are right just by chance...
Does 'the problem will get even worse' mean that Nintendo will begin to lose real money to pirates? Just imagine, all that is needed for the last game to be enjoyed by all the Net is buying ONE copy, then perhaps waiting one week to circumvent the last anti-piracy trick. Do you think they could stay in business like that? Well, maybe they wouldn't have to close, they'd just have to lay some people off, most likely not the CEO. How cool, almost 3l33t...
I always thought RMS has a real point here. Good performance is cool, but not the central issue. The central issue is that software should be FREE. I would say the priorities are freedom first, then robustness, then performance. Oh, and point-and-drool^H^H^H^H^H^H^H^H^H^H^H ease of use.
Slashdot Mirror
First, the suers should be liable to be sued back if their claims are shown to be unsubstantiated, to avoid this 'buy-a-lottery-ticket-suits'.
Second, what about the modern warranties, those that say 'This product is sold in hopes that it will be useful, but we don't claim anything about it, particularly fitness for any particular purpose'? Maybe if you put a marketroid and a lawyer in the same room, they will cancel each other in an explosion of hype/downplay reaction.
Wouldn't that be nice? Less marketroids, less lawyers, more energy! (not necessarily fit for any particular purpose)
JM
Or Debian, for that matter. For one, they don't get much mainstream coverage. Then, they require you to know what you're doing, or at least the names of the programs you want. A newbie unfortunate enough to be faced with these distros(my information is more than two years old, beware) would just run back to his W98 CD...
As for the problems that the users have, expect to see more and more from the more popular distros, because that's where the newbies will be.
The GPL is far from free in that it enforces its own morality on anyone that might want to use it.
Not really. You would only want to use the GPL *IF* you agree with its morality(I do). What would otherwise be the reason, the cool name?
"Linus' needs are what drive kernel development, not overall needs and issues."
Well I sure want to have 'needs' like those...
As for the PCMCIA and IP implementations, I dunno: did you actually do better and got your changes rejected?
JM
They don't do anything in TeX either, but it's not what THEY can do with it... I guess they really should have included the free software version of Qt.
The advantage of using Slackware is that you tend to be more in control over what you actually have installed on your system. I used to be a Slackware user, then tried Redhat, now SuSE, and the latter take care of many things for you; if that is good or bad depends on your personal taste.
What you fail to see is that the people who might believe this kind of crap is not reading Slashdot. The target audience seldom finds out about how gross the misrepresentation is, and we already know... The fact that we can read the article does not mean it's intended for us.
A full-time job, maybe. But dangerous? And for NT, you don't get specific patches, so if you have ONE problem which is addressed by a SP, you are playing Russian roulette, as maybe more bugs will be 'created'. You can't get very surgical with 4 service patches^H^H^H^H^Hcks...
I loved the part of a service pack causing bugs in the OS. Go figure, they sell them as being the other way 'round...
Maybe what they should do is send people over to TEACH them how it is done. Show them the how so there comes a time in which users actually care for their system's security, [not to mention the systems programmers]. In the meantime, we will live in interesting times, but then again, don't we now?
You are right about the BSD license. That much is true. So, why in hell must you go calling names? If you are right but clueless, it leads one to wonder whether you are right just by chance...
Does 'the problem will get even worse' mean that Nintendo will begin to lose real money to pirates?
Just imagine, all that is needed for the last game to be enjoyed by all the Net is buying ONE copy, then perhaps waiting one week to circumvent the last anti-piracy trick. Do you think they could stay in business like that? Well, maybe they wouldn't have to close, they'd just have to lay some people off, most likely not the CEO. How cool, almost 3l33t...
I always thought RMS has a real point here. Good performance is cool, but not the central issue. The central issue is that software should be FREE. I would say the priorities are freedom first, then robustness, then performance. Oh, and point-and-drool^H^H^H^H^H^H^H^H^H^H^H ease of use.
JMH