4 ms·
It's been 19 years since this problem has been fixed and yet the bad code is still there.
by fistynuts 5y ago
It's been 19 years since this problem has been fixed and yet the bad code is still there.
- brunoborges 5y agoI'd suggest you assess first the amount of code that depends on java.net.URL both in Java SE itself and then in the ecosystem, before you can say it would be "easy" to remove java.net.URL. Hint: same reasons java.util.Date, and java.util.Vector are still there.