... the less tolerant people get. The less tolerant people get, the more censorship needs to be applied to protect people from 'inappropriate' material.
Give people their free speech. If you don't like what they say, don't listen, but respect their rights.
Productivity will hardly be influenced at all. When Google goes down for 72 hours, people will switch back to AltaVista for a few days. If Google *regularly* goes down for 72 hours, people will switch back permanently. It's not like they Google are the *only* search engine around, they're just the most popular.
This question is entirely besides the point though. As it is in Google's interest to stay the most popular search engine, I'm sure they have got their backup mechanisms in place. I'm pretty sure they can guarantee that they *will not* go down for 72 hours *ever*.
Sounds like Cliff Richard et al aren't happy about the idea of copyrights on their old recordings 'expiring'... and let me guess, they protest because it is so more convenient to keep collecting dough for an effort that you made in a long lost past than it is to come up with something good enough to live up to the standards of today?
"I remember when they improved the error messages you get in Internet Explorer"
Don't make me laugh. The error messages in Explorer are pitiful, and haven't gotten any better, just more verbose. IE is not alone in this however. To illustrate the point, exactly the same goes for Oracle messages such as ORA-00942 "View or table does not exist"
So *which* view or table does not exist? The message can be made more verbose:
"The view or table that you tried to access does not exist. Check if the specified view exists, and if it doesn't, if there is a table of that name. If neither is the case, you can create one. Are you still reading? Please bring me a sixpack next time you want me to find the table for you."
but a much better approach would be to parameterize the error message:
"View or table 'pesron' does not exist"
This would *immediately* make clear that the word 'person' was misspelled, possibly saving hours of bug-hunting time. I'll accept the extra verbosity built-in for 'stupid' users, but at least give me some troubleshooting information so that I can fix what the hell is wrong.
BZZZZZZZT wrong:) Sound needs a medium to propagate. This medium isn't restricted to air, however. Your desk will do fine as a medium to transfer vibrations, and if acoustic sensors are attached to it firmly enough, they will pick up the typing vibrations just fine, even in a vacuum.
All you need is Windows experience (which everyone has nowadays). Linux requires special knowledge and/or training.
Why it is that on Windows you call it experience, whereas on Linux you call it 'special knowledge'? It is the same thing.
Linux isn't user friendly enough for the average workplace drone to administer....and nor is Windows, if you want to make sure it's done right. It requires some "special knowledge" to get things right.
most small/medium companies can't afford to hire somebody extra purely because they have Linux experience.
As you mentioned, you don't need 'someone extra'- just employees that are more versatile. This will in fact help you to operate with less people. Replace the first two techies that leave your company with people that (also) know Linux and you're set.
Of course, if your company does have people familiar with Linux, then the TCO is going to be WAAAAY lower.
Q.E.D.
Do you really think that 0.05% of all spam comes from Linux, BSD, MacOS, Solaris and OS/2 lumped together? Then I'll have to disappoint you. Look again. Windows 95 is curiously absent from the graph. How big a part of 0.05% do you think it could handle?
I'm sure the users of my cross-platform C++ application (hd24tools) wouldn't complain that it is supported on Linux. It *started* on Linux, because *I* needed it on Linux. I don't need any more argumentation than that to keep supporting it on Linux. It is making it available to the *other* platforms that costs (some) extra time.
This could very easily be replicated in praticially any web scripting language of your choice. Exactly. It doesn't require any client-side processing. That's the beauty of it. This means you can TURN OFF javascript and it will still work.
As for the innovation- it allows a user to enter their pin while reducing the chance that it's snooped by malware, which is a Good Thing. It also makes it a lot harder for said malware to replicate the response compared to keyboard entry- because in addition to protecting your code, it also acts as a (primitive) captcha, making reasonably sure that whoever is entering the code is human.
The main problem I see with adapting new practices is that project management relies on discipline as a replacement for motivation. This Does Not Work. Discipline alone is not enough- This is why for instance source control systems have been invented.
At some point at our company we started 'crosschecking'- which essentially means all developers have their code tested by another developer, mostly before things got to nightly build. (Other quality assurance practices are also already in place).
The result was twofold. First of all, incorrect code was communicated back the same day, or even several times the same day. This saved a huge amount of time in detecting problems. Second, because each developer knows their code is going to be reviewed by another developer, they try harder to avoid the bugs in the first place.
The first release after we introduced this practice, we noticed that the bugs being reported by the client mostly had to do with previous releases. The bug rate has steadily decreased since, and we're not constantly patching holes anymore. We catch most bugs before we deliver the product to the client- so the client is happier too. We spend more time doing 'fun' stuff now, rather than bug hunting. And it is quite an ego boost to ship a product and not hear of any defects. Would we stop crosschecking, we would have the feeling that we are shipping an inferior product.
By making sure the practices to adopt are insanely useful, time savers and make the work more fun, developers will adopt them without complaining.
What happens after a couple of years of having this duck farm and the water contains a slightly larger percentage of minerals? Simple. This will not happen. As the water is used and/or evaporates, eventually it find its way back to the sea, restoring the salt balance.
What the fuck is wrong with people who will go out and vote more power to Bush and his fucking fascist government this Tuesday? Can Bush even be president again? I thought US law only permitted 2 consecutive terms for any president, to offer some protection against evil dictators.
I couldn't even figure out how to draw a box in GIMP Simple. Select a box, then edit->stroke selection. Lines are harder- I think they require the shift or ctrl key.
The problem is not that GIMP is difficult to use- it and Photoshop are just different. When you consistently use one, the other seems awkward. I've gotten used to the GIMP and can draw pretty much anything I want with it. Maybe at some point I'll even put up a page for it.
However, assuming that a seasoned Photoshop pro is just going to switch to the GIMP is utterly naive.
As for the capabilities of GIMP, I've dug pretty deep but for sure the limiting factor so far is still me, not the program. I find the Photoshop tutorials (and worth1000.com) very worthwhile to study though, most techniques map pretty well to the GIMP.
If you want to be fair, you should compare modperl with the modular version of php.
Syntactically, they're relatively similar. Obviously the PHP/Zend folks knew perl before they started on PHP.
Perl was originally intended for string handling, but is also quite suitable for general-purpose programming. Perl has CPAN- almost any module you'll ever need is probably already there.
PHP was originally intended as HTML Preprocessor - so it is specifically targeted at web programming. Which of the two is "better"? Maybe we'll let the statistics speak for themselves.
Any HTML page is a valid PHP page. You can sprinkle some PHP in an existing HTML page for some automation (which can end up in a big mess if you're not careful). As such, if you have an existing website in which you want to add a little bit of automation, PHP is most likely the 'best' option.
In perl it's the other way around- you start out with code and put bits of web page generation in there. As such, if you have an existing program that you want to port to be web-enabled, perl may be a better choice.
Slashdot Mirror
... the less tolerant people get. The less tolerant people get, the more censorship needs to be applied to protect people from 'inappropriate' material.
Give people their free speech. If you don't like what they say, don't listen, but respect their rights.
... Time for you to leave.
Productivity will hardly be influenced at all. When Google goes down for 72 hours, people will switch back to AltaVista for a few days. If Google *regularly* goes down for 72 hours, people will switch back permanently. It's not like they Google are the *only* search engine around, they're just the most popular.
This question is entirely besides the point though. As it is in Google's interest to stay the most popular search engine, I'm sure they have got their backup mechanisms in place. I'm pretty sure they can guarantee that they *will not* go down for 72 hours *ever*.
Sounds like Cliff Richard et al aren't happy about the idea of copyrights on their old recordings 'expiring' ... and let me guess, they protest because it is so more convenient to keep collecting dough for an effort that you made in a long lost past than it is to come up with something good enough to live up to the standards of today?
"I remember when they improved the error messages you get in Internet Explorer"
Don't make me laugh. The error messages in Explorer are pitiful, and haven't gotten any better, just more verbose. IE is not alone in this however. To illustrate the point, exactly the same goes for Oracle messages such as ORA-00942 "View or table does not exist"
So *which* view or table does not exist? The message can be made more verbose:
"The view or table that you tried to access does not exist. Check if the specified view exists, and if it doesn't, if there is a table of that name. If neither is the case, you can create one. Are you still reading? Please bring me a sixpack next time you want me to find the table for you."
but a much better approach would be to parameterize the error message:
"View or table 'pesron' does not exist"
This would *immediately* make clear that the word 'person' was misspelled, possibly saving hours of bug-hunting time. I'll accept the extra verbosity built-in for 'stupid' users, but at least give me some troubleshooting information so that I can fix what the hell is wrong.
Sure, go ahead, mod the parent down because you don't like to hear their opinion. It's a perfectly valid one though.
Dutch license plates are usually in XX-YY-ZZ format. So the license plate on the picture is probably French.
BZZZZZZZT wrong :) Sound needs a medium to propagate. This medium isn't restricted to air, however. Your desk will do fine as a medium to transfer vibrations, and if acoustic sensors are attached to it firmly enough, they will pick up the typing vibrations just fine, even in a vacuum.
All you need is Windows experience (which everyone has nowadays). Linux requires special knowledge and/or training. Why it is that on Windows you call it experience, whereas on Linux you call it 'special knowledge'? It is the same thing.
...and nor is Windows, if you want to make sure it's done right. It requires some "special knowledge" to get things right.
Linux isn't user friendly enough for the average workplace drone to administer.
most small/medium companies can't afford to hire somebody extra purely because they have Linux experience.
As you mentioned, you don't need 'someone extra'- just employees that are more versatile. This will in fact help you to operate with less people. Replace the first two techies that leave your company with people that (also) know Linux and you're set.
Of course, if your company does have people familiar with Linux, then the TCO is going to be WAAAAY lower.
Q.E.D.
... just wait until Duke Nukem Forever is released!
Turns out it is 1.58573928 furlongs high.
"with sediment as deep as the Chrysler Building is high" Sorry- can someone convert that to furlongs?
come on, isn't it a little much to explicitly point it out in this case? :)
No
Do you really think that 0.05% of all spam comes from Linux, BSD, MacOS, Solaris and OS/2 lumped together? Then I'll have to disappoint you. Look again. Windows 95 is curiously absent from the graph. How big a part of 0.05% do you think it could handle?
I'm sure the users of my cross-platform C++ application (hd24tools) wouldn't complain that it is supported on Linux. It *started* on Linux, because *I* needed it on Linux. I don't need any more argumentation than that to keep supporting it on Linux. It is making it available to the *other* platforms that costs (some) extra time.
This was previously posted tomorrow.
Most closed source software is abandoned, buried and full of bugs as well. Conveniently, he ignores that fact.
This could very easily be replicated in praticially any web scripting language of your choice.
Exactly. It doesn't require any client-side processing. That's the beauty of it. This means you can TURN OFF javascript and it will still work.
As for the innovation- it allows a user to enter their pin while reducing the chance that it's snooped by malware, which is a Good Thing. It also makes it a lot harder for said malware to replicate the response compared to keyboard entry- because in addition to protecting your code, it also acts as a (primitive) captcha, making reasonably sure that whoever is entering the code is human.
The main problem I see with adapting new practices is that project management relies on discipline as a replacement for motivation. This Does Not Work. Discipline alone is not enough- This is why for instance source control systems have been invented.
At some point at our company we started 'crosschecking'- which essentially means all developers have their code tested by another developer, mostly before things got to nightly build. (Other quality assurance practices are also already in place).
The result was twofold. First of all, incorrect code was communicated back the same day, or even several times the same day. This saved a huge amount of time in detecting problems. Second, because each developer knows their code is going to be reviewed by another developer, they try harder to avoid the bugs in the first place.
The first release after we introduced this practice, we noticed that the bugs being reported by the client mostly had to do with previous releases. The bug rate has steadily decreased since, and we're not constantly patching holes anymore. We catch most bugs before we deliver the product to the client- so the client is happier too. We spend more time doing 'fun' stuff now, rather than bug hunting. And it is quite an ego boost to ship a product and not hear of any defects. Would we stop crosschecking, we would have the feeling that we are shipping an inferior product.
By making sure the practices to adopt are insanely useful, time savers and make the work more fun, developers will adopt them without complaining.
What happens after a couple of years of having this duck farm and the water contains a slightly larger percentage of minerals? Simple. This will not happen. As the water is used and/or evaporates, eventually it find its way back to the sea, restoring the salt balance.
...as long as Duke Nukem Forever is released.
What the fuck is wrong with people who will go out and vote more power to Bush and his fucking fascist government this Tuesday? Can Bush even be president again? I thought US law only permitted 2 consecutive terms for any president, to offer some protection against evil dictators.
Maybe Arnie is a better bet these days.
I couldn't even figure out how to draw a box in GIMP
Simple. Select a box, then edit->stroke selection. Lines are harder- I think they require the shift or ctrl key.
The problem is not that GIMP is difficult to use- it and Photoshop are just different. When you consistently use one, the other seems awkward. I've gotten used to the GIMP and can draw pretty much anything I want with it. Maybe at some point I'll even put up a page for it.
However, assuming that a seasoned Photoshop pro is just going to switch to the GIMP is utterly naive.
As for the capabilities of GIMP, I've dug pretty deep but for sure the limiting factor so far is still me, not the program. I find the Photoshop tutorials (and worth1000.com) very worthwhile to study though, most techniques map pretty well to the GIMP.
If you want to be fair, you should compare modperl with the modular version of php.
Syntactically, they're relatively similar. Obviously the PHP/Zend folks knew perl before they started on PHP.
Perl was originally intended for string handling, but is also quite suitable for general-purpose programming. Perl has CPAN- almost any module you'll ever need is probably already there.
PHP was originally intended as HTML Preprocessor - so it is specifically targeted at web programming. Which of the two is "better"? Maybe we'll let the statistics speak for themselves.
Any HTML page is a valid PHP page. You can sprinkle some PHP in an existing HTML page for some automation (which can end up in a big mess if you're not careful). As such, if you have an existing website in which you want to add a little bit of automation, PHP is most likely the 'best' option.
In perl it's the other way around- you start out with code and put bits of web page generation in there. As such, if you have an existing program that you want to port to be web-enabled, perl may be a better choice.