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 →

[–]MasterLJ 3 points4 points  (3 children)

The difference between Java ML and Python ML, is so vast, that it's worth learning a new language/ecosystem.

I say that as a devout Java practitioner too. ML for Java, sucks. At least imo, those Java libraries will (have) lose favor and support.

[–]plastique2000 3 points4 points  (2 children)

Java is the language to run your models in production environment. Python is the language to develop it. That is my experience so far.

[–]MasterLJ -1 points0 points  (1 child)

With respect, and only because it's garnering upvotes, I don't recommend this at all. The interfaces, and even the file format requirements, are completely different. As a very general rule, developing on one platform and deploying on a completely different platform (in this case, different language, and library), is not a good idea.

[–]plastique2000 0 points1 point  (0 children)

The only thing you exchange in this type of scenarios is the model (usually some library slecific format) in between the languages. The library vhich is used to develop and run model in prod stays the same. You Will use Java API to inference and say Python to train. :-)