It can’t be confirmed by Netcraft, but Java is dying, and has been, according to many naysayers, pretty much since the language came out. But when you have a blog post from the driving force behind the popular Wicket framework with a title that ends with “…and the end of Java” (and has a picture of a tombstone with Java’s name on it, natch) maybe it’s time to pay attention. Jonathan Locke basically feel that Java generics, and type-safety in general, have absorbed way too much energy in the developer community for years. “If the problem can’t be solved in such a way that ordinary programmers can write and not just use generics, I think Java has (in the words of somebody who I never ever thought would say this about Java) ‘jumped the shark.'” Java