I guess define Enterprise. The OS experience doesn't sound like "Enterprise" to me. Just install the JDK? Most enterprises I worked at, it was more like inst

I guess define Enterprise. The OS experience doesn't sound like "Enterprise" to me. Just install the JDK? Most enterprises I worked at, it was more like install WebSphere and it's clients. I did hardly any of these things and I worked at a Fortune-5 company for close to 10 years on a mix of technologies; java being one. Much of the Java there was of the IBM variety. We had WebSphere and their over priced crap. As an insider, many of the DEVs preferred C#. I think much of this had to do with the better development tooling: Visual Studio vs. IBM's version of Eclipse and its infinite list of bolt on and buggy tools. My last 4-5 years there, just about all new apps. were going to C#/.NET platform. I was an insider in an architect role where one of my responsibilities was sitting on a board that oversaw every app. coming into our data center to make sure it followed best practices from language, tools, and general infrastructure stuff like Oracle vs. MS-SQL, SAN or local disk storage. One of our major areas of problems was JMX Message queues and prioritizing them across load balanced clusters of WebSphere servers. It was extremely clunky where as the .NET had better alternatives. Since we were an Enterprise (Fortune-5) by a reasonable definition, GIT and open source version control wasn't use. We use IBM Synergy which is another mess. My last year working there we actually did a trial using subversion which gained a lot of traction. Another problem for Enterprises is single sign on. Especially when you have tons of vendors who want to vet user credentials against our backends. We looked at SAML, WS-Federation, and how much vendor support there was. Like many others at the time, we came up with a kluge based on shared cookies so both our Java apps and .NET apps could work. Largely these standards are too lose to begin with too. Enterprises with deep pockets are hard to work with if your small OEM who can't afford the same financial commitment. In short, most "Enterprises" have a separate group of people who manage the development environment. You don't typically see DEVs setting these things up. We had standard loads for our developers to install and we had the same for our servers. Yea, there were occasions where we would install more JDKs and JREs to test to see if there was a bug or performance difference in the libraries but for the most part, none of the developers had to really mess with the dev environment or the version control stuff.