> What do you mean by shallow support?

There's a good deal of Java that simply can't be used directly from within
CF. A lack of support for null values is a big reason. There's also a good
deal that requires workarounds or hacks. It's certainly possible to use a
lot of Java from within CF, but it requires 1) knowing a second language and
2) knowing Java well enough to be able to workaround the implementation
details.

In contrast, Visual Basic, Jscript and C# are all first class .Net
languages. This means that they can treat anything in the .Net Framework as
a native object (with a few exceptions). So, a VB programmer doesn't have to
learn a new language to implement something in the .Net Framework.

> Honestly I almost never used Java in
> CF since CF has almost everything I ever needed.

I agree for the most part. I can program most Web sites completely in
ColdFusion, and in most cases that is perfectly reasonable. However, for
example, there are many times where it would be preferable to use a data
type other than a struct or an array. I can now create my own data types
using CFCs, but that's not nearly as nice as having every common (and some
not so common) data types pre-built for me.

My point isn't that I can't do most of what I need to in ColdFusion. It's
just that the old arguments no longer apply. It used to be the case that
ColdFusion offered an environment that was much richer than other competing
platforms such as ASP. I do not believe this to be the case anymore.

I believe ColdFusion is on par with most other platforms and that it offers
most of the functionality that I need to develop most Web applications
without resorting to coding COM objects or Java classes, or purchasing third
party components.

As a side note, the biggest notable exception from my perspective is image
manipulation. I'd love some native image tags. I'm hoping that the jimg tag
off the resource kit makes it into the next release of ColdFusion.

> Once should also look at
>  what is needed, not what can be done. Sure C#.Net offers a lot, but you
> only really need a fraction of that for the web.

I only need a fraction for any given Web site, yes. However, I need
different pieces for different Web sites. In some Web sites, image
manipulation is a big deal. In others, COM interoperability is important.

-ben
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to