/tech/ - Technology★

so you can use jvm libraries with python syntax

>>933195

This

>>933194 (OP)

>people who use shit languages want more shitty things

Not that surprising.

>>933194 (OP)

>>933195

>>933204

jvm used to be _the_ way to do MPP. It's nice to be able to use under the hood of your code. These days with mesos and lxc though it's advantages are becoming less significant.

Pythonistas are retarded cultists. That's why.

>have large codebase in python

or

>have irrational love of python

and

>need to target jvm

Same as any other (especially bytecode) translator/emulator

>>933195

/thread

We actually use it at work because we want to create new machine learning models in python, but Java is used in production where the models should run. Models can usually be exported in some language agnostic format or can be imported in Java for some python specific frameworks. But the actual feature extraction, scaling of values, preparation etc is usually specific per model, so apparently jython is used as an experimentation for doing that so that you don't have one Java and one python implementation. Since if that step is done wrong, the model is basically broken if values are not correctly prepared. But I feel there must be a better approach, however things like REST API is too slow for the rate that the data come in at.

Just use assembly bro.

Jython doesn't use the Java language, that's just your own confusion. Jython actually uses the Java virtual machine which is a theoretical computer. This computer is theoretical because there aren't really hardware devices that follow the architecture of this Java virtual machine

>>933506

>Jython doesn't use the Java language

>besides being written in it

>besides the main point being to call Java libraries

hurr

>>933194 (OP)

Same as IronPython, FAG

Java shops are trapped in a Java ecosystem but hate the verbosity of Java. So they're really into fucking anything which lets them continue to use Java without having to actually use Java.

>>933542

Java shops are Java-oriented by choice. The real answer is that some devops personnel needs to write code which interfaces with the main application, but there's not a clear separation of concerns because the company was too cheap/small to hire an architect. Enter: Jython.

>>933194 (OP)

So you can wait 20 seconds to run your pythong scripts

>>933527

He's right, though. Java as a language is not the same thing as the JVM. When you use Jython at runtime, it doesn't interact with the Java language at all. It doesn't call javac or touch any Java source code. It interacts with the Java platform.

>>933194 (OP)

One more niche is scripting applications with a Java codebase or somehow other deep integration into the Java ecosystem (e.g. RMI interface or XML galore), especially since Jython still only implements the legacy branch of the Python language.

For example, at work I have to deal with proprietary applications running on Oracle WebLogic Server, which uses WLST (Weblogic Scripting Tool) for automation, which is a Jython interpreter that loads a subset of the application server's classpath and declares some domain-specific global objects.

Sadly, their embedded version is stuck at Jython 2.4 with a subset of the standard library, so you still have to script most things around that with the system Python interpreter and shell scripts.

>>933194 (OP)

>What's the point of jython?

Planned obsolescence.

>>935155

Can you elaborate?

>>935255

Reinvent everything and make it so heavy people need more powerful computers to run it.

>>935257

Have you ever used CPython? It's not exactly speedy.

Not to mention that Jython is squarely aimed at people who are already using the JVM.

...2 weeks later...

Tutorial - How to use garbage collection in jythonC?

>>933527

>what is syntax

>what is executing bytecode

hurrr^2

>>933527

java compiles to a virtual machine

jython compiles to the same virtual machine

jython knows nothing of java. I

ts just the same target "hardware", and libraries are compatible by means of the hardware; not the language.

In the same fashion that python normally calls C binaries, despite not knowing how to parse C code.

>>939160

Lol you know nothing about Java, its history, or its use cases.

>>939226

I find Java great for OOP / GUI stuff. Python's great for scripting, and pretty much everything else can be done with C.

python is a language for retarded pajeets

>>939160

>Java heyday was the 90's.

Java had barely begun to be formed as a language by the late 90's, and its seen much wider adoption in the 2000's, especially after version 1.5 introduced major enhancements.

>>939207

>GCC does a better job of portability

Ridiculous, silly statement. The JVM normalizes so many things that the C programmer has to consider. You are sub-Pajeet levels of language competency, so I'll let you dig through this.

https://softwareengineering.stackexchange.com/questions/111080/why-is-java-considered-more-portable-than-other-languages-like-c

>>939655

As a C progammer, I can ./configure && make && make install 20 year old C projects and expect them to work. But getting anything modern in Java to build is a nightmare. Gradle seems to barely be maintained and is falling apart, everything needs a specific JVM version and everything needs a different specific JVM version, there are a ton of build tools that need to be understood, it takes a long time to set up a proper build environment, etc.. It's insane. What a fucking mess.

>>939711

Really? I have a few old Java programs from 2000~ that still run fine now. I also have old C programs that still work too. Don't know what to tell you anon.

>>939374

Do you have any real arguments? I have personally found Python to be great for writing quick scripts to do tedious tasks.

>>939655

I used to hate Java, but after using it for awhile, I prefer it now. If I need a GUI and I want it to look native to the OS, I just use SWT.

oh noooOOOOOOOOO the two worst languages!

>>939711

>>939711

> Gradle seems to barely be maintained and is falling apart, everything needs a specific JVM version and everything needs a different specific JVM version, there are a ton of build tools that need to be understood, it takes a long time to set up a proper build environment, etc..

First of all, it's pretty obvious that you checked out the source of a large project and were overwhelmed by a toolset you aren't familiar with. There's nothing easier than installing a JVM and using a dependency management tool like Maven or Gradle to get a project started in minutes. And this:

>everything needs a different specific JVM version

Bullshit. Give me one example of some old Java code that won't run in a modern JVM.

>>939718

>SWT

Just out of curiosity, why SWT and not Swing with the UIManager setting the system look-and-feel?