I don't see what MySQL provides to Oracle. How long would it take Oracle to create a defeatured version of their database product that has about the same features as MySQL. It's not as if MySQL has some great database secrets that Oracle doesn't already know about.
I agree. Developers today (at least the vocal ones) seem to be a lot more interested in putting down the work of others than improving their own. That's why there are sites like The Daily WTF.
TCP isn't a specification either. Has there ever been a clean-room implementation of Internet Protocols? I doubt a working implementation could be created based solely on RFC's.
Wow, if only the seven-year-olds new that the DS used DRM they would certainly get rid of it and wait until a similar device was available based on Linux (about the time they want to start playing brain age to help combat alzheimer's).
You claim that Moonlight code is "infected" with code that implements a Microsoft patent. Since the source code is available to you, you should be able to show us a sample of the code and tell us which MS patent it embodies.
If you can't find it, look in your ass. Many Slashdotters have been able to pull stuff out of theirs.
You missed my point. Why do you need to check if everybody's style is identical? In other words, everybody's style isn't identical and that's why you check.
As for a better style, you're barking up the wrong tree. There's little correlation between any particular style and a successful product. The evidence is all the great applications that have been written over time with vastly different styles.
Of course checking people's style is a great way to pass the hours and a hell of a lot easier than confirming that code is actually going to work.
"What fits on a page is really quite simple. Typesetters, etc, have decent rules of thumb about line length, font size, and easy of right-to-left tracking after hitting the end of a line. Somewhere around 140 characters is reasonable for a modern computer. 500 chars is not."
You make my point. What fits on a page isn't constant over time.
"What happens when I leave? Nothing. We have 100+ programmers with almost identical style: they enforce keeping the codebase clean and consistent"
So you have no need to check for compliance, since everybody's style is identical, right? There are actually following a standard established by their employer. Following orders isn't the same as approving of it. In any company, there are those who have the power to change policy sometimes at lower levels, sometimes at higher levels.
"I don't even know what you mean by "program correctness." Formal methods? Nailing the spec? Passing the unittests? Doing what the users expect? Selling well? I do know that consistent, understandable, well-crafted code is required for anything more than throwaway projects."
Program correctness means as bug free as is reasonably possible (i.e. the code meets the spec).
"If you find something by the side of the road, take it, and leave a note for the rightful owner, is it stealing if the owner never comes to claim it?
The answer to that question isn't relevant to this issue because the books that Google is scanning cannot be said to be "by the side of the road" in any way, shape, or form.
"Instead of bashing someone who decides to spend the money to implement a solution, why don't you just compete with them. Scan these books yourself and offer them online."
The only "problem" that Google is attempting to solve is how to make more money for Google. Nobody has been clamoring for these books to be scanned.
Don't worry. In 20 years the future equivalent of the Borg will be part of the logo that the future equivalent of Slashdot will be using with articles about Google.
Is that the 40 x 25 page, the 80 x 25 page, oh that's right, for you it's the 70 x something page. What "fits nicely" today probably won't tomorrow.
And what happens when you leave the company? Another guy comes in with a different set of "best" idioms and has everyone modify the code accordingly. I've seen it happen before.
If you focus on real program correctness, you won't have time to be so anal.
"I bitch about poor function names, bad idioms, pointless abstractions, code that rolls past 140 columns or so: don't leave crap that slows down the next person."
So I guess on the slow days, you consider minor issues like program correctness.
"If a programmer can't deal with pair programming them they're a very poor programmer."
That's like saying that sculptor must be a poor artist if he can't handle sculpting with a partner.
Being able to handle pair programming is a good talent to have since you may be required to do it, but it's really about communication skills, not programming skills.
Slashdot Mirror
I don't see what MySQL provides to Oracle. How long would it take Oracle to create a defeatured version of their database product that has about the same features as MySQL. It's not as if MySQL has some great database secrets that Oracle doesn't already know about.
I agree. Developers today (at least the vocal ones) seem to be a lot more interested in putting down the work of others than improving their own. That's why there are sites like The Daily WTF.
TCP isn't a specification either. Has there ever been a clean-room implementation of Internet Protocols? I doubt a working implementation could be created based solely on RFC's.
Wow, if only the seven-year-olds new that the DS used DRM they would certainly get rid of it and wait until a similar device was available based on Linux (about the time they want to start playing brain age to help combat alzheimer's).
See title.
You're just repeating the Linux fan-box FUD. You haven't looked at any of the Moonlight code and you haven't done any research on MS patents.
Who other than geeks knows about the Star Wars kid?
You claim that Moonlight code is "infected" with code that implements a Microsoft patent. Since the source code is available to you, you should be able to show us a sample of the code and tell us which MS patent it embodies.
If you can't find it, look in your ass. Many Slashdotters have been able to pull stuff out of theirs.
I'd listen to my senior coworkers but it's hard to find workers that have more than 25 years experience.
You missed my point. Why do you need to check if everybody's style is identical? In other words, everybody's style isn't identical and that's why you check.
As for a better style, you're barking up the wrong tree. There's little correlation between any particular style and a successful product. The evidence is all the great applications that have been written over time with vastly different styles.
Of course checking people's style is a great way to pass the hours and a hell of a lot easier than confirming that code is actually going to work.
I wish EVERYTHING was back to normal.
With everyone trying to create the newest and greatest thing to make money from, do people even follow or refer to RFC's for compliance?"
Do you mean the 'C' in RFC stands for compliance rather than comments?
this anniversary really would be a BFD.
"What fits on a page is really quite simple. Typesetters, etc, have decent rules of thumb about line length, font size, and easy of right-to-left tracking after hitting the end of a line. Somewhere around 140 characters is reasonable for a modern computer. 500 chars is not."
You make my point. What fits on a page isn't constant over time.
"What happens when I leave? Nothing. We have 100+ programmers with almost identical style: they enforce keeping the codebase clean and consistent"
So you have no need to check for compliance, since everybody's style is identical, right? There are actually following a standard established by their employer. Following orders isn't the same as approving of it. In any company, there are those who have the power to change policy sometimes at lower levels, sometimes at higher levels.
"I don't even know what you mean by "program correctness." Formal methods? Nailing the spec? Passing the unittests? Doing what the users expect? Selling well? I do know that consistent, understandable, well-crafted code is required for anything more than throwaway projects."
Program correctness means as bug free as is reasonably possible (i.e. the code meets the spec).
"If you find something by the side of the road, take it, and leave a note for the rightful owner, is it stealing if the owner never comes to claim it?
The answer to that question isn't relevant to this issue because the books that Google is scanning cannot be said to be "by the side of the road" in any way, shape, or form.
Sorry, but that's a bit abstract for me to get excited about.
"Instead of bashing someone who decides to spend the money to implement a solution, why don't you just compete with them. Scan these books yourself and offer them online."
The only "problem" that Google is attempting to solve is how to make more money for Google. Nobody has been clamoring for these books to be scanned.
"Who else is making a serious effort to get a hold of these orphan books and put them out there? Last I checked, absolutely no one."
So if only a single thief is interested in ripping something off it makes it OK?
Don't worry. In 20 years the future equivalent of the Borg will be part of the logo that the future equivalent of Slashdot will be using with articles about Google.
I think you overestimate the significance of a Democratic President.
It just happened that a Democrat was in the White House when MS wasn't pouring money into Washington and their competitors were.
If just happened that a Republican was in the White House when MS corrected their problem by starting to pour money into Washington too.
MS has no interest in buying Sun. If they were really interested they would have bought them a long time ago.
Is that the 40 x 25 page, the 80 x 25 page, oh that's right, for you it's the 70 x something page. What "fits nicely" today probably won't tomorrow.
And what happens when you leave the company? Another guy comes in with a different set of "best" idioms and has everyone modify the code accordingly. I've seen it happen before.
If you focus on real program correctness, you won't have time to be so anal.
"I bitch about poor function names, bad idioms, pointless abstractions, code that rolls past 140 columns or so: don't leave crap that slows down the next person."
So I guess on the slow days, you consider minor issues like program correctness.
shouldn't mock those who believe they are too.
"If a programmer can't deal with pair programming them they're a very poor programmer."
That's like saying that sculptor must be a poor artist if he can't handle sculpting with a partner.
Being able to handle pair programming is a good talent to have since you may be required to do it, but it's really about communication skills, not programming skills.