Fuck Java

Just when I thought I was rid of Java, I needed to use a component that is written in Java in an app. The thing is fucking huge, gets updated frequently and uses a dozen other micro-libraries. Re-writing it was not a fucking option. Setting up a Java environment on the server and performing out of process calls and redirecting the output was an option, but not a good one. Maybe like 4 people on this board would understand why.

Thank god I needed to do this in an ASP.Net. I took the jars, recompiled it for the .Net CLR using IKVM.Net and now I have totally in process calls to a native component that I can keep up to date with no effort. Some quick benchmarking revealed it was faster than the Java implementation.

So you can compile Java, PHP, Cold Fusion, Python, Ruby and some 40 other languages/frameworks to native .Net code that will run on Windows and Unix like systems. And write websites using a modern framework that handles shit like MVC without resorting to the ass backward ancient models like embedding code in markup like PHP.

Maybe enterprise isn't such a bad deal.

>>19
Actually, Visual Studio makes GUI-building a real pain. It's best to avoid the Windows Forms designer, which will generate the most shitty code possible and the shittiest layout code possible¹. It will also fuck up at the slightest opportunity, especially when using custom controls, and also delete your event handlers without warning.

¹ Seriously, specifying control X and Y coordinates? What is this, 1995? .NET 2.0 added the Table and Split panels, which make better layout easier, but they're shitty and it's too little too late anyway. Also, Mono's support for those is very spotty.

And then there's WPF/XAML, which is a whole fresh new bloated pile of shit. But a shiny one. A shiny one which Mono don't even have any plans to implement.