4 ms·
"Disclaimer: The file.encoding property is undocumented and not officially supported, and it has been reported to act inconsistently across Java versions and pl
by phyzome 11y ago
"Disclaimer: The file.encoding property is undocumented and not officially supported, and it has been reported to act inconsistently across Java versions and platforms."
Oh Christ on a cracker. Why doesn't Oracle just default everything to UTF-8 in the next version of Java?
- chillydawg 11y agoToo late for that kind of change, really. 20 years of legacy systems are not going to enjoy that.
- colejohnson66 11y agoIf their legacy system doesn't support UTF-8, I doubt they'd update their system at all.
- chillydawg 11y agoThey probably want update the JVM for security purposes, though. There's plenty that will absolutely kill you in any public facing JVM from more than a few years back. The first release of 7 has at least two very bad denial of service attacks that allow a remote user to saturate as many CPUs on your server as they like, all they need to do is send magic http headers to your tomcat or whatever.
- colejohnson66 11y agoPeople say that about operating systems, yet you have businesses running Windows XP still simply because they don't want to update. Yes, there's ones that don't for compatibility, but there are some that don't upgrade simply because they don't want to.