Example: I occasionally still use new Date(...) out of convenience and ignore the warnings. I know it's wrong, but Calendar feels like a 18- wheeler when all I need is a bike.
/Casper On 2 Aug., 16:26, Jess Holle <[email protected]> wrote: > Ben Schulz wrote: > > On 1 Aug., 11:42, Jess Holle <[email protected]> wrote: > > >> Actually removing things will break a substantial amount of software in > >> most cases and fragment the Java community. Simply filtering out cruft > >> and moving it to legacy compatibility modules where possible gives > >> almost all the benefits of removal without the cost. > > > When it comes to removing e.g. System.getenv(), I agree. It worked > > well for a bunch of people -- utter madness to quasi-remove it by > > having it throw an Error (which goes beyond mere lunacy). That really > > "breaks software"; but then there's Thread.stop() and the like. > > Breaking broken software so that it has to be fixed is a good thing. > > I'd concur for Thread.stop() but there are very few cases that are as > clear cut as Thread.stop. > > -- > Jess Holle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The 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 -~----------~----~----~----~------~----~------~--~---
