Crispin wrote:
Sorry David, but I have to disagree with you :-)

Of course without a good understanding of the generated code, trying to fix problems in the code is going to be a nightmare.

Sure, but you certainly SHOULD NOT be modifying the generated code. You
SHOULD BE going back to the tool and resolving the bug at the higher level
generators afford you.
And it seems to work pretty well, actually. Actually, the small amount of debugging I've needed to do was resolved with writing to STDOUT.

And that's why we're arguing about which technology is better to get a
business application to the Web, rather than getting it there. I've used
generators for almost 20 years. I write WinC/Java/5250/HTML clients. I write
JDBC/ODBC/SQL Server/DB2 backends. I put the business logic where it makes
sense. I can change where each piece goes on a whim.

I don't care that I use a tool. I use the tool to get the job done. I cared
when I first looked at generated code 18 years ago, because I was an RPG
coder, and I wanted to keep my job as a programmer. I see too many people
get defensive when it comes to something else writing the code for them. I
think these people need to get over it.

Just My Opinion :-)
I hate badly written code that I can do myself easier and/or more quickly. However, with EGL it does far more than I can do by myself by hand. I am the ultimate make vs. buy guy, and yet even I have to admit that the tool does it better. I wish people would try it for themselves.

And when I get time, I will try to create some videos or some such silliness to show people just how easy it is. But really, just download the tool and go through the tutorial.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.