[pjmlp]

Again, that culture was already there decades before Java came to be, COM, SOM, CORBA, Taligent, ER model, Booch method, Rational Unified Process, Structured systems analysis and design method. Yes, I am an old dog at this game.

Had Ruby and Rails been embraced at the same scale, you can bet there would exist a comparable flavour of Ruby EE.

[revskill]

As i said, it's about the mindset that matters (rather than throwing me a bunch of design patterns).

If you're at work and want to get shit done fast for the salary reason: There's no reason NOT to use Rails.

If you want to go enterprise, use something lightweight and modular, composable instead. Throwing a bunch of inheritable BeanClass serves no purpose on the job.

UNIX philosophy came long ago, before JAVA.

[pjmlp]

UNIX philosophy is cargo cult from a book worshiped by FOSS folks.

CORBA was born on UNIX, original implementation targeted C, C++ and Smalltalk.

Java was years away to be created, again by a UNIX company.

Java EE, was reborn from an canceled Objective-C project created by Sun and NeXTSTEP, again two UNIX companies.

[revskill]

No, unix philosophy is what make things work together as i see. A big mess of inheritance tree doesn't solve large scale problem. That's the misunderstanding of "large scale engineering" that i've seen from most companies.

You don't solve problem by solving it. You solve it by decomposing it, and compose again.

[pjmlp]

The technical architects, solution architects and business analysists couldn't care less about what a worshiped book says about the UNIX philosophy.

On the enterprise mines, the minions do what they say.