I think that's a question of semantics: GenericServlet handles no protocol specifically, but it handles all protocols because all protocol-dependent classes that extend it inherit its (admittedly rudimentary) code - which is thus used to handle all those protocols.
So I would say GenericServlet implements no protocol, but it handles all of them.
I was rooting for Belgium, but I think on that day the better team won. The French side lost sympathies for the blatant (and successful) attempts to take time off the clock late in the game, though. A newspaper here counted that there were less than 8 minutes of soccer between the 81. and the 97. minute. They have acted similarly against Argentina and Uruguay - while other teams also dabble with this, none does it as blatantly. That is a turn-off for me.
My advice is to work on a product or library that you're already using and which you like. It's easier to stay interested in it over a longer time that way. Plus, you get to enjoy the fruits of your own labour :-)
Well, things like range accurate floating point mode surely need to happen.
Why? IEEE 754 -which float and double implement- allows underflow and overflow, and for the vast majority of applications that appears to be adequate. I'm not convinced that the rest need to be accommodated via functionality built into the JRE.
I don't think there is a consensus for many of the things that you say must change or need to be provided that that is actually so. There is no shortage of mathematical libraries that address many of these points for anyone to use who needs them. That they all need to be provided by the JRE is not clear to me. While it would make some people's work easier, my guess is that it is actally a small niche; I wouldn't hold my breath waiting for any of this.