Name: Anonymous 2009-05-18 2:39
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.
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.