poor environments (like some RAD tools) which store source code in binary formats and/or where you would have to trigger exports manually to get to the code could be reasons for not using a repository. those tools must be easy to use, e.g. being integrated with your IDE or you simply would not use them.
_all_ my documents go into Subversion: source code, office documents (text, spreadsheet, presentation), pdf manuals, invoices... easy to back up and keep consistent over all machines.
JBoss will erode away the lower ends of the J2EE spectrum for sure.
That's already happening:
- On development/integration machines. Our development is all done with JBoss. When we ship, we can cross-deploy to the customer's App Server, even to another OS quite seamlessly. Nothing you can do very easily without J2EE. (And you don't _really_ want to code on AIX machines, don't you?)
- In low-cost projects. Non-business-critical applications with no need for huge administration and support. You really need the money for development, then.
Being very sceptical in the first place, JBoss blew me away when I got to know it a few month ago. Really cool stuff. Technically, it plays in the same league like all the commercial ones.
From documentation and support aspects ('support' meaning: calling a hotline, wait one hour, someones coming in, fixing your problem), JBoss is not a good choice. Support through internet forums etc. is quite good, though. But you can pay for documentation from "JBoss - The Company". Anyone ever read one of these? Are they good?
Not true. Java is an Interpreter but also does Runtime-Compilation. So, if you run that loop in Java the JVM may compile your loop at runtime and use CPU-specific optimisation. In fact, it does for 586-type CPUs. Your C code is or is not optimized for that CPU at compile time. If it's not, the Java-loop is faster.
The question behind it is: Is technology and progress good or bad?
If we look back and see how much money North American, European and Russian economy made with selling technology (i.e. weapons) to those 3rd world states becoming the alledged terrorist states of today, blaming Open Source is really a silly point of view. (The only difference: There is nothing to sell here.) Because behind Open Source there is no short-sighted political interest (if any). Behind supporting regimes there is.
Today, certain US politics put the 'Terrorist' label on whatever they like. It's just ridiculous.
USA must overcome their trauma and go back to careful and educated political stategies instead.
And go on developing Open Source with all the other developers round the globe.
Re:Java will stay. WAS:Java is dying
on
The Faded Sun
·
· Score: 1
good to know. too few people out there with biased views. leads to poor IT decisionmaking.
Java will stay. WAS:Java is dying
on
The Faded Sun
·
· Score: 3, Interesting
Looking at the current Java-based code developed since 1995, it can be taken for granted that Java will stay. There are huge investments in running Java applications at banks, insurances, e-business companies (IBM). Just like Cobol, Java will probably loose market share while the C#/.NET environment will rise. That's only fair - now there is a modern alternative besides Java.
And I don't understand why people are always complaining only about runtime performance. Java development speed is fast. Java code is robust. Java libraries are so good they are 1:1 ported to C# (JUnit, log4j). Java IDE's are incredible productive. Java can be used over all tiers (JSP, Servlets, Beans, Enterprise Beans). Even with performance 50% lower than "native" C/C++ code, it probably performs better economically than any other technology.
So, still, Java is the best for mid-sized to large projects (besides C#/.NET).
Slashdot Mirror
poor environments (like some RAD tools) which store source code in binary formats and/or where you would have to trigger exports manually to get to the code could be reasons for not using a repository. those tools must be easy to use, e.g. being integrated with your IDE or you simply would not use them.
_all_ my documents go into Subversion: source code, office documents (text, spreadsheet, presentation), pdf manuals, invoices...
easy to back up and keep consistent over all machines.
> Java is designed to scale well on big programs
Read: "Java's Virtual Machine (JVM) is designed to scale well on big programs"
Why should Solaris be the leading Java OS? Only because Sun delivers both?
Following this logic would impose the question why no IBM OS shows up in the first ranks although they provide a Java implementation as well.
I think this figures more or less represent Java's overall OS-related deployment numbers (on Server machines).
JBoss will erode away the lower ends of the J2EE spectrum for sure.
That's already happening:
- On development/integration machines. Our development is all done with JBoss. When we ship, we can cross-deploy to the customer's App Server, even to another OS quite seamlessly. Nothing you can do very easily without J2EE. (And you don't _really_ want to code on AIX machines, don't you?)
- In low-cost projects. Non-business-critical applications with no need for huge administration and support. You really need the money for development, then.
Being very sceptical in the first place, JBoss blew me away when I got to know it a few month ago. Really cool stuff. Technically, it plays in the same league like all the commercial ones.
From documentation and support aspects ('support' meaning: calling a hotline, wait one hour, someones coming in, fixing your problem), JBoss is not a good choice. Support through internet forums etc. is quite good, though.
But you can pay for documentation from "JBoss - The Company". Anyone ever read one of these? Are they good?
Not true. Java is an Interpreter but also does Runtime-Compilation. So, if you run that loop in Java the JVM may compile your loop at runtime and use CPU-specific optimisation. In fact, it does for 586-type CPUs. Your C code is or is not optimized for that CPU at compile time. If it's not, the Java-loop is faster.
The question behind it is: Is technology and progress good or bad?
If we look back and see how much money North American, European and Russian economy made with selling technology (i.e. weapons) to those 3rd world states becoming the alledged terrorist states of today, blaming Open Source is really a silly point of view. (The only difference: There is nothing to sell here.)
Because behind Open Source there is no short-sighted political interest (if any). Behind supporting regimes there is.
Today, certain US politics put the 'Terrorist' label on whatever they like. It's just ridiculous.
USA must overcome their trauma and go back to careful and educated political stategies instead.
And go on developing Open Source with all the other developers round the globe.
good to know. too few people out there with biased views. leads to poor IT decisionmaking.
Looking at the current Java-based code developed since 1995, it can be taken for granted that Java will stay. There are huge investments in running Java applications at banks, insurances, e-business companies (IBM). Just like Cobol, Java will probably loose market share while the C#/.NET environment will rise. That's only fair - now there is a modern alternative besides Java.
And I don't understand why people are always complaining only about runtime performance. Java development speed is fast. Java code is robust. Java libraries are so good they are 1:1 ported to C# (JUnit, log4j). Java IDE's are incredible productive. Java can be used over all tiers (JSP, Servlets, Beans, Enterprise Beans).
Even with performance 50% lower than "native" C/C++ code, it probably performs better economically than any other technology.
So, still, Java is the best for mid-sized to large projects (besides C#/.NET).