I have found this to be _especially_ important for bug-fixes. Very important to document why things were done a certain way to minimize implicit side effects.
Yes. These can be comments in code, but SVN (or any SCM) commit comments are also extremely useful for this.
ClearView doesn't have to prove that a program is either correct or incorrect. It only has to detect certain types of bugs, and fix them. There is no guarantee your program is correct after running it.
And personally I can't think of any cases where a buffer overflow is part of a correct program...
#1 is better for both, because #1 pays the bills. Developers that waste their time on features nobody uses should be removed from the industry. They should talk to users, and find out why users like #1 better.
Actually it costs tens of dollars to produce per item (I read in my local newspaper), much more than the cost of the magazine, and probably more then the advertiser paid for it. But it will only be available in a couple of thousand magazines, so the total cost is likely a couple of hundred thousand dollars.
And now think of the advertising value. In my local newspaper, on slashdot,.... Way higher than you could hope to get spending that much on a traditional advertisement.
Yes, big difference; all combinations are possible:
Strong and Statically typed: Scala, Java, C++ Strong and Dynamically typed: Python, Ruby Weak and Statically typed: C Weak and Dynamically typed: PHP, Perl, Javascript
There's roughly 150K lines of C++ for the game engine, and another 25K for editing tools. Gameplay scripting uses JavaScript. We build on top of low-level libraries (OpenGL, OpenAL, ENet,...), not an existing game engine (like OGRE).
Have you read the article? The reason they did this had nothing to do with lack of proper skills; it was to reduce licensing costs by moving to an open source stack. In fact, they deliberately chose to do a 1-to-1 conversion, instead of rebuilding the system:
- to keep the cobol-developers on-board, who know not just how the software works, but also why it does what it does
- to prevent the project from becoming a big-bang-lets-fix-everything-project, doomed to fail, and instead stay focused on the savings it should bring
- to be able to fully automate it, including all tests
I was skeptic when I read the summary, but from the presentation it looks like they handled it very well, and are now in a very good position to continue the improvements they started.
In the case of Oracle, you have a company that makes an obscenely bloated, broken, overpriced software package that has caused havoc and pain across the continent.
Fixed that for ya
Re:Java is safe, mysql is safe...
on
Oracle Buys Sun
·
· Score: 1
Java is far from safe. The language will continue to exist, but the platform will most likely stop developing. Oracle has never shown commitment to Open Source, has never shown commitment to any non-Java JVM languages, etcetera. Java's future is insecure at best.
Don't blame management. If you were asked to make a kid's toy, would you ask 'do you want it the safe way, which will cost an extra $5 per unit, or do you want the cheap way?'. You are a professional, it is your job to produce software that meets professional standards. If others screw up, fine, but don't deliver an unsafe product just because nobody told you to make it safe.
GP is incorrect, parent understands the broken window fallacy correctly. The point of the broken window fallacy is that what seems like a loss for the economy (less $$$ made in the software industry/glazier), is in fact a gain for the economy (same useful effect (software vs window), $$$ spend somewhere else).
Slashdot Mirror
Not at all. Perl6 is not an upgrade of Perl5, which is still being actively developed. Perl6 is a brand new language in the same family.
Then why name it Perl6?
If it's a different language, give it a different name!
Many programmers don't understand that concept:
* Code tells you 'how'
* Comments tell you 'why'
I have found this to be _especially_ important for bug-fixes. Very important to document why things were done a certain way to minimize implicit side effects.
Yes.
These can be comments in code, but SVN (or any SCM) commit comments are also extremely useful for this.
Now your brain can catch a virus just by reading!!!1
Nothing new there... check The Catcher in the Rye
ClearView doesn't have to prove that a program is either correct or incorrect. It only has to detect certain types of bugs, and fix them. There is no guarantee your program is correct after running it.
And personally I can't think of any cases where a buffer overflow is part of a correct program...
I'm still wondering what happened to General Protection Fault.
Is he retired? Missing In Action?
So you're saying the bug report is useless without a testcase?
You don't need fraud to lie using statistics!
#1 is better for both, because #1 pays the bills. Developers that waste their time on features nobody uses should be removed from the industry. They should talk to users, and find out why users like #1 better.
I'm amazed you can ship a million lines with only two bugs (found that is) when you misspell "have" as "ahve" three times in a single post.
So you can imagine how many bugs have been caught by his unit tests before shipping.
No unit tests for Slashdot posts though...
Actually it costs tens of dollars to produce per item (I read in my local newspaper), much more than the cost of the magazine, and probably more then the advertiser paid for it. But it will only be available in a couple of thousand magazines, so the total cost is likely a couple of hundred thousand dollars.
And now think of the advertising value. In my local newspaper, on slashdot, ....
Way higher than you could hope to get spending that much on a traditional advertisement.
Yes, big difference; all combinations are possible:
Strong and Statically typed: Scala, Java, C++
Strong and Dynamically typed: Python, Ruby
Weak and Statically typed: C
Weak and Dynamically typed: PHP, Perl, Javascript
To add to that, I've seen books about sex for sale, and sex is occasionally free.
as in beer or as in speech?
TFA says they didn't
There's roughly 150K lines of C++ for the game engine, and another 25K for editing tools. Gameplay scripting uses JavaScript. We build on top of low-level libraries (OpenGL, OpenAL, ENet, ...), not an existing game engine (like OGRE).
Have you read the article? The reason they did this had nothing to do with lack of proper skills; it was to reduce licensing costs by moving to an open source stack. In fact, they deliberately chose to do a 1-to-1 conversion, instead of rebuilding the system:
- to keep the cobol-developers on-board, who know not just how the software works, but also why it does what it does
- to prevent the project from becoming a big-bang-lets-fix-everything-project, doomed to fail, and instead stay focused on the savings it should bring
- to be able to fully automate it, including all tests
I was skeptic when I read the summary, but from the presentation it looks like they handled it very well, and are now in a very good position to continue the improvements they started.
The 20 to 30 apps you'll be breaking are not MS apps, but are (usually misbehaving) third party apps. Read the SimCity example from Joel.
It will be a long time before Wine will have this level of compatibility.
I have never paid Sun a penny for support. Their kit is reliable.
I'm beginning to see Oracle's business case
Wait... So all this GPL-stuff is because Stallman couldn't print his TPS reports?
In the case of Oracle, you have a company that makes an obscenely bloated, broken, overpriced software package that has caused havoc and pain across the continent.
Fixed that for ya
Java is far from safe. The language will continue to exist, but the platform will most likely stop developing. Oracle has never shown commitment to Open Source, has never shown commitment to any non-Java JVM languages, etcetera. Java's future is insecure at best.
Yeah, but if you try Chuck Norris, Chuck Norris will iterate you!
I can think of one who can be included on both lists.
Don't blame management. If you were asked to make a kid's toy, would you ask 'do you want it the safe way, which will cost an extra $5 per unit, or do you want the cheap way?'.
You are a professional, it is your job to produce software that meets professional standards. If others screw up, fine, but don't deliver an unsafe product just because nobody told you to make it safe.
Wait... now you are making it sound like it went through the same lifecycle as Java...
What's next? Legitimate uses for VisualBasic??
Here I was happily typing along, suddenly my keyboard stops working: slashdotted!! Thanks a lot ThousandStars!
GP is incorrect, parent understands the broken window fallacy correctly. The point of the broken window fallacy is that what seems like a loss for the economy (less $$$ made in the software industry/glazier), is in fact a gain for the economy (same useful effect (software vs window), $$$ spend somewhere else).