This is exactly the reason Microsoft has a BizSpark™ programme, and Ruby doesn't.
This is exactly the reason Microsoft has a BizSpark™ programme, and Ruby doesn't.
I'm not that worried about the whole thing. I mean, they could have included commercial features at any time, and probably do. This is just a switch.
Suddenly, putting a bit of money in the JVM allows you to go faster. In the beginning, the community will be disciplined about it and make sure that libraries and applications that use these features degrades gracefully, so you can make use of them without getting the commercial JVM. But already here it starts smelling, there are now two target JVMs. Testing just doubled in complexity.
Soon, small, clever libraries that does immensely useful stuff with the new features appear - like what Google Collections did for generics - and pretty soon you're wilfully handicapping your developers by not using commercial JVM. When you already have a revenue-generating code base, throwing Oracle a little money is a no-brainer. There's no way they'd make licensing so expensive that it wouldn't get a CTO fired NOT to buy it. But now they've introduced the drag at the start-up level which I'd voice concern over in my previous post. This is especially sad at a time when the JVM and even Java seems to be enjoying a bit of a renaissance.
Or are you equivocating Ruby with Rails running in a cloud platform? Your last sentence doesn't really parse well.
But that makes more sense thanks, I don't normally deal with Microsoft products in that fashion.
Open source projects like Ruby naturally don't need anything like this; the whole open source model is more open and accessible for everyone than even Microsoft's free offerings.
Ruby doesn't need such a program because the cost of licensing Ruby for a company that only has 2 servers and the cost of licensing Ruby on a fleet of 10,000 servers is still $0. The same is true for Java, for now...