That to my knowledge is one part of the workplace desktop..
The desktop more or less is an eclipse based universal application shell it even has an office integration.
I saw the thing during a presentation at IBM a while ago, cool stuff.
Java Studio Creator 2 is your friend...
Exactly what you are looking for, and it is free.
Re:Now, if he could apply the same wisdom to SQL,
on
Exploring Active Record
·
· Score: 2, Interesting
Well KODO is considered to be the best persistence layer for java around, I am glad that Bea decided to opensource the KODO EJB3/JPA layer under an Apache license.
And I agree Hibernate is subotimal, there are issues with performance in certain areas, there are issues with mass data, and the whole many to many handly in combination with some of the Hibernate core people (not Gavin King he always is nice) in the JBoss forums gives it the rest. I cannot await to move away from Hibernate towards EJB3 JPA based on Kodo.
You bring up a point here with using something else, until recently Hibernate was the only OSS based implementation of an ORM system usable and coming close to being a standard and having good tools, now that JPA is out, we have finally a good number of them all based on JPA:
Hibernate, KODO JPA, Toplink JPA all OSS based on various licenses. Due to the issues mentioned I will probably move away from Hibernate towards something else.
The main problem with Kodo simply used to be the price which was way too high for small developments, and still is if you need KODO JDA, but the JPA implementations are there now or will be there soon and usuable for a budget.
Well the JPA simplifies to a big degree the mapping
instead of having a class and a xml descriptor describing every field you normally have
@Entity
public class Table {
@Id Integer id;....
so things have become easier, but there are certain limitations of course
you have the java inherent setters and getters, which blow up your code (although the usually are generated, no one normally codes them by hand
something like a query over a method is not possible you still have to go over the persistence api
the apis persist, lock, save, update hell was carried over straight from hibernate, but persist and merge ease things to a certain degree, thank god.
In the end rails has caused a lot of momentum im the java world, there are several interesting projects going on, Seam, Trains, FacesFreeway, they all try to follow the rails approach of trying to simplyfy as much as possible.
And thank god Struts is out of the game in all these approaches due to the fact that scaffolding needs a component tree!
Well lets say it that way, I have been using hibernate for quite a while and it has a lots of quirks, the most annoying aspects of it, for many is:
a) many to many mappings which simply need more documentation, the best way to do is is to enforce surrogates on the many to many tables otherwise you will often run into implicit clashes via compound keying (rails already enforces it, hibernate does not, it is not documented but after many hours of trying to fix this problem on a compound key I came to the conclusion there is no sane other way to handle it)
b) The whole locking, merge save, update, persist api is a huge mess, which was carried over to a big degree into the whole jpa, partially also caused by a huge lack of documentation in exactly this critical area. (90% of all problems regarding saving usually circle around the lock persistence functions and many to many resolution)
Having to juggle with lazy non lazy objects, with merge, save, update, lock, persist wich all do almost the same but not exactly the same, with referencing issues on many to many relationships etc... Is nothing I would call a walk in the park either.
I was at a conference a while ago where one of the people hosting the conferences said, that one thing many frameworks simply have lost is the KISS principle, and the guy clearly said, the perfect example is Hibernate where someone has to be an expert in it to be able to handle it.
And Hibernate is considered to be the one of the easier ones in the java world.
And no this guy knew what he was talking about, I have used hibernate very often and I agree with him.
JPA, Hibernate etc... are very powerful apis, but they are way to complex for a RAD approach and they all have huge areas where they need to be cleaned up instead of being carried over to the next API. The biggest one of them IMHO are the areas mentioned.
Well rails is a very good framework + toolset, but like every other enforcing toolset which tries to cover a lot of ground by automating stuff it has a huge problem, follow the road and you are set, if you cannot follow the road you are screwed.
That is pretty much the problem with all toolsets which give you a lot of expert automation.
A perfect example for this in the java world is maven, an excellent tool, but even the maven documentation says, use the structures provided by maven otherwise you will have a rough ride.
In the end you always will have to make a decision between verbosity (which general solutions usually have and only can be covered to some degree by a language for framework) and automatisation which means enforcing a certain road to follow and if you find out that the road does not work for you once the application is finished to 70% you really have a problem on your hands.
And thus a framework like Rails, or Seam, Trails or Seaside you name it, always has to be cleanly evaluated if you can apply it, there is no hammer for all, and things which might work for small stuff might become desastrous once things become bigger, customer demands rise and the team becomes bigger.
Actually a good idea, there are 300 million people from the indian middle class which probably could do the job better and for a fraction of the costs, of GW;-)
Webworks is one of the myriads of opensource web frameworks, it is merging currently with struts, to Struts Ti (one of the handful of Struts successors)
Dont know if it offers any significant benefits over the others, I rather doubt it and it was before the merger more or less pretty unknown even in the Java webdev crowd. But face it the old Struts codebase was so much behind anything remotely sane that there was no other way to get the old framework into newer waters than merge it.
Actually I agree with your comment on Struts, Struts is one of the huge jokes of history, why it ever became a defacto standard is beyound me, even the core struts developers have moved onto saner grounds (Struts shale, which basically is a JSF extension framework)
But fact is it is used and it works, although no one likes it, including me.
Actually Prototype.js is inherently problematic it does language and namespace hijacking, as good as the work is which is based upon it (namely script.aculo.us) as weak is the foundation of prototype.js.
And no prototype is not a framework which is widely used among corporations and big sites and never will be, it is a javascript framework and not even a very good one (dojo for instance is way better in the way it tries to be non intrusive and tries to cover more ground)
and the frameworks mentioned are very popular, they are just java centric thus unknown to people outside of the java world, and all of them mentioned have a high usage rate in corporate banking etc... environments and generally are very popular. (Way more popular than prototype.js, which in the long run if they designers do not change their namespace problems will be a dying framework)
No, but the business model of MySQL AB goes down the drain, and given the fact that MySQL is more or less just a query engine on top of a handful of third party repos, I wish them good luck if oracle decides to close their future developments.
What does MySQL have now?
They have a query engine, one of the worst there is.
Two GPL repos which still can be relicensed for their business model, but if oracle says no one day, bad luck.
What can they do,
a) Either try to merge the SAP codebase in (good luck with that)
b) Merge the Postgresql Repo in, but why use MySQL at all
c) Merge the firebird Repo in, but why use MySQL at all
both Postgresql and Firebird are superior to MySQL especially on the query engine and repo side of things.
Those small businesses have to move on, there are better alternatives. MySQL had the hype, but the others the better and freer prodduct.
It is not like people can move on to Firebird or PostgreSQL!
Good luck with buying out PostgreSQL, that is close to impossible. It only worked for MySQL because
a) The entire thing is GPLed with a buyout option
b) MySQL is basically a query engine on a number of third party repos which had the same licensing issues you can find in a) (and not even a good one)
c) The entire thing is in and out dominated by a single company wich is living on a) and b)
None of these issues are relevsant in PostgreSQL and the license is free enough, that even if all the core devs are hired by Oracle or IBM the product stil can be forked away by anyone without any restrictions whatsoever (that is the reason why Apache BSD and other BSDish licenses are more welcome in libraries and servers than the GPL)
Firebird could become a target (but the codebase is lean enough that anyone could fork it again) but with Postgres, forget it, besides the license to many already are involved which are not buyable by a single entity.
Sorry guys, but given the fact that MySQL always was inferior to its alternatives and did cost more than the better opensource alternatives. That the license since version 4 was a tangeling two edged sword over the top of many small devs (who never read the license in happy GPL land) and the shouting for we are enterprise ready while having only arrived at a stage where most of the others were in the mid nineties. If you are burned by this now (MySQL IMHO is a victim in the ongoing battle between SAP and Oracle), you and no one else is to blame for this now.
I until now cannot understand why someone should shell out money for MySQL while other alternatives which are better come for free in non binding licenses.
(sorry but there are only GPL exceptions in the MySQL license for certain OSS programs and languages)
My guess is it must be the hype.
Prototype has some serious issues, it messes around with basic javascript datastructures, has no namespaces, reserves often used names and keywords $ for instance for itself
Many people switched from prototype to dojo exactly for those reasons.
Speed becomes lousier than in most other db systems once you move away from I read a single table without transactions situation.
Easy to administer, yes, but the others have caught up, pgAdmin3 is a very good tool as well.
Enterprise features, which ones, hosing the repo at serious loads (MySQL is known for that)
Postgres is known for its stability.
Do a join over 8 transactional tables some of them huge in MySQL and come back talking about speed and enterprise features, this is a typical situation where you need something more decent where MySQL simply falls flat on its face!
I banned Symanted from my machine after they pushed a 5 mb atguard to a 60mb monster with almost no extra functionality within a year, all due to the fact that the clean streamlined interface was exchanged with a bloated buggy full of picutes disneyesk interface...
All I can say is if you are looking for a change, dont wait for Symantec.
Xaml... typical Microsoft not invented here syndrome...
instead of going with xul, they forked xul and svg away altered parts of it and tied it to windows, so that the rest of the world has to clean up their mess again.
Well by using it you are screwed, does that count?
Re:More than two options...
on
JSF vs ASP.net
·
· Score: 1
Actually maintainability in teams is a huge problems in dynamic languages like PHP or ruby, you have to do excessive Unit testing to keep everything in place.
These languages definitely have a team scaling problem, add to that in PHP at least the most popular version (4) no namespacing no separation of code concerns via mvc and you are in for a scaling desaster.
PHP is fine for small projects but it does not scale for real world enterprise requirements.
Both PHP, Rails etc... have their place but there are places where you better not use them as a tool. And those places are where J2EE todays is used most often.
Things are moving fast in the apache world, actually the controls are not very buggy anymore (You probably checked then out a while ago). Much has been done in the last year.
for a good demo check this:
site out.
Slashdot Mirror
sorry here is the link http://www.mathcaddy.com/windowsxpbootsonamac!!!!1 /
This link has the proof
That to my knowledge is one part of the workplace desktop.. The desktop more or less is an eclipse based universal application shell it even has an office integration. I saw the thing during a presentation at IBM a while ago, cool stuff.
Java Studio Creator 2 is your friend... Exactly what you are looking for, and it is free.
Well KODO is considered to be the best persistence layer for java around, I am glad that Bea decided to opensource the KODO EJB3/JPA layer under an Apache license. And I agree Hibernate is subotimal, there are issues with performance in certain areas, there are issues with mass data, and the whole many to many handly in combination with some of the Hibernate core people (not Gavin King he always is nice) in the JBoss forums gives it the rest. I cannot await to move away from Hibernate towards EJB3 JPA based on Kodo.
You bring up a point here with using something else, until recently Hibernate was the only OSS based implementation of an ORM system usable and coming close to being a standard and having good tools, now that JPA is out, we have finally a good number of them all based on JPA:
Hibernate, KODO JPA, Toplink JPA all OSS based on various licenses. Due to the issues mentioned I will probably move away from Hibernate towards something else.
The main problem with Kodo simply used to be the price which was way too high for small developments, and still is if you need KODO JDA, but the JPA implementations are there now or will be there soon and usuable for a budget.
you have the java inherent setters and getters, which blow up your code (although the usually are generated, no one normally codes them by hand
something like a query over a method is not possible you still have to go over the persistence api
the apis persist, lock, save, update hell was carried over straight from hibernate, but persist and merge ease things to a certain degree, thank god.
In the end rails has caused a lot of momentum im the java world, there are several interesting projects going on, Seam, Trains, FacesFreeway, they all try to follow the rails approach of trying to simplyfy as much as possible. And thank god Struts is out of the game in all these approaches due to the fact that scaffolding needs a component tree!
Well lets say it that way, I have been using hibernate for quite a while and it has a lots of quirks, the most annoying aspects of it, for many is: a) many to many mappings which simply need more documentation, the best way to do is is to enforce surrogates on the many to many tables otherwise you will often run into implicit clashes via compound keying (rails already enforces it, hibernate does not, it is not documented but after many hours of trying to fix this problem on a compound key I came to the conclusion there is no sane other way to handle it)
b) The whole locking, merge save, update, persist api is a huge mess, which was carried over to a big degree into the whole jpa, partially also caused by a huge lack of documentation in exactly this critical area. (90% of all problems regarding saving usually circle around the lock persistence functions and many to many resolution)
Having to juggle with lazy non lazy objects, with merge, save, update, lock, persist wich all do almost the same but not exactly the same, with referencing issues on many to many relationships etc... Is nothing I would call a walk in the park either.
I was at a conference a while ago where one of the people hosting the conferences said, that one thing many frameworks simply have lost is the KISS principle, and the guy clearly said, the perfect example is Hibernate where someone has to be an expert in it to be able to handle it. And Hibernate is considered to be the one of the easier ones in the java world. And no this guy knew what he was talking about, I have used hibernate very often and I agree with him.
JPA, Hibernate etc... are very powerful apis, but they are way to complex for a RAD approach and they all have huge areas where they need to be cleaned up instead of being carried over to the next API. The biggest one of them IMHO are the areas mentioned.
Well rails is a very good framework + toolset, but like every other enforcing toolset which tries to cover a lot of ground by automating stuff it has a huge problem, follow the road and you are set, if you cannot follow the road you are screwed. That is pretty much the problem with all toolsets which give you a lot of expert automation. A perfect example for this in the java world is maven, an excellent tool, but even the maven documentation says, use the structures provided by maven otherwise you will have a rough ride. In the end you always will have to make a decision between verbosity (which general solutions usually have and only can be covered to some degree by a language for framework) and automatisation which means enforcing a certain road to follow and if you find out that the road does not work for you once the application is finished to 70% you really have a problem on your hands. And thus a framework like Rails, or Seam, Trails or Seaside you name it, always has to be cleanly evaluated if you can apply it, there is no hammer for all, and things which might work for small stuff might become desastrous once things become bigger, customer demands rise and the team becomes bigger.
something like Seam? took me around 20 lines of application code to develop a simple blogger with master detail view...
Actually a good idea, there are 300 million people from the indian middle class which probably could do the job better and for a fraction of the costs, of GW ;-)
In case of the mac mini yes... it is just at that pricepoint.
Webworks is one of the myriads of opensource web frameworks, it is merging currently with struts, to Struts Ti (one of the handful of Struts successors) Dont know if it offers any significant benefits over the others, I rather doubt it and it was before the merger more or less pretty unknown even in the Java webdev crowd. But face it the old Struts codebase was so much behind anything remotely sane that there was no other way to get the old framework into newer waters than merge it.
Actually I agree with your comment on Struts, Struts is one of the huge jokes of history, why it ever became a defacto standard is beyound me, even the core struts developers have moved onto saner grounds (Struts shale, which basically is a JSF extension framework) But fact is it is used and it works, although no one likes it, including me.
Actually Prototype.js is inherently problematic it does language and namespace hijacking, as good as the work is which is based upon it (namely script.aculo.us) as weak is the foundation of prototype.js.
And no prototype is not a framework which is widely used among corporations and big sites and never will be, it is a javascript framework and not even a very good one (dojo for instance is way better in the way it tries to be non intrusive and tries to cover more ground)
and the frameworks mentioned are very popular, they are just java centric thus unknown to people outside of the java world, and all of them mentioned have a high usage rate in corporate banking etc... environments and generally are very popular.
(Way more popular than prototype.js, which in the long run if they designers do not change their namespace problems will be a dying framework)
No, but the business model of MySQL AB goes down the drain, and given the fact that MySQL is more or less just a query engine on top of a handful of third party repos, I wish them good luck if oracle decides to close their future developments. What does MySQL have now? They have a query engine, one of the worst there is. Two GPL repos which still can be relicensed for their business model, but if oracle says no one day, bad luck. What can they do, a) Either try to merge the SAP codebase in (good luck with that) b) Merge the Postgresql Repo in, but why use MySQL at all c) Merge the firebird Repo in, but why use MySQL at all both Postgresql and Firebird are superior to MySQL especially on the query engine and repo side of things.
Those small businesses have to move on, there are better alternatives. MySQL had the hype, but the others the better and freer prodduct. It is not like people can move on to Firebird or PostgreSQL! Good luck with buying out PostgreSQL, that is close to impossible. It only worked for MySQL because a) The entire thing is GPLed with a buyout option b) MySQL is basically a query engine on a number of third party repos which had the same licensing issues you can find in a) (and not even a good one) c) The entire thing is in and out dominated by a single company wich is living on a) and b) None of these issues are relevsant in PostgreSQL and the license is free enough, that even if all the core devs are hired by Oracle or IBM the product stil can be forked away by anyone without any restrictions whatsoever (that is the reason why Apache BSD and other BSDish licenses are more welcome in libraries and servers than the GPL) Firebird could become a target (but the codebase is lean enough that anyone could fork it again) but with Postgres, forget it, besides the license to many already are involved which are not buyable by a single entity. Sorry guys, but given the fact that MySQL always was inferior to its alternatives and did cost more than the better opensource alternatives. That the license since version 4 was a tangeling two edged sword over the top of many small devs (who never read the license in happy GPL land) and the shouting for we are enterprise ready while having only arrived at a stage where most of the others were in the mid nineties. If you are burned by this now (MySQL IMHO is a victim in the ongoing battle between SAP and Oracle), you and no one else is to blame for this now. I until now cannot understand why someone should shell out money for MySQL while other alternatives which are better come for free in non binding licenses. (sorry but there are only GPL exceptions in the MySQL license for certain OSS programs and languages) My guess is it must be the hype.
Prototype has some serious issues, it messes around with basic javascript datastructures, has no namespaces, reserves often used names and keywords $ for instance for itself Many people switched from prototype to dojo exactly for those reasons.
There still is firebird and postgres, but integrating their repos would mean to lose the face for MySQLAB...
Speed becomes lousier than in most other db systems once you move away from I read a single table without transactions situation. Easy to administer, yes, but the others have caught up, pgAdmin3 is a very good tool as well. Enterprise features, which ones, hosing the repo at serious loads (MySQL is known for that) Postgres is known for its stability. Do a join over 8 transactional tables some of them huge in MySQL and come back talking about speed and enterprise features, this is a typical situation where you need something more decent where MySQL simply falls flat on its face!
I banned Symanted from my machine after they pushed a 5 mb atguard to a 60mb monster with almost no extra functionality within a year, all due to the fact that the clean streamlined interface was exchanged with a bloated buggy full of picutes disneyesk interface... All I can say is if you are looking for a change, dont wait for Symantec.
Xaml... typical Microsoft not invented here syndrome... instead of going with xul, they forked xul and svg away altered parts of it and tied it to windows, so that the rest of the world has to clean up their mess again.
Well by using it you are screwed, does that count?
Actually maintainability in teams is a huge problems in dynamic languages like PHP or ruby, you have to do excessive Unit testing to keep everything in place. These languages definitely have a team scaling problem, add to that in PHP at least the most popular version (4) no namespacing no separation of code concerns via mvc and you are in for a scaling desaster. PHP is fine for small projects but it does not scale for real world enterprise requirements. Both PHP, Rails etc... have their place but there are places where you better not use them as a tool. And those places are where J2EE todays is used most often.
Things are moving fast in the apache world, actually the controls are not very buggy anymore (You probably checked then out a while ago). Much has been done in the last year. for a good demo check this: site out.