It was... well it was as bad as 2
3 could have been good, but it failed in lousy writing not on the actors.
The funny thing is, that the Highlander series with Adrian Paul is really good. I cannot understand why the writers did an amazing job on the series and then fail constantly on good story arcs with lousy writing in the movies or on both.
Adrian Paul did a good job in the series, Christoph Lamberds Qualities are non discussable, but yet, Highlander2 was one of the worst sequels every, highlander 3 even worse.
Highlander Endgame could have been good, good beginning of the story arc, but then failed totally in the second part despite the actors best efforts.
I think whoever is responsible for those movies, should kick the movie authors and hire the ones from the TV series.
Hilander2, probably the worst sequel of all times. Superman 4 was a total crap but at least it kept a story within the realm of Superman stories, it was just that the story was not a Dark Knight Returns quality but from the lowest drawers of usual Superman comic book stuff.
(Superman defeats a supervillain created by Lex Luthor)
Check outExade for jsf development much better in this regard than MyEclipse.
As for ejb3, it is very close to Hibernate but more cleaned up and really good.
There already is a good tool which covers the ORM part of EJB3 (the BO part is equally stunningly good) it is called jsr200 an you can download it from the Eclipse site.
You forgot to mention one thing, there is a maximum heap size, every java program has to adhere to, it is depending on the VM between 32 and 64MB, and you can adjust it with the -Xmx param.
It is true, the heap never shrinks but in reality it also does not grow!
Actually natively compiled languages in the server sides case are not really that much faster, but you are around 10 times as fast in development times as you would be in C++, besides that you get stuff like clustering scaling up to mainfraime level, clustered caches, excellent orm mappers etc... out of the box. There is a reason why Java is used heavily on the server side nowadays, it is scalability, fast development times, stability, and huge excellent libraries for everything under the sun.
The most hilarious case of this extension I have seen so far is to sell prozac now as a helper drug for menstrual syndroms, a usage which is highly questionable and given the withdrawal I have had on anti depressents, even the argument you do not get dependend on them is a blank lie, you get withdrawals as sort of depression backslashes which ease once the drug has left the body entirely, so where is the no dependency issue there!
In Europe we probably have equally many laywers as AUZ but, the distribution of wealth among laywers is more vertical, many do not live by doing lawsuits but other legal stuff. Also this gold rush mentality does not work really out here (some try from time to time, patents and a broken trademark system in germany enforce it)
there is no high profile lawsuite where a laywer an suck millions out of someone.
Laywers can make good money, the average does not earm much more or less than the average techie.
And yes the lawsuit costs are overe here also much less than in the USA regarding the health system. The main problem the health system has are the high medication costs, which are caused by a broken frivolous patent system
If the bird flue really becomes a pandemic, we could face the first mass killing in the west caused by the patent system, if there is a medication and laws and patents prevent a mass production.
Could happen if things become severe that country by country in a state of emergency they will kick the patent system out for production but then probably it is too late.
Patent mass killings have occured en masse already, AIDS medication for instance, also the whole interferon issue caused by BTG...
Dream on, given MySQLs track record, they can be happy if that thing works at all over a realy business situation.
And opensource killing oracle, dream on, you already know how hard it is to switch operating systems, believe me, moving 20 years of legacy data stored procs etc... from a stable work horse to something like MySQL, no sane DB admin would even think of that, remotely making a plan.
Once you have set for a DB moving away makes no sense anymore, and Oracle knows that, hence, they have a foothold in the ORM market which basically abstracts DBs, and also did a really good job as co specificators for the EJB3 entity bean layer (the other co specs came from Gavin King who did Hibernate) and have no problem with it.
The deal comes probably from another side, they do not want to get MySQL to become too cozy with SAP and basically to sum it up, they have them at their balls.
Why should IBM do that, all they could gain is the MySQL AB brand?
Fact is, MySQL is merely a parser and a rather basic repository on top of added semi fitting third party repos...
Ibm just donated a full featured entry level embeddable db to the opensource community, I see no reason for that move.
If IBM wanted something stable they probably would be better off to make an entry level version of DB2 or fork away postgresql or firebird, which are less hodj podj systems but DB systems grown from ground up with no external core contributions,
Wont help too much, but I rather doubht it, I think the buyout was done due to the MySQL SAP connections.
It is rather unlikely that Oracle customers move to PostgreSQL, and even more unlikely is a move to MySQL (besides the constant hype that MySQL finally is enterprise ready, it is not, it simply has the basic features you really need not to hose your data at all after a while)
I have seen enough DB installations, that I know that a move from one DB to another is not really something feasable normally, once you have set for a DB you usually stay there, because it is very cost intensive even with ORM data abstraction etc... to move away from it. Hence Oracle still has Toplink in their program and did not shut it down and never did anything about other ORM mappers in fact they were one of the key companies behind the really good EJB3 orm specification. They are well aware that they do not loose customers by specifying a good DB abstraction layer.
From this angle I also think they see the whole Postgresql issue, it is a no brainer for them, no real lost Customers, they already have all the big ones which roll in the Cash, and they currently move towards app servers, development solutions and CRM systems as extensions to their core business.
The whole MySQL issue, probably would give them just a hammer which they can draw if MySQL becomes to nasty from the SAP side of things.
I rather doubt any community would arise after the downfall of MySQLAB people simply would start to look for alternatives, that could give Firebird the well deserved push and also PostgreSQL would get another boost, after the obvious one it has gotten since 8.0.
Actually most people who need a solid but free db engine do, but they do not constantly brag about, how this db will take over oracle or that the db is enterprise ready, while having a db which hoses itself constantly under heavy load.
The most hyped one os probably the better description, before MySQL, during MySQLs absolute heydey and even today, better OSS dbs exist with more features which do not carry the hidden 500 USD pricetag.
But none of them have MySQLs hype engine behind it, they have one advantage though, they work!
Most developer from time to time enjoy smaller applications, less responsibility testing ground, trying out new stuff and libs, and often you simply have to do it because you have this urge to eat sometimes!
Depending on what you describe average, the average projects I personally have to live with (have to live because I can see the mistakes every day) probably would be better off with a clean JSF frontend, seam and ejb3 for the middle tier (I am talking about EJB3 which is close to excellent not the absymality 1 and 2 were).
RoR would not be applicapble there, first of all, legacy data, secondly, the usualy project management problems of having some excellent people and some average, with db schema changes sometimes til often, and given RoRs nature having such a hen house in front of RoR would result in desaster.
On the other hand once a team is really tight and good to average quality you can push out amazing stuff in RoR, I have seen it.
Actually many web developers keep a constant eye on rails, I am heavy into J2EE and like it, especially the stuff which is coming along Seam, Spring, JSF and EJB3, but almost every one I know who works in the domain, keeps an eye on rails as a fallback option for quick small webapps.
Besides that many concepts and libaries currently are heavily evaluated for inclusion into other frameworks.
Actually no, Rails has heavily inspired many developments in many languages over the last year.
Pretty much every framework currently at least is looking at the stuff the rails guys are doing and whether some of the concepts are viable.
Stuff like Seam which also is excellent is heavily inspired by the ease of use metaphor of Rails, and the Prototype javascript libary used by rails currently sort of becomes a defacto standard for more advanced javascript stuff with many projects building on top of it.
Rails definitely does not scale into the average J2EE project dimensions, but it has its merits and definitely made huge inroads in the web development domain over the last year.
Not really that correct, Fact is Lotus did not the needed info to make 123 work on Windows in time, while Microsoft relied on internal undocumented code to have Excel ready for Windows 3.0 (which was the cornerpoint where Microsoft took over the app market as well, before they were only niche players just being the market leader in dos and basic)
All that stuff is documented very well in the book undocumented windows, at least it was in its first incarnation.
And to my knowledge there was a lawsuit regarding this which just ended this year with a loss by Microsoft and a payment to Lotus.
Slashdot Mirror
It was... well it was as bad as 2 3 could have been good, but it failed in lousy writing not on the actors. The funny thing is, that the Highlander series with Adrian Paul is really good. I cannot understand why the writers did an amazing job on the series and then fail constantly on good story arcs with lousy writing in the movies or on both. Adrian Paul did a good job in the series, Christoph Lamberds Qualities are non discussable, but yet, Highlander2 was one of the worst sequels every, highlander 3 even worse. Highlander Endgame could have been good, good beginning of the story arc, but then failed totally in the second part despite the actors best efforts. I think whoever is responsible for those movies, should kick the movie authors and hire the ones from the TV series.
Hilander2, probably the worst sequel of all times. Superman 4 was a total crap but at least it kept a story within the realm of Superman stories, it was just that the story was not a Dark Knight Returns quality but from the lowest drawers of usual Superman comic book stuff. (Superman defeats a supervillain created by Lex Luthor)
Well the UI is nice but rather minimalistic, even NeXT has moved on, they have taken over Apple :-)
Is to bleed the RIAA and others dry by boykotting their products...
Check outExade for jsf development much better in this regard than MyEclipse. As for ejb3, it is very close to Hibernate but more cleaned up and really good. There already is a good tool which covers the ORM part of EJB3 (the BO part is equally stunningly good) it is called jsr200 an you can download it from the Eclipse site.
You forgot to mention one thing, there is a maximum heap size, every java program has to adhere to, it is depending on the VM between 32 and 64MB, and you can adjust it with the -Xmx param. It is true, the heap never shrinks but in reality it also does not grow!
Actually natively compiled languages in the server sides case are not really that much faster, but you are around 10 times as fast in development times as you would be in C++, besides that you get stuff like clustering scaling up to mainfraime level, clustered caches, excellent orm mappers etc... out of the box. There is a reason why Java is used heavily on the server side nowadays, it is scalability, fast development times, stability, and huge excellent libraries for everything under the sun.
Well it was called summer of code, not summer of greed or lawsuits ;-)
american students were all too busy becoming laywers or business crooks.
Actually L4, QNX, WindowsNT3.5 and other operating systems basically show that Microkernels both can be stable and very performant.
The most hilarious case of this extension I have seen so far is to sell prozac now as a helper drug for menstrual syndroms, a usage which is highly questionable and given the withdrawal I have had on anti depressents, even the argument you do not get dependend on them is a blank lie, you get withdrawals as sort of depression backslashes which ease once the drug has left the body entirely, so where is the no dependency issue there!
I agree with Bill Gates.. whats next? Gnu Hurd 1.0?
In Europe we probably have equally many laywers as AUZ but, the distribution of wealth among laywers is more vertical, many do not live by doing lawsuits but other legal stuff. Also this gold rush mentality does not work really out here (some try from time to time, patents and a broken trademark system in germany enforce it) there is no high profile lawsuite where a laywer an suck millions out of someone. Laywers can make good money, the average does not earm much more or less than the average techie. And yes the lawsuit costs are overe here also much less than in the USA regarding the health system. The main problem the health system has are the high medication costs, which are caused by a broken frivolous patent system
If the bird flue really becomes a pandemic, we could face the first mass killing in the west caused by the patent system, if there is a medication and laws and patents prevent a mass production. Could happen if things become severe that country by country in a state of emergency they will kick the patent system out for production but then probably it is too late.
Patent mass killings have occured en masse already, AIDS medication for instance, also the whole interferon issue caused by BTG...
Dream on, given MySQLs track record, they can be happy if that thing works at all over a realy business situation. And opensource killing oracle, dream on, you already know how hard it is to switch operating systems, believe me, moving 20 years of legacy data stored procs etc... from a stable work horse to something like MySQL, no sane DB admin would even think of that, remotely making a plan. Once you have set for a DB moving away makes no sense anymore, and Oracle knows that, hence, they have a foothold in the ORM market which basically abstracts DBs, and also did a really good job as co specificators for the EJB3 entity bean layer (the other co specs came from Gavin King who did Hibernate) and have no problem with it.
The deal comes probably from another side, they do not want to get MySQL to become too cozy with SAP and basically to sum it up, they have them at their balls.
Why should IBM do that, all they could gain is the MySQL AB brand? Fact is, MySQL is merely a parser and a rather basic repository on top of added semi fitting third party repos... Ibm just donated a full featured entry level embeddable db to the opensource community, I see no reason for that move. If IBM wanted something stable they probably would be better off to make an entry level version of DB2 or fork away postgresql or firebird, which are less hodj podj systems but DB systems grown from ground up with no external core contributions,
Wont help too much, but I rather doubht it, I think the buyout was done due to the MySQL SAP connections. It is rather unlikely that Oracle customers move to PostgreSQL, and even more unlikely is a move to MySQL (besides the constant hype that MySQL finally is enterprise ready, it is not, it simply has the basic features you really need not to hose your data at all after a while) I have seen enough DB installations, that I know that a move from one DB to another is not really something feasable normally, once you have set for a DB you usually stay there, because it is very cost intensive even with ORM data abstraction etc... to move away from it. Hence Oracle still has Toplink in their program and did not shut it down and never did anything about other ORM mappers in fact they were one of the key companies behind the really good EJB3 orm specification. They are well aware that they do not loose customers by specifying a good DB abstraction layer. From this angle I also think they see the whole Postgresql issue, it is a no brainer for them, no real lost Customers, they already have all the big ones which roll in the Cash, and they currently move towards app servers, development solutions and CRM systems as extensions to their core business. The whole MySQL issue, probably would give them just a hammer which they can draw if MySQL becomes to nasty from the SAP side of things.
I rather doubt any community would arise after the downfall of MySQLAB people simply would start to look for alternatives, that could give Firebird the well deserved push and also PostgreSQL would get another boost, after the obvious one it has gotten since 8.0.
The entrance door of the Eclipse foundation has been smashed with a chair recently...
Actually most people who need a solid but free db engine do, but they do not constantly brag about, how this db will take over oracle or that the db is enterprise ready, while having a db which hoses itself constantly under heavy load.
The most hyped one os probably the better description, before MySQL, during MySQLs absolute heydey and even today, better OSS dbs exist with more features which do not carry the hidden 500 USD pricetag. But none of them have MySQLs hype engine behind it, they have one advantage though, they work!
Most developer from time to time enjoy smaller applications, less responsibility testing ground, trying out new stuff and libs, and often you simply have to do it because you have this urge to eat sometimes!
Depending on what you describe average, the average projects I personally have to live with (have to live because I can see the mistakes every day) probably would be better off with a clean JSF frontend, seam and ejb3 for the middle tier (I am talking about EJB3 which is close to excellent not the absymality 1 and 2 were). RoR would not be applicapble there, first of all, legacy data, secondly, the usualy project management problems of having some excellent people and some average, with db schema changes sometimes til often, and given RoRs nature having such a hen house in front of RoR would result in desaster. On the other hand once a team is really tight and good to average quality you can push out amazing stuff in RoR, I have seen it.
Actually many web developers keep a constant eye on rails, I am heavy into J2EE and like it, especially the stuff which is coming along Seam, Spring, JSF and EJB3, but almost every one I know who works in the domain, keeps an eye on rails as a fallback option for quick small webapps. Besides that many concepts and libaries currently are heavily evaluated for inclusion into other frameworks.
Actually no, Rails has heavily inspired many developments in many languages over the last year. Pretty much every framework currently at least is looking at the stuff the rails guys are doing and whether some of the concepts are viable. Stuff like Seam which also is excellent is heavily inspired by the ease of use metaphor of Rails, and the Prototype javascript libary used by rails currently sort of becomes a defacto standard for more advanced javascript stuff with many projects building on top of it. Rails definitely does not scale into the average J2EE project dimensions, but it has its merits and definitely made huge inroads in the web development domain over the last year.
Not really that correct, Fact is Lotus did not the needed info to make 123 work on Windows in time, while Microsoft relied on internal undocumented code to have Excel ready for Windows 3.0 (which was the cornerpoint where Microsoft took over the app market as well, before they were only niche players just being the market leader in dos and basic) All that stuff is documented very well in the book undocumented windows, at least it was in its first incarnation. And to my knowledge there was a lawsuit regarding this which just ended this year with a loss by Microsoft and a payment to Lotus.
Java seems to be fast enough, because stuff like ebay, www.weather.com, walmart.com etc... all run on java, and they do that happily.