Don't pretty all software vendors, open-source or not, include those scary ALL CAP DISCLAIMERs that basically tell you to go fuck yourself if something goes wrong? So how can you sue? Have those DISCLAIMERs been tested in court?
Just a thought: if what you're proposing becomes reality, the whole idea of "parties" will not be needed any more. Corporations and special interest groups will just get away with their party proxies and directly engage in legislation and policy-making, and get their policies, rather than representatives, voted.
Welcome to democracy 2.0, with less overhead while maintaining exact bug-to-bug compliance with democracy 1.0.
Well, two browsers (IE, Mozilla) are becoming faster but thousands more Web apps are probably going to find this an excuse for their continued obsession with more and more computer-heavy software features.
Well, I don't think they even tried to make the test case W3C-compliant. At least wrap the javascript in//<![CDATA[ and//]]> lines so we know you had the validator in mind when you did that page.
And I think nitpicking is particularly educational for Microsoft considering its history of misconduct.
Writing computer code used to be an art form with simplicity being the crowning achievement. We've mostly "solved" this "problem" by throwing hardware at it. It turned out to be a two-edged sword, freeing human talents from the computing power limit while lowering the barrier of entry so that cheap, fast, bad code drives away good code that takes art, talent and ordeals to develop.
While I'm not against the trend of Web-based computing, I do observe that software grows slower faster than hardware grows faster. I guess sometimes we've got to stop for a while, take a step back and see how things can be simplified instead of piling things on top of another in the hope of more powerful hardware becomes available.
And there are natural limits to hard, physical computing power, but human talent and imagination have no end. A piece of software simplified both algorithmically and mentally is worth a 1000x hardware boost.
Perhaps the fixation upon the unattainable body characteristics will be exactly what gives the next generation's geek girls their first ideas in differential geometry...
The woman in the drawing looks distinctively non-human. I wonder whether the designer had mistaken "astronaut" for "alien life" when she was doing that.
You've already been modded troll rightfully, but the byproduct of Na-S batteries is sodium polysulfate, a salt (which yield an alkaline solution under hydrolysis). And sodium doesn't get called an *alkali* metal because of its acidity.
> I mean, hits such as "programming in PHP sucks" or > "you must be an idiot to write production code in VB" > would count as +1 for PHP and VB, correspondingly!
This is the true spirit of our times. Any publicity is good publicity.
> so it all boils down to how knowledgeable the user is about security
But you're the one who brought up this "Linux makes creating malware handier and stealthier" argument, and you're now resorting to the same old, tiring "user incompetence" excuse?
And did you just pulled that argument from your ass, or have you actually worked on malware on Linux, Windows and Mac OS X and compared them before making that post?
And yes, some people are creating a false sense of security around Linux. But aren't you creating a false sense of threat as well?
It is not Linux that has made malware more threatening. Incompetent design (like this) and poor programming practice make has made malware possible, on all platforms, and now the popularity (or rather, low cost) of incompetent design and poor programming is making it rampant.
But next perhaps someone will tell me that Linux is doomed because most distros ship gcc and gdb by default and they're used to create malware.
You must be new here. This is/. and here "children" means the process you get from a fork() call, not some vaguely remembered bio-science concept that has something to do with a strange experience that no true/.er ever really knows.
BTW: Seven child processes were kill()ed during the making of this post.
but can it be extended so that plugins are not only run in their separate processes, but separate SELinux sandboxes as well?
Don't pretty all software vendors, open-source or not, include those scary ALL CAP DISCLAIMERs that basically tell you to go fuck yourself if something goes wrong? So how can you sue? Have those DISCLAIMERs been tested in court?
Just a thought: if what you're proposing becomes reality, the whole idea of "parties" will not be needed any more. Corporations and special interest groups will just get away with their party proxies and directly engage in legislation and policy-making, and get their policies, rather than representatives, voted.
Welcome to democracy 2.0, with less overhead while maintaining exact bug-to-bug compliance with democracy 1.0.
It's 2010 and you are still doing *that*.
"A sane default" is one of the basic principles of software design. The default values usually reflect how well a designer understands the users.
However, I don't find it particularly newsworthy either.
Well, two browsers (IE, Mozilla) are becoming faster but thousands more Web apps are probably going to find this an excuse for their continued obsession with more and more computer-heavy software features.
And yes, I am confused with this.
I feel sympathetic toward you. We both feel sad about something we cannot change.
However, nowhere in my original post indicated that I "consider web pages to still be static blocks of text with some images dotted around them."
And that's my bad not making myself understood. Perhaps my other post ( http://slashdot.org/comments.pl?sid=1611776&cid=31776606 ) is a little bit clearer.
But then again, I made these posts without much effort in eloquence. This is /. anyway ;)
Well, I don't think they even tried to make the test case W3C-compliant. At least wrap the javascript in //<![CDATA[ and //]]> lines so we know you had the validator in mind when you did that page.
And I think nitpicking is particularly educational for Microsoft considering its history of misconduct.
O RLY?
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fie.microsoft.com%2Ftestdrive%2FPerformance%2F01FlyingImages%2FDefault.html
Writing computer code used to be an art form with simplicity being the crowning achievement. We've mostly "solved" this "problem" by throwing hardware at it. It turned out to be a two-edged sword, freeing human talents from the computing power limit while lowering the barrier of entry so that cheap, fast, bad code drives away good code that takes art, talent and ordeals to develop.
While I'm not against the trend of Web-based computing, I do observe that software grows slower faster than hardware grows faster. I guess sometimes we've got to stop for a while, take a step back and see how things can be simplified instead of piling things on top of another in the hope of more powerful hardware becomes available.
And there are natural limits to hard, physical computing power, but human talent and imagination have no end. A piece of software simplified both algorithmically and mentally is worth a 1000x hardware boost.
You forgot a functional x86 emulator written in javascript so you can run Linux in Firefox in Linux in Firefox in Linux...
I feel sad about it when hardware acceleration is needed for rendering, what, websites.
We live in interesting times indeed. I want my Web back.
I agree, but meanwhile the GP's rocket has already gone *whoosh* into orbit...
Look on the bright side, bro.
Perhaps the fixation upon the unattainable body characteristics will be exactly what gives the next generation's geek girls their first ideas in differential geometry...
Nail Randall Monroe. He's a terrorist advocating the use of computers as weaponry. http://xkcd.com/504/
If they call it a war, you know what will happen to peace-time law.
The woman in the drawing looks distinctively non-human. I wonder whether the designer had mistaken "astronaut" for "alien life" when she was doing that.
I wonder what the theoretically possible highest score could be. LONG_MAX? ULONG_MAX? Or something entirely different?
oops, I mean polysulfide. See, that's perhaps why people think it's acid.
ZOMG SO4 ACID RAIN WE"RE DOOMED
You've already been modded troll rightfully, but the byproduct of Na-S batteries is sodium polysulfate, a salt (which yield an alkaline solution under hydrolysis). And sodium doesn't get called an *alkali* metal because of its acidity.
Those who can't appreciate the beauty of Lisp are doomed to rot in (mismatched) parenthesis hell.
BTW: use a real text editor.
I've always suspected that Google Go is just some Rob Pike & ken "fan service".
Never underestimate the power of fanboys.
> I mean, hits such as "programming in PHP sucks" or
> "you must be an idiot to write production code in VB"
> would count as +1 for PHP and VB, correspondingly!
This is the true spirit of our times. Any publicity is good publicity.
> so it all boils down to how knowledgeable the user is about security
But you're the one who brought up this "Linux makes creating malware handier and stealthier" argument, and you're now resorting to the same old, tiring "user incompetence" excuse?
And did you just pulled that argument from your ass, or have you actually worked on malware on Linux, Windows and Mac OS X and compared them before making that post?
And yes, some people are creating a false sense of security around Linux. But aren't you creating a false sense of threat as well?
It is not Linux that has made malware more threatening. Incompetent design (like this) and poor programming practice make has made malware possible, on all platforms, and now the popularity (or rather, low cost) of incompetent design and poor programming is making it rampant.
But next perhaps someone will tell me that Linux is doomed because most distros ship gcc and gdb by default and they're used to create malware.
You must be new here. This is /. and here "children" means the process you get from a fork() call, not some vaguely remembered bio-science concept that has something to do with a strange experience that no true /.er ever really knows.
BTW: Seven child processes were kill()ed during the making of this post.