Just wanted to post this to say that I'm finished migrating some of my
WebWork actions to JavaScript, and now I don't need to keep casting my
objects to their mix-ins anymore, as I'm using a dynamic-typed language
:)
I like JavaScript a lot, when it comes down to ease of prototyping and ease of
development. My plan is to have 0 lines of business logic in Java, so
expect me to find some dark corners and muddy places soon. You'll see,
as I'll start ranting and cursing at my own ideas if something doesn't
go the way I was expecting...
Oh, and regarding lots of folks who are still debating over why I'm not
just using a defined class hierarchy, polymorphism and everything like
that, the answer is simple: I don't know how my objects are going to
look like at development time - and I need flexibility to change my
object definitions when installing the CMS without modifying code -
well, at least not the 'business' object's code, just some of the
business logic.
Having my business logic in an easier language - JavaScript - also
helps a lot here. You can find a good and cheap web designer that can
crank out JavaScript code pretty easily, but finding a good Java
developer these days in Brazil is definitely a hard task - and they
(should I say we, here?) are pretty expensive professionals if you
compare them to JavaScript developers.
Update:
Got some actions working already. Damn, I should have tried
javascriptin' WebWork earlier. Clean, beautiful code as always, works
like a charm, and it's very very very very very easy to get things
done. Kudos to Rickard, again :)
Previous Topic
