Viewing profile — mikmoila

https://openjdk.org/legal/ai Shitposting, the reasons are very clear and explicit: The risks of having legal problems are very clear. Google for example GEMA vs. OpenAI.

Code contains deviations from assumed behaviour, and some behaviours might manifest themselves as failures. Some failures might be exploitable by attackers.

Yes, imagine a breakthrough moneymaker product containing generative AI parts; It'll be under legal attacks from day zero...

OpenJDK project (interim) AI-policy faq ( https://openjdk.org/legal/ai ): "What are the intellectual-property risks of using generative AI tools? The Oracle Contributor Agreement (…

How about intellectual-property risks?

I don't I use Java for small scripts/tools.

Are they really? I've been under impression that agentic LLMs are just instances of the LLMs, no "specialized training" involved

This is great idea.

Very interesting tool; I've done something quite similar by implementing a CLI-mode interpreter to VS Code Rest-client ( https://marketplace.visualstudio.com/items?itemName=humao.r…

There is nothing special in getters and setters, the runtime sees them as methods and may optimize them as it'd do for any other methods.

Good point, isn't this the partial compilation?

Wasn't it so that as Graal jitter is written in Java, Truffle can easily call it by using ordinary Java api? By the way there's an excellent series of articles about implementing a…

Of course, this is not fully comparable to Akka, but you might find this interesting: https://github.com/ebarlas/game-of-life-csp

Also there are some traceability issues involved in using asynchronous APIs: "In the asynchronous style, each stage of a request might execute on a different thread, and every thre…

Jetty can be used with virtual threads: https://webtide.com/jetty-12-virtual-threads-support/

SC will be a preview level API in Java 21: https://openjdk.org/jeps/453

In addition, this implementation detail might help in gaining some insight: "The synchronous networking Java APIs, when run in a virtual thread, switch the underlying native socket…

Nima uses virtual threads where blocking call blocks only the current virtual thread but not the underlying carrier-thread, which can run another virtual thread while waiting i/o t…

One at a time, not concurrently.

"callRemote" simulates a blocking outbound http-call.

Right to the spot, thanks for sharing this! I've always thought that having a decision log of justifying design/implementation choices which are somehow surprising would be healthy…

Fascinating info, thanks for sharing this with all the details! Didn't watch your youtube video but do you use any formal systems like TLA+ internally for validating your designs?