Ask YC: Are there *any* startups using ASP.NET?

"According to the author of the book Core JSF, JSF offers a means for Java to compete with ASP.NET/Visual Studio in the area of Rapid application development (RAD). The addition of the Sun Java Studio Creator IDE provides a RAD environment similar to Visual Studio 2005, potentially lowering development cost and other barriers to entry."

So basically the world of J2EE pre-JSF is worse than ASP.NET and with JSF, J2EE is catching up with ASP.NET stack.

System.out.println("Hi, I'm a Java library function for Java being called in Java");

Java The Language and C# are extremely similar, and if the differences bother you that much you can use J#. Java and .NET both provide managed runtime environments. Java and .NET both provide a large library of functions for that environment.

I'd say if you're going to put Java and .NET into different categories, you should have some solid reasons, so let's hear them.

.NET has stronger patterns throughout the system, you basically learn one set of patterns and it works on everything. most developers support all of the patterns.

.NET has superior thread and memory management. in most tests i have seen, .NET code runs faster with less memory bulk and with better memory access models for most object calls.

.NET remoting is built in, while with Java you need external 3rd party Apps.

Visual Studio Blows Eclipse out of the water. I have yet to see a feature in Eclipse that was not first deployed in Visual Studio.

Visual Studio Team Edition, better supports 100,000 lines of code or more in revision control than any other platform, while remaining agile.

Microsoft has a long term support option if you plan to actually scale your product, Java on the other hand requires you to base your support options on the user community.

If you want to get access to the hardware layer for graphics, or communication, you can use the same tool set vertical, as you can to develop the rest of your code. With Java, if you want to do hardware, you need to break out of your development tools and use different ones.

.NET/ Visual Studio has framework language packages for C#, Visual Basic, Python, PHP, Ruby, C, C++, J#, JavaScript, -and if we wanted to, we could write a framework package for ActionScript3 (yes we have considered it)

We love the .NET platform, but what we do not like is the server licensing fee. at $1000 a software license, we would rather amortize that cost based on uptime like a service, so that we could deploy an image on any number of computers, and pay for what we use. I have raised this concern with MS and how they do not fit well with EC2. For now we feel that MS will move along with their Novell relationship and Mono will become an extension platform for MS developers, with a service contract only.

In Linux Piping is really fast, but in Windows, Piping is slow.

I really like being able to code C++ and C# in the same solution, but in different projects, while being able to step through all layers of the code.

Remote Debuging, and RPC calls are way better in .NET

Also if you are doing XML, and Web Service calls (soap, get, post) .NET includes the functional layering and interface segmentation to access each of the protocols independently or together.

In my opinion, if you want to set up some sort of transactional API, .NET has leaps and bounds better performance and professionals level tools.

If you are trying to hack something together, .NET has a large learning curve, and requires disciplined programing to get any practical use out of it.