Being against the government having the right to do something against you before you commit your first crime and being against letting these people live freely a few years after their first crime are not mutually exclusive. I think we can afford to not let them out if they are proven guilty but we would really open the system for abuse if we give the government the right to lock someone up before they do something illegal.
That would mean disallowing newbie users to multitask. If you don't do multitasking there are simpler alternatives to a full-blown desktop environment.
Did the thought ever occur to you that the press might be biased towards reporting about such shutdowns in "bad guy"-countries? Its not like there are no shutdowns of bars and such things in the Western World.
Chances are good this single multipurpose gadget would then be too big to fit into any of the pockets of normal clothes. In addition these would lead to the "one function breaks - have to buy completely new multipurpose gadget" problem
It gets a lot more complicated when you get more admins into the mix because then you will surely have at least one admin far less motivated and/or skilled than you seem to be.
An ego-centric view of the Linux World by KDE-Developers?
You can see it everywhere with KDE...starting with their braindamaged way of not using separate tarballs for every app and instead bundling the apps to arbitary categories which can be quite frustrating for people not using KDE wanting to use only a single app.
Which way is simpler for support of a web company?
To tell the customer how to install a ftp client, enter the correct information (like Host, Port, Username...) in complex dialogs and describe how to upload files or to simply tell the customer to type the URL ftp://user@host/blah/blah in his File->Save Dialog?
And we would be back to singletasking since multiple big Java Apps eat way too much memory to be used in parallel like we use "normal" apps now. (and we would have "Crash One - Crash All" problems in a similar way Java Plugins seem to be able to crash the whole browser from time to time)
If you want a bug-free system in the long run you should not hide (unexpected) errors from the user. Your program should alert the user in the best way it can (not some hidden logfile) so the bug gets reported and fixed.
Everyone knows Windows is exactly the same as Linux, but people irrationally hate Microsoft so they use and promote Linux just out of spite.
How the hell did that get an "+1 Insightful"?
Sorry to spoil your point but I use Linux because it suits me as a programmer better than Windows which is designed for Beginner-Level-Users. The two are definitly not the same and if you drop your Microsoft-centric view you might actually see there are more people out there except the "For Windows" and the "Against Windows" People.
The problem with OOP is that even though there are good arguments for it (and against it) most OOP-Zealots just use things like "Can't you see OOP is clearly superior" and call those arguments.
You have much to learn if you blindly tell about the advantages of one paradigm and dismiss the disadvantages. Every paradigm (imperative, functional, OOP,...) has both of them.
Personally I do not think OOP would make maintaining of Kernel Code easier since in the Kernel you have a real advantage from being able to image the Assembler-Code/Hardware-Operations involved. OOP is simply to far from actual Hardware to be used for this lowest level Programming.
If I remember correctly 2.5.0 (the start of the 2.5-development-branch) was identical to 2.4.15. The 2.6 stable branch simple needs some time. The early 2.4 were not exactly stable either.
I ran 2.5.70-bk12 or some similar version for over a year on my semi-production (if it does not work I do not have internet) internet-router/file-server/irc-bot-server/console -irc-client/console-icq-client/...-server at home for over a year. The only time I was forced to reboot was a power outage. Linux is not exactly unstable even in the development branch as long as you stay away from modules marked as "Experimental" or "Dangerous".
Config Tools ARE a bad thing if (and only if) every distribution uses a different config-tool for the same app. If you try out new distros every once in a while config-files stay 99% the same but config-tools are 100% different which is quite annoying.
It's not like CDs with lots of old songs on them are cheaper...
Re:Frank wants to know about Volvo repair.
on
Search By.... Email?
·
· Score: 2, Interesting
More like:
Alice wants to know about "Total Newbie"
Bob wants to know about "Yelp is shit"
Charlie wants to know about "I have a question..."
Dave wants to know about "Problem here" ...
At least most Support Forums with people too stupid to google their answers themselves look like this.
Slashdot Mirror
In most cases where kids commit violence the parents are to blame (at least partially) and its easier to blame the games than to blame themselves.
Being against the government having the right to do something against you before you commit your first crime and being against letting these people live freely a few years after their first crime are not mutually exclusive. I think we can afford to not let them out if they are proven guilty but we would really open the system for abuse if we give the government the right to lock someone up before they do something illegal.
I think this is one of the strong points in Open Source:
Nobody focuses on Marketing
When Open Source starts to enter the Marketing Arena the big way it becomes just as bells-and-whistles minded as closed source
That would mean disallowing newbie users to multitask. If you don't do multitasking there are simpler alternatives to a full-blown desktop environment.
Did the thought ever occur to you that the press might be biased towards reporting about such shutdowns in "bad guy"-countries? Its not like there are no shutdowns of bars and such things in the Western World.
Chances are good this single multipurpose gadget would then be too big to fit into any of the pockets of normal clothes. In addition these would lead to the "one function breaks - have to buy completely new multipurpose gadget" problem
It gets a lot more complicated when you get more admins into the mix because then you will surely have at least one admin far less motivated and/or skilled than you seem to be.
"stable" and "secure" are two totally different things. Also in kernelspace malicious code can do far worse than crashing your pc.
An ego-centric view of the Linux World by KDE-Developers?
You can see it everywhere with KDE...starting with their braindamaged way of not using separate tarballs for every app and instead bundling the apps to arbitary categories which can be quite frustrating for people not using KDE wanting to use only a single app.
Which way is simpler for support of a web company?
To tell the customer how to install a ftp client, enter the correct information (like Host, Port, Username...) in complex dialogs and describe how to upload files or to simply tell the customer to type the URL ftp://user@host/blah/blah in his File->Save Dialog?
You seem to know nothing about programming if you think "robust"=="complex features"
And we would be back to singletasking since multiple big Java Apps eat way too much memory to be used in parallel like we use "normal" apps now. (and we would have "Crash One - Crash All" problems in a similar way Java Plugins seem to be able to crash the whole browser from time to time)
If you want a bug-free system in the long run you should not hide (unexpected) errors from the user. Your program should alert the user in the best way it can (not some hidden logfile) so the bug gets reported and fixed.
Sorry to spoil your point but I use Linux because it suits me as a programmer better than Windows which is designed for Beginner-Level-Users. The two are definitly not the same and if you drop your Microsoft-centric view you might actually see there are more people out there except the "For Windows" and the "Against Windows" People.
*looks at Western Politician*
What did you say about Western and honest again?
The problem with OOP is that even though there are good arguments for it (and against it) most OOP-Zealots just use things like "Can't you see OOP is clearly superior" and call those arguments.
You have much to learn if you blindly tell about the advantages of one paradigm and dismiss the disadvantages. Every paradigm (imperative, functional, OOP,...) has both of them.
Personally I do not think OOP would make maintaining of Kernel Code easier since in the Kernel you have a real advantage from being able to image the Assembler-Code/Hardware-Operations involved. OOP is simply to far from actual Hardware to be used for this lowest level Programming.
The Hardware solution can provide something no OS can: Multiple Monitors without using all your PCI Slots for additional cards
If I remember correctly 2.5.0 (the start of the 2.5-development-branch) was identical to 2.4.15. The 2.6 stable branch simple needs some time. The early 2.4 were not exactly stable either.
I ran 2.5.70-bk12 or some similar version for over a year on my semi-production (if it does not work I do not have internet) internet-router/file-server/irc-bot-server/console -irc-client/console-icq-client/...-server at home for over a year. The only time I was forced to reboot was a power outage. Linux is not exactly unstable even in the development branch as long as you stay away from modules marked as "Experimental" or "Dangerous".
Config Tools ARE a bad thing if (and only if) every distribution uses a different config-tool for the same app. If you try out new distros every once in a while config-files stay 99% the same but config-tools are 100% different which is quite annoying.
It's not like CDs with lots of old songs on them are cheaper...
More like:
...
Alice wants to know about "Total Newbie"
Bob wants to know about "Yelp is shit"
Charlie wants to know about "I have a question..."
Dave wants to know about "Problem here"
At least most Support Forums with people too stupid to google their answers themselves look like this.