On Dec 12, 2005, at 7:49 AM, Leonardo Quijano Vincenzi wrote:
Ah ha! Now we're to the fun stuff.... successful compilation is
a false sense of "correctness". So what if you got your syntax
correct - your program still could have logical flaws.
Does your compiler check that you've got your OGNL expressions
correct? Or if you have a typo even syntactically (not even
logically) will you still get a run-time error? <span
jwcid="@Insert" value="ognl:customer.nmae"/> - client's make the
best testers, that's for sure :)
As a matter of fact, it'd be great if it would!
However it *doesn't*.
Unit tests are for logic, not for simple expressions!
You were speaking of a compiler regarding this though, not a unit
test. So currently you're using Tapestry without compilation OR unit
tests for your fragile expressions in your templates. So you've got
neither. Hmmmm.
So, dynamic languages *do* tend to produce buggy code.
I'll refrain from using the more colorful and expressive word, so
I'll go a more circuitous route and say "you're wrong". Bad
programmers produce buggy code, regardless of the language. The
language itself facilitates expressiveness, which Ruby has covered
nicely. Java does not allow for a DSL to be built on top of it, not
cleanly.
It's just that unorganized coders tend to prefer dynamic languages
because... they give more freedom, from their point of view.
You're digging the whole deeper and deeper for yourself here. I hope
your potential future employers don't find this thread when they
Google you up. Because they'll be hiring you to do RoR ;)
As for freedom, I feel free when I can do a big refactoring in my
app, and have the compiler tell me if I screwed up, *before* I even
need to run the test suite.
Again that is a false sense of security.
(And yes, I do write unit tests. I just don't like writing them
just because my application language is not good enough to check
some things for me)
Oh really?!
I encourage you to check out the unit test facility that comes with
RoR then. Spend a week building a RoR app, not the hyped 10
minutes. Dig in and do some unit tests for the functionality you're
building, testing your actions, your business logic, everything.
Cleanly. This is not even comparable to the best of breed ways of
doing this in any Java application using any of the top frameworks, I
assure you.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
