They will after they get fired. Once all the manufacturing and r&d know how is elsewhere management is just a dead shell. Plus in China the government owns the banks.
Napoleon III remodeled Paris at vast expense to stop the constant worker rebellions. Then his incessant infatuation with warfare ignited the Franco-Prussian war when he decided to invade Belgium. France had to pay heavy war reparations after it lost that war with Germany. So it comes as little surprise their economy stagnated then.
Computationally intensive tasks have always been crap in Java. Non unsigned types, no support for fast floating point types, no vector instruction support, etc. I believe the DoD and DARPA even funded Sun Microsystems to extend Java for such applications once and they ended up developing a whole *new* language that went nowhere instead.
Just don't use EJBs if you can avoid it. Which you usually can except for client 'requirements' which don't have even the slightest resemblance with reality.
Java is ok. Just use Servlets, POJOs, XML-RPC or JSON, and whatever.
That is because to justify the expense of being a large project they needlessly complicate the architecture of the program. Then it gets delayed and buggy like heck. Fact: 90% the things done with EJBs don't need them at all.
I think France did ok. They had a lot of social and economic issues and experienced a lot of revolts from the XVIIIth to the XIXth century. Plus they had the continental powers to deal with. Unlike the UK they couldn't just hunker down and rely on the Navy to defend their nation. They have always had to split their resources more towards land armies than the UK.
I mean Ampére? French. Sabatier? French. Pasteur? French. They didn't do THAT bad in technological development.
MOC sucks period. You can implement all of those paradigms in C++ without the use of a pre-compiler. I mean GTK+ does it in C so you surely can do it in C++. And it doesn't take forever to compile code with it.
As for ANSI Common LISP I haven't programmed it in yonks and the reasons are usually the same. Generally shitty compilers which produce slow native code, bad GCs, fragmented support for ANSI Common LISP features, poor interfacing with C system libraries, etc.
C++ has RTTI typeid and dynamic_cast. People usually deride MOC not only because it makes compilation loads slower but because Qt's signal and slots mechanism sucks. I personally think it is WORSE than the GTK+ signal mechanism. GTK+ doesn't need a pre-compiler either.
The license issues were bad enough at one point that the KDE developers themselves started developing their own OSS version of Qt called Harmony. After Trolltech made the license more open Harmony folded.
Qt is LGPL now. It used to have the Q Public License, then GPL, now LGPL. They switched to GPL after they saw MySQL managed to retain profit with a GPL license and they switched to LGPL after the Nokia aquisition AFAIK.
It is a hack because it does nothing useful that you could not do with later versions of ANSI C++. For whatever reason Trolltech decided they couldn't trust ANSI C++ compilers to be present on the system.
Until it was LGPLed it was problematic to use it as a system library. It would mean many commercial programs would have to pay Trolltech just to have a GUI which is not something you see in other development platforms. They only did that after they were bought by Nokia AFAIK. They would have little business otherwise.
Slashdot Mirror
They will after they get fired. Once all the manufacturing and r&d know how is elsewhere management is just a dead shell. Plus in China the government owns the banks.
The US has 10 million in prison. So what? Its a matter of percentages.
I have always found that weird considering Larry hates Microsoft more than anything.
Napoleon III remodeled Paris at vast expense to stop the constant worker rebellions. Then his incessant infatuation with warfare ignited the Franco-Prussian war when he decided to invade Belgium. France had to pay heavy war reparations after it lost that war with Germany. So it comes as little surprise their economy stagnated then.
Computationally intensive tasks have always been crap in Java. Non unsigned types, no support for fast floating point types, no vector instruction support, etc. I believe the DoD and DARPA even funded Sun Microsystems to extend Java for such applications once and they ended up developing a whole *new* language that went nowhere instead.
Just don't use EJBs if you can avoid it. Which you usually can except for client 'requirements' which don't have even the slightest resemblance with reality.
Java is ok. Just use Servlets, POJOs, XML-RPC or JSON, and whatever.
Same goes for Hibernate and similar crap.
That is because to justify the expense of being a large project they needlessly complicate the architecture of the program. Then it gets delayed and buggy like heck. Fact: 90% the things done with EJBs don't need them at all.
You can use XML-RPC or whatever. Data storage is not explicit. It is just for RPC. But who cares.
Nah. Ellison is holding him in his secret private Hawaiian island lair.
I think France did ok. They had a lot of social and economic issues and experienced a lot of revolts from the XVIIIth to the XIXth century. Plus they had the continental powers to deal with. Unlike the UK they couldn't just hunker down and rely on the Navy to defend their nation. They have always had to split their resources more towards land armies than the UK.
I mean Ampére? French. Sabatier? French. Pasteur? French. They didn't do THAT bad in technological development.
No, population growth increases economic growth as well. As production is defined by the number of workers x tool efficiency.
SSA can use registers. In fact it usually does use registers.
Remember the scuba mask from the James Bond movie Thunderball? Sure it still needed O2 tanks but it was positively tiny.
MOC sucks period. You can implement all of those paradigms in C++ without the use of a pre-compiler. I mean GTK+ does it in C so you surely can do it in C++. And it doesn't take forever to compile code with it.
As for ANSI Common LISP I haven't programmed it in yonks and the reasons are usually the same. Generally shitty compilers which produce slow native code, bad GCs, fragmented support for ANSI Common LISP features, poor interfacing with C system libraries, etc.
Boost manages to do signals in C++ without a precompiler as well.
C++ has RTTI typeid and dynamic_cast. People usually deride MOC not only because it makes compilation loads slower but because Qt's signal and slots mechanism sucks. I personally think it is WORSE than the GTK+ signal mechanism. GTK+ doesn't need a pre-compiler either.
The license issues were bad enough at one point that the KDE developers themselves started developing their own OSS version of Qt called Harmony. After Trolltech made the license more open Harmony folded.
Qt is LGPL now. It used to have the Q Public License, then GPL, now LGPL. They switched to GPL after they saw MySQL managed to retain profit with a GPL license and they switched to LGPL after the Nokia aquisition AFAIK.
No. People just used GTK+ because GIMP used it as a toolkit. Eventually someone pushed GNOME around but that was later.
Xaw. That's nasty too.
It is a hack because it does nothing useful that you could not do with later versions of ANSI C++. For whatever reason Trolltech decided they couldn't trust ANSI C++ compilers to be present on the system.
I like GTK+'s way of doing things better than Qts. Qts main advantage is that it is better at cross-platform and supports C++ by default. Little else.
Well GTK+ was better than Motif that's for sure.
Until it was LGPLed it was problematic to use it as a system library. It would mean many commercial programs would have to pay Trolltech just to have a GUI which is not something you see in other development platforms. They only did that after they were bought by Nokia AFAIK. They would have little business otherwise.