Post #279,456
3/24/07 11:46:03 PM
|
Rails is OK
but compare to Seaside it just seems so last-century.
I4 NOW!
Impeach, Indict, Incarcerate, Inject
Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice
|
Post #279,457
3/24/07 11:49:48 PM
|
Uh, yeah.
Actually, it has a few real problems as opposed to just not being fashionable.
No Unicode, for one thing. And Rails strikes me as yet another "get the simple stuff done whiz bango, but fall apart for hard stuff" framework.
Regards,
-scott anderson
"Welcome to Rivendell, Mr. Anderson..."
|
Post #279,464
3/25/07 2:33:56 AM
|
I didn't mean fashionable
I meant, unwieldy. I like working on live systems. Live, as in running while I work on it. Live, as in, faults trigger debuggers, archive the execution state such that I can restore the entire program to examine it, and then keep going. Rails is a dead system. You have to kill the program to change it. How quaint.
I4 NOW!
Impeach, Indict, Incarcerate, Inject
Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice
|
Post #279,496
3/25/07 12:55:37 PM
|
Fashionable == !quaint
You're the one using the words that way, not me. :-)
I've never been one to use debuggers, and a live system isn't worth the hassle of repository-based development. When I do Django development I never have to restart the program either. To each his own.
Regards,
-scott anderson
"Welcome to Rivendell, Mr. Anderson..."
|
Post #279,502
3/25/07 1:17:43 PM
|
I code in the debugger
then execute it, write, step, write, step....
Guarantee's a high level of quality. If I write a line wrong, I just back up the PC to the outer context, change the line, and test it. I recently had to fix a Java web service and felt absolutely crippled because I couldn't write a couple lines for the wacky string manipulation I was about to do - just to make sure I had it right.
This is the way computers should work.
I4 NOW!
Impeach, Indict, Incarcerate, Inject
Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice
|
Post #279,530
3/25/07 8:14:22 PM
|
I prefer to use unit tests to guarantee quality
They're repeatable and useful for regression testing. I don't have to worry about side effects, either.
As far as immediate Java testing, that's what the Bean Shell is for. Or use the remote debugger if you want. Either way.
Again, different strokes.
Regards,
-scott anderson
"Welcome to Rivendell, Mr. Anderson..."
|
Post #279,568
3/26/07 2:04:26 AM
|
I do both
Cool thing about SUnit is you click on failed test - brings it up in a debugger - step, analyze, and fix.
I4 NOW!
Impeach, Indict, Incarcerate, Inject
Bush, Cheney, Gonzalez, Rumsfeld, Rove, Rice
|
