my quick take on AOP and Java: it better be done inside the language or it should be done with scripting language. Lisp (CLOS) had it obviously. AspectJ people decided that Java's too weak for this stuff and proceeded to build their own language, its compiler and development environment. This is nice but for me at least the barrier to entry is too high. Even if I have to type a bit more, I'd rather do AOP in Java. This way I can still rely on all the infrastructure I already have: compiler (jikes), IDE, debugger, deployment knowhow, etc. Another option is doing it with something like Javascript or others that can bind Java effortlessly.

If I were to start another AOP, I'd consider JavaAssist. Beautiful papers by its author are very underrated. JAC is an AOP that builds on AOP but quite complicated (but one of their papers on categories of AOP techniques are very nice).

[Note to self: I've known of JavaAssist for almost a year and what the hell have I done so far? Depressing.]

12:10:34 PM  #  

The object may be weirder than it appears.

Well, well, the Rational story is getting interesting. According to this story, Microsoft is also bidding on Rational. That's interesting. Well, one of the two will end up supporting the overblown, heavyweight cruft that is RUP, and the other will have another chance to look at the Agile side of things. Should be interesting either way, I think. [Cincom Smalltalk Blog] I figured Rational built XDE IDE based on Eclipse because it got scared by Microsoft's acquisition of Visio. Visio is Rose done in 'worse is better' way. (Well, not that Rose is good in any sense!) [Jay's Scrapbook]

I'd give rational more credit: a) They may have used eclipse because they recognized a need to have a better technical foundation for their product; b) they wanted to be more appealing to IBM; c) they recognized that they need to become more agil and saw eclipse as a step in that direction (it is); d) they relized that there was a market for a common tool set for dot net and j2ee deveopment in large organizations. e) a+b+c+d.

I'm amazed that there was not more Slashdot interest in the Togethersoft connection. As half-troll pointed out, Borland just agreed to buy Togethersoft. Togethersoft Control Center offer support for multi-language, model driven development -- many Java developers prefer it to the WebGain and/or Rational tool set. Of couse, Together Control Center addresses problems not normally encountered by the slashdoters such as deploying to multiple J2EE servers, object modeling, complex documentation that is generated from code, etc.

Why does IBM want Rational? Because Rational provides a story, toolset, and customer base that needs both dot net and J2ee solutions. It moves IBM further into the MS turf and heads off at the pass a clear danger: MS owning Rational with the implict entry into more of the IBM enterprise level accounts.

Why would MS want Borland? To gain a tool set that has Java legitimacy and (perhaps) the powerful j2EE tools of TogetherSoft.

It may or may not be significant that TogetherSoft will release a version based on WebSphereStudio 5.0, which is the IBM product based upon the open source eclipse project.

One thing to consider: neither IBM nor MS are the companies are as inflexible as many of their detractors. MS is setting itself up to support development in multiple languages for a reason. IBM is setting itself up to play on the MS desktop for a reason.

[Contours]

Emphasis added. The last paragraph deserves careful examination.

6:38:06 AM  #