3 ms·

It may. Java io stack is quite bad at certain tasks like crawling files and tracking changes.

• pjmlp 11y ago
  On my experience, the blame is more between chair, keyboard and monitor than with JVM itself, given the typical codebases I have to review for quality issues.
  • LoSboccacc 11y ago
    eh, any app that maintains compatibility with jdks < 7 can't use the WatchService and it's low level system specific API, which includes buttload of enterprise app and but the most recents IDE that are starting to drop jdk 6 support. then there is indeed the PEBCAK as you say, but you can't really blame people that knows the proper solutions if they have weird jdk to support.
    • pjmlp 11y ago
      Just two examples of such PEBCAK quality: - Using a for loop to copy array contents instead of System.arraycopy() - Doing everything on the main thread in Swing There are plenty more that I can list and they never have anything to do with JDK versions.
    • pron 11y ago
      That problem was solved in the JDK five years ago. If you're required to support a ten-year-old, EOL-ed platform because people don't upgrade, that's still not the JVM's fault...
      • LoSboccacc 11y ago
        If it were for rational people, we wouldn't have spring beans application around. World isn't built on technical excellence.