3 ms·
> Combine that with the fact that they chose to implement the scheduler in Java instead of C(++) and you're set for performance problems. Ah yes, the argument
by bitcharmer 3y ago
> Combine that with the fact that they chose to implement the scheduler in Java instead of C(++) and you're set for performance problems.
Ah yes, the argument from the 1990s. It would make sense to understand where the JVM and its compiler are these days before making incorrect statements about performance.
From your link:
> Blocking network TCP IO needs a sychronized block to work
This is utterly false.
- spintin 3y agoSo how do you implement a TCP socket? I have always had to do synchronized(something) { socketInputStream.read(); } And the dude himself says that reading from a socket is a problem if you listen to the interview.
- bitcharmer 3y agoSomething tells me you don't know much about programming in Java. Just look up any tutorial showing how to use NIO (blocking and non-blocking). Synchronized in this context is pretty nonsensical.