
Ok, that I can understand. But any modern Java application should be shipped as a container were this isn’t an issue.

Ok, that I can understand. But any modern Java application should be shipped as a container were this isn’t an issue.

Not sure what experience with Java you are talking about. As a Dev, modern Java still rock solid and is finally quite convenient to use and the JVM itself is a great runtime.


It’s someone from .ml . Don’t bother.


Funny that they are complaining about a restriction put in place by Google that they have no control over. So either Google already backdoored Pixels for them or more likely they know they can just bully FOSS devs without direct legal repercussions…


Seems like it evaluates on par with llama3.1. Haven’t had many reasons to use LLMs, but this looks like a good option.


From the gitlab repositories it kind of looks like they are dropping that naming scheme wit v4. It was kind of cute, but also confusing if you have no idea about TF2 and use Steam.
I don’t see how you’d have any less problems with a natively installed Node.js, Python or PHP application. This is not a Java specific issue.