I guess I didn't make it clear that my unfair sweeping generalization 'you are claiming that "new technology" is irrelevant.' was a shot at your sweeping generalization of "irrelevant".
I don't really understand "% of money". what money? github just did a $100m round at a $700million valuation. So someone thinks it's interesting…. take a look at github. a huge chunk of the interesting open source stuff is being hosted there: twitter bootstrap (and all twitter open source projects), play framework, hibernate, jquery, mongodb, etc, etc, etc from http://gigaom.com/2012/07/09/github-finally-raises-funding-100m-from-andreessen-horowitz/ : "GitHub’s site holds more than 3 million software repositories (co-founder and former CEO Chris Wanstrath once described it as “the Wikipedia for programmers”) and counts more than 1.7 million developers as users. On an average day, 80,000 repositories are updated and 7,000 individuals push their first repository to GitHub’s site, according to the company. " I think it's safe to say github is a measure of active open source projects. It is not a measure of enterprise usage. here are the lang stats: https://github.com/languages On Fri, Jul 20, 2012 at 1:22 PM, Fabrizio Giudici <[email protected]> wrote: > On Fri, 20 Jul 2012 20:34:25 +0200, phil swenson <[email protected]> > wrote: > >> very flawed statistics (tiobe). >> >> If you want to know where the mindshare of new stuff is, take a look at >> github. > > > Tiobe is surely flawed, but github? I don't know any large industry which is > placing its sources under a private github repo. I presume we have to > clarify what we mean with industry. > > >> basically, you are claiming that "new technology" is irrelevant. > > > This is a wild generalization of my thinking. I'm saying that the new > languages are, up to now, scarcely relevant or irrelevant. "Relevance" for > me is the % of money. The discussion was related on the industry alleged to > leave Java because it's too old, with the postponing of jigsaw making the > problem worse. My point is that I'm upset with jigsaw delays because it's > jeopardizing the chances Java clients defend or enlarge a bit their market > share, but for what concerns the areas where Java is currently strong it > won't make a big difference because, as others said, server-side people > needing componentization can use OSGi and a few dozens of megabytes more in > the runtime are not a problem. > > Back to the technical point, I cited Maven and somebody put a question. I > have to disagree with Kirk's position about it's better a delay that a > half-baked solution. It largely depends on the context. If the good solution > arrives when it's useless, I prefer a half-baked solution. Maven > dependencies provide a mechanism for defining components and relationships > which is far from being perfect, but it is something that has been used for > years, so we know it pretty well. It doesn't deal with runtime, but a simple > mechanism for it can be borrowed from other systems. So, while a team is > working on a full-fledged jigsaw for 2015, another team could have been > working on an intermediate solution that should have been ready in 2013. And > looking back, the alternate solution should have been worked about since the > very beginning, so perhaps we could have had it by 2011, JDK 7. Some said > that the community could have contributed instead of whining and well, this > is what I often say for many other things, so I can't really disagree. But I > fear that working inside the core of the JVM is beyond the capabilities of > the community. > > Of course, it all depends on which are the actual technical problems of > jigsaw and a big trouble of this discussion is that we're not dealing with > them. > > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > [email protected] > http://tidalwave.it - http://fabriziogiudici.it -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
