Re: Apache and .Net

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Richard Schoen wrote:
> Kind of like smokin that Wacky Weed called EGL :-)
>   
Hey, I didn't bring up EGL.  Even though it's faster, easier, uses 
industry standards and generates applications that run on multiple 
platforms, I wasn't comparing it to your Rube Goldberg ".Net plus some 
plug-in that makes it run on Apache" stuff.  I was just pointing out 
that mod_aspnet is a Windows lock-in, and sort of defeats the purpose of 
using Apache.

Of course, the same thing could be said about .Net in general :)

> mod_aspnet works fine. It basically just plumbs the standard MS .Net
> calls through to Apache. Even works with the 3.5 Framework. 
>
> mod_mono is really for if you're not targeting Windows machines and
> since I was talkin Windows and I have successfully used mod_aspnet for
> over two years, you can use it too :-)
>   
If you're going to lock yourself into Windows, then just use IIS.  It 
may be a security sieve, but at least it's supported by Microsoft. I'm a 
little unsure about running mission critical systems on a plug-in from a 
single vendor, no matter whether they call it "open source" or not.

> Don't let Joe scare you away from .Net. 
>
> He just wants you to use IBM's new flavor of the day.  
>   
I love the characterization crowd <smirk>.  EGL no more the "flavor of 
the day" than XP or Vista.  EGL is the culmination of nearly 30 years of 
cross-product development.  However, unlike Windows, EGL relies on open 
standards.  The generated applications can run anywhere you have a JVM.

But I'm not suggesting EGL here.  EGL is really more for people who want 
to get applications written quickly without having to worry about the 
underlying technologies.  Dave is much farther down the technology stack 
than most i shops.  He wants something that will work with an i that's 
been turned into a database server, and so needs external technologies.  
EGL is for people who aren't technology-driven.

Even so, though, EGL would work for him.  Because it has integrated SQL 
support built right into the language, an easy way to discover the 
existing schemas and build complex queries from them, and a powerful 
drag-and-drop UI builder that would allow him to create entire 
applications in minutes.

Not only that, he could then review the generated JSF code and use that 
as a quick way to come up to speed on JSF, which is the industry 
standard for Java-based user interfaces.  In fact, if he decided to take 
the leap into Java and forego EGL entirely at some point down the road, 
he would be able to leverage all the experience he'd gained working with 
EGL.

So maybe I am suggesting EGL <grin>.

Joe