> My counterpoint is that I think you're exaggerating the difficulty of
> writing ASP.NET code in any generic text editor. It's simply not that
> difficult. I pointed out some tools other than Visual Studio, but I also
> pointed out that the code itself isn't that complex in most cases.
>
It might not be difficult, but it is more time consuming.

> I also think it's a mistake to base your comparison on how easy it is to
> develop without tools. Who cares, really? That's what tools are for! Even
> if
> ASP.NET were as difficult to read as obfuscated Perl, who cares if you can
> generate the code without knowing how it works by just clicking your
> mouse?
> Sure, it might be more difficult to maintain that code, but we're talking
> about "Rapid Application Development", not "Rapid Application
> Maintenance".
> And there's no reason why that code can't be maintained through the same
> tool, either.
>
Even the best tools can't hide the complexity that is required. They can
improve the situation, but they can't win. This is why I still believe CFML
beats ASP.NET even when using VS.NET.

> The feature that makes Visual Studio stand out as an ASP.NET IDE is its
> success at abstracting how web applications work - at a very basic level -
> away from the programmer. That is, you can take someone who's been
> building
> desktop forms-based applications, who has no experience with web
> applications, and put that person in front of Visual Studio and say,
> "build
> me a web app". Visual Studio makes the most out of the (largely illusory)
> event-driven model that ASP.NET allows.
>
That remains to be seen how it will work out long term. In the history of
software development, it is rare of have an abstraction of this nature work
out. A perfect example is remote objects. There have been all kinds of
attempts at making remote object invocation require no knowledge of the fact
that the object itself is remote. However, sometimes you need to know it is
remote and because that has been abstracted away disastrous results follow.

> So, I'm not sure whether a Visual Studio-workalike for CF would make CF
> developers any more efficent than they already are. In addition, I don't
> think it would make them more efficient than ASP.NET developers using the
> same development model, since ASP.NET supports this model while CF
> doesn't.
>
If that is the case then why do CFML developers use tools? I mean if it
can't make them more efficient, then why use them?

-Matt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to