Just look at http://www.sco.com/. Right now it is:
===
Welcome to Your New Home in Cyberspace!
This is a placeholder page installed by the Debian release of the Apache Web server package, because no home page was installed on this host. You may want to replace this as soon as possible with your own web pages, of course....
===
ROTFL:)
SQL in presentation layer (JSP, ASP, PHP, whatever) is EVIL!
Yes, it allows to write something fast, but maintainance will be a nightmare. SQL should be moved to another layer and wrapped in some sort of DAOs (Data Access Objects).
There are tools in Java which can do data binding for you - look at Hibernate (www.hibernate.org), so you won't need SQL at all!
I knew you will say this:)
I'm using gSOAP since for one year. And it's far from 'decent' SOAP implementation: it's impossible to dynamicaly call functions, gSOAP supports STL only partially (there's no way to generate STL-aware source from WSDL), memory management in gSOAP is a nightmare, etc.
1. It is more concise - java even _less_ compact than C++ with a good set of libraries - whereas PHP has loads of very forgiving high-level functions builtin.
Yes, Java code takes more space than C++ or PHP. But modern IDEs allows you to generate 30%-50% of this code! And Java libraries are FAR superior to C++ ones (try to find decent open source SOAP toolkit for C++:) ).
2. It is more lightwight - java is just _still_ too bloated and slow even after all these years of promises from Sun.
Java code runs faster than PHP. Period. Try simple benchmarks if you don't believe it.
3. The Java VM's for Linux really suck, they 'officially support' only RedHat and are unstable as hell running on Debian.
Are you still using JRE 1.1_04? Wakeup, JVMs are enterprise-ready on Linux for two or three years by now.
That said I really miss the J2EE ability to cache persistent data between requests in memory simply by declaring a variable as static. It's the only feature I miss in PHP.
Have you ever read books with such names as "Design Patterns" or "Thinking in Java"? Using static variables in servlets to cache data is an example of wrong design (there are some exceptions, though).
.NET has COM+ for backend systems, Java has EJB, but PHP has nothing:(
I can't use distributed transactions, transparent failover, declarative security and transaction demarcation in PHP.
Slashdot Mirror
Look, for example at MSDN: Layered windows
Well, this patent clearly has LOTS of prior art.
Well, it's possible.... in Russia. Statisctics for Lib.ru :
:)
On 1 Oct 2003 library contains 4000Mb in 21200 text items.
Most of Lib.ru is in Russian (of course!), but it contains some English-translated texts: Russian prose and science fiction in English translation Envy
5:00 AM? Seems like 17:00 in my timezone...
Is this the begining of: 1. _E_mbrace 2. _E_xtend 3. _E_xtinguish strategy? There's my tinfoil hat....
Just look at http://www.sco.com/. Right now it is: === Welcome to Your New Home in Cyberspace! This is a placeholder page installed by the Debian release of the Apache Web server package, because no home page was installed on this host. You may want to replace this as soon as possible with your own web pages, of course.... === ROTFL :)
JCP is slow as a turtle. Some JSR are being developed for SIX years ("Adding Generics to Java Language" comes to mind).
Russia - $3.00 :)
Well, maybe they SHOULD navigation systems too?
Well we really made such cooling system for ZX-Spectrum computer back in good old Soviet Russia days (1988, If I recall correctly).
No, just second :)
..goes here..
In Russia (not Soviet Russia :) ) Win Longhorn is sold in every software shopside with WinXP (for $3), Adobe Photoshop ($3) and Half Life II ($6).
SQL in presentation layer (JSP, ASP, PHP, whatever) is EVIL! Yes, it allows to write something fast, but maintainance will be a nightmare. SQL should be moved to another layer and wrapped in some sort of DAOs (Data Access Objects). There are tools in Java which can do data binding for you - look at Hibernate (www.hibernate.org), so you won't need SQL at all!
I knew you will say this :)
I'm using gSOAP since for one year. And it's far from 'decent' SOAP implementation: it's impossible to dynamicaly call functions, gSOAP supports STL only partially (there's no way to generate STL-aware source from WSDL), memory management in gSOAP is a nightmare, etc.
.NET has COM+ for backend systems, Java has EJB, but PHP has nothing :(
I can't use distributed transactions, transparent failover, declarative security and transaction demarcation in PHP.
"A novice programmer thinks kilobyte contains 1000 bytes, an experienced one thinks kilometer contains 1024 meters" :)