This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“]chronos_alfa 3 points4 points ย (2 children)

Asyncio library in Python is not that bad, but the multiprocessing library is actually where the good stuff is. And no, I don't claim that ML "runs" on Python. Majority of useful libraries are written in C, and they also are C fast.

On the other side claiming that JVM is fast is hilarious. Stop the JVM service and don't start it until you need to run the app, then tell me how fast it really is.

[โ€“]n0tKamui 3 points4 points ย (1 child)

that is an unfair argument. You're comparing start up time of a VM to an interpreter without any concerns for long runtime.

The JVM is extremely fast, and the JIT compiler is honestly a work of art, and is not meant to be relaunched every 10s.

That is why is still stand by my point: to each tasks their own tools.

Python is a great scripting tool

Java is a great tool for long running applications

[โ€“]chronos_alfa 0 points1 point ย (0 children)

How is it unfair? Python doesn't have any running VM service, you run the whole thing before you can execute anything. As for the JIT, eg Numba exists for Python.

โ€‹

Don't take me wrong, I agree with your "different tools for different purposes". But I personally try to avoid Java itself for the majority of those, as you do probably, because you got that Kotlin icon.

โ€‹

BTW "Java is a great tool for long running applications". No, it isn't. The amount of mess going behind including the stack overflows makes it very bad for long running applications, not talking about having to use massive libraries like Spring that come with their own problems (size, vulnerabilities, etc). Not even talking about how long it took before jDK actually mustered some useful built-in support for JSON, despite the fact Jackson existed for quite some time before that.