Re: bosses who want to research .NET alternatives
Re: bosses who want to research .NET alternatives
- Subject: Re: bosses who want to research .NET alternatives
- From: "Ricardo Cortes" <email@hidden>
- Date: Tue, 17 May 2005 15:38:48 -0400
- Organization: Bolt
And I'm sure there are people that would argue the same about Apple ;)
.NET is a viable solution for many reasons but the major competing
factor is that they have a toolset that aids development and deployment
from beginning to end. This is what's missing from the J2EE world.
Getting a solid J2EE project going these days with the latest *hot*
technologies requires one to learn Struts+Tiles or Spring, Hibernate,
Ant, Eclipse Plugins or IntelliJ, servlet/JSP specification, JSTL,
JUnit, JProbe, JBoss, JMX and MBeans, yadda, badda, cadda. You name it.
I failed to mention WebObjects because the enterprise is just not using
WebObjects. On Wall Street it's either .NET or J2EE and those that are
using J2EE aren't exactly floating on Cloud 9 because it's a pain in the
ass to get anything done. Getting rid of EJBs and replacing them with
Hibernate was a big help but Hibernate still has it's issues (i.e. Lazy
Instantiation exceptions in comparison to EOF's fault-firing mechanism).
I think the biggest shift in mindset might very well be Tapestry, with
or without Cayenne. Afterall, the creator, Howard Ship, was a
WebObjects fan. Sun did an amazing job marketing J2EE but I think they
failed to do it at the right time because the product wasn't ripe
enough. Now things are getting ripe but .NET stepped in and has offered
an end-to-end solution that's appealing to mucky mucky project managers
because the tools are integrated and there are numerous offerings for
languages (C# ain't all the different from Java, except for check
exceptions). It's just plain hard to compete with that.
On Tue, 2005-05-17 at 10:14 -0700, email@hidden wrote:
> On May 17, 2005, at 9:40 AM, Ted Thibodeau Jr wrote:
>
> > The .NET CLR is bound to MS Windows, but producing a .NET assembly
> > (if done according to the ECMA standard) leaves you free to use any
> > CLR (Common Language Runtime), including .NET and Mono.
>
> True, but there is still the issue of Microsoft holding patents which
> could be used to cripple Mono. I did a quick Google search for the
> current state of things and it looks like for now M$ has granted them
> the right to use the patented concepts, but there's no guarantee that
> will hold in the future. Many people seem to think that if Mono
> actually takes off, M$ will step in and cut them off at the knees.
>
> All of this could turn out to be anti-Microsoft FUD, but personally I
> would not want to put myself in a position of having my project even
> potentially depend on a M$ product.
>
> Just my $0.02,
>
> janine
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden