The conspiracy minded might wonder if Sun sees Java -- not Linux -- as the most important part of the Java Desktop System. As long as people are migrating away from Windows, why not sell them an OS where Java is the preferred system programming language?
I put Smalltalk in there for exactly that reason. It's not clear why it wouldn't be considered a scripting language by many popular definitions of the term.
Personally, I don't worry about it much. It's pretty easy to find the language bigots and then to ignore them.
It might be easier to group languages based on a dynamic versus static scale. Perl, Python, PHP, Ruby, Tcl, most shells, and Smalltalk allow run-time code evaluation, late binding, and rather less compile-time type checking. They also tend to prefer a unified compile-and-run step.
That's still not perfect set, but it's more accurate than "programming" versus "scripting".
The language, the libraries, or the platform? There's J2SE, J2EE, J2ME, Blackdown, Kaffe, Classpath, the AOP thing, the Pizza project that preceded Java 1.5's generics, IBM's JDK, HP's JDK, GCJ....
It takes time and planning to put a product into stores. You have to convince buyers to buy it before it's available and you have to get it to them in time. You also need to coordinate your advertising (and your finite budget) with the product's availability, or you risk too many returns. Missing the window of opportunity with Wal-Mart will likely kill your game.
There are also business considerations of when to show revenue, but I take that to show the problem with publicly-held game publishers.
If I find that the design of my program creates significant problems down the line, I will not kludge something into place. I will redesign the program.
Do you find this at odds with the rule about freezing the design before you start coding? If you find a flaw in the design, will you only implement the redesign in the next version?
Good point inheritance and class hierarchies must serve some psychological need among OO professors and authors. They're certainly not the end goal of good design.
Since you bring up Smalltalk, you might like Traits in Smalltalk, research on alternate mechanisms of polymorphism, behavior, and code reuse.
You failed to quote the third sentence of the PostgreSQL gotchas page:
This is work-in-progress; a few more gotchas will follow as time allows.
Use what you like, but comparing a list of twenty gotchas to a page clearly labeled "not finished yet" seems a little bit unfair. (Your claim that "professional" companies only use statically typed languages also seems rather unfounded.)
I browsed the TMDA FAQ and couldn't find the question "Did you realize that it's possible and probable that a spammer or virus has spoofed the sender's e-mail address?" Seems to me that TMDA might be part of the problem, not part of the solution.
nVidia can not release their drivers as open source due to the licensing for the AGP interface code in their drivers-pure plain and simple.
It's been four years since NVIDIA released beta drivers. If they'd wanted, they likely could have produced their own AGP code in that time. One of their product managers hinted they'd be releasing open source 2D drivers several years ago too.
Slashdot Mirror
Unless you mean "platform-specific modules in the Win32:: namespace", you're off-base. It's the same source code as all the other platforms.
If everything interesting lives one layer above the OS, it may not matter which OS it is.
The conspiracy minded might wonder if Sun sees Java -- not Linux -- as the most important part of the Java Desktop System. As long as people are migrating away from Windows, why not sell them an OS where Java is the preferred system programming language?
The license does not apply to the copyright holder, who can do anything he wants.
I put Smalltalk in there for exactly that reason. It's not clear why it wouldn't be considered a scripting language by many popular definitions of the term.
Personally, I don't worry about it much. It's pretty easy to find the language bigots and then to ignore them.
It might be easier to group languages based on a dynamic versus static scale. Perl, Python, PHP, Ruby, Tcl, most shells, and Smalltalk allow run-time code evaluation, late binding, and rather less compile-time type checking. They also tend to prefer a unified compile-and-run step.
That's still not perfect set, but it's more accurate than "programming" versus "scripting".
Just a nit on Subversion's status: it's in beta now, with a release candidate scheduled for tomorrow and the official 1.0 release set for Monday.
The term "scripting language" is nearly meaningless, but it certainly does not preclude a JIT or a sophisticated virtual machine.
The language, the libraries, or the platform? There's J2SE, J2EE, J2ME, Blackdown, Kaffe, Classpath, the AOP thing, the Pizza project that preceded Java 1.5's generics, IBM's JDK, HP's JDK, GCJ....
Read any "blogs" lately?
Just look at voter turnout rates in the past several decades: so far, so good.
(My inner historian also wants to point out that the two major parties in the U.S. right haven't been around since 1787, so there's hope for change.)
It takes time and planning to put a product into stores. You have to convince buyers to buy it before it's available and you have to get it to them in time. You also need to coordinate your advertising (and your finite budget) with the product's availability, or you risk too many returns. Missing the window of opportunity with Wal-Mart will likely kill your game.
There are also business considerations of when to show revenue, but I take that to show the problem with publicly-held game publishers.
Do you find this at odds with the rule about freezing the design before you start coding? If you find a flaw in the design, will you only implement the redesign in the next version?
Good point inheritance and class hierarchies must serve some psychological need among OO professors and authors. They're certainly not the end goal of good design.
Since you bring up Smalltalk, you might like Traits in Smalltalk, research on alternate mechanisms of polymorphism, behavior, and code reuse.
Why not fix the scheduling problems while you're at it?
Actually, he wrote the article.
I thought my amplifier was cool for going up to 11, but it can't compete with a piano that goes up to W!
You failed to quote the third sentence of the PostgreSQL gotchas page:
Use what you like, but comparing a list of twenty gotchas to a page clearly labeled "not finished yet" seems a little bit unfair. (Your claim that "professional" companies only use statically typed languages also seems rather unfounded.)
That rather is the point of anti-trust law.
Actually, several projects use test-driven design. It's popular in the Perl and Ruby communities, and projects like Subversion and Neon do it too.
I browsed the TMDA FAQ and couldn't find the question "Did you realize that it's possible and probable that a spammer or virus has spoofed the sender's e-mail address?" Seems to me that TMDA might be part of the problem, not part of the solution.
It's been four years since NVIDIA released beta drivers. If they'd wanted, they likely could have produced their own AGP code in that time. One of their product managers hinted they'd be releasing open source 2D drivers several years ago too.
Add use diagnostics; during development, and you may be able to skip the Camel step in many cases.
Whose fault could that be?
Next time, use some discipline
I suggest Test::More
(Maybe the hyperlink is cheating.)