|
Interesting. In my experience, an essential part of any project is creating the database. In fact, design issues dictated several features of the database layout (especially the logging!). Heck, the SQL people say you can just add columns and such on the fly, it's no problem! :)Well, we created everything from scratch. Why shouldn't you? <grin>Since your "challenge" was to see how much time it takes to implement functionality in technology X, not how much time it takes to build something from zero, it would not be unreasonable to provide the data you have for the thing to reimplement.
I'm tired of listening to everyone say how good (TECHNOLOGY X) is. Time to prove it. It's easy to sit on a mailing list and pontificate. It's a lot harder to really do something.Oh, the RSDC is the application we are discussing. Thought it was some kind of Rational Super Duper Checkmark thing we had to use.
Personally I do not say that EGL is better or worse than anything else, I just say that _I_ am very careful of meta-languages since the additional translation step may be extremely hard to debug. Just look at how long it took before JSP's were debuggable - that was painful.EGL is debuggable both at the EGL level and the generated code level (Java or JavaScript). It's really quite powerful.
I would love to see the Ruby on Rails people take a stab at this.
As an Amazon Associate we earn from qualifying purchases.
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.