Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mikmoila
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
mikmoila
12d ago
Yes "at any substancial level" . But still, its all about deterministic processes and still it obeys the law that the same input gives the same output. Or do you mean that the fluctuations like computing environment might ruin th
2.
▲
by
mikmoila
12d ago
I think you're referring to the fact that the sheer amount of computations is something too time consuming for us to follow? But still it is not "magical" - in theory we could follow all the steps, there's no hidden info
3.
▲
by
mikmoila
12d ago
"you could never have accomplished"; I am not able to follow the logic here - there is no "magic" in LLMs, they're built by humans and we know what they do.
4.
▲
by
mikmoila
12d ago
Humans built the tool which enabled the result. AI used the tooling for eliminating the dead ends. Yes, I can appreciate the practical value of all this, but IMHO it is not a kind of breakthrough result the article gives impression of.
5.
▲
by
mikmoila
12d ago
"The effort succeeded when we switched to using Prove2Me, an open collaborative platform for formalizing mathematics designed by Tianyi Peng and his collaborators at Columbia University." So in the end, it required tooling crafted
6.
▲
by
mikmoila
1mo ago
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.
7.
▲
Demystifying Dependence [pdf]
(jameskoppel.com)
2 points
by
mikmoila
2mo ago
|
0 comments
8.
▲
by
mikmoila
4mo ago
Code contains deviations from assumed behaviour, and some behaviours might manifest themselves as failures. Some failures might be exploitable by attackers.
9.
▲
by
mikmoila
5mo ago
Yes, imagine a breakthrough moneymaker product containing generative AI parts; It'll be under legal attacks from day zero...
10.
▲
by
mikmoila
5mo ago
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 (OCA) requires that a contributor ow
11.
▲
by
mikmoila
5mo ago
How about intellectual-property risks?
12.
▲
by
mikmoila
5mo ago
I don't I use Java for small scripts/tools.
13.
▲
by
mikmoila
8mo ago
Are they really? I've been under impression that agentic LLMs are just instances of the LLMs, no "specialized training" involved
14.
▲
by
mikmoila
1y ago
This is great idea.
15.
▲
by
mikmoila
1y ago
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.re... ) files, with a support of executin
16.
▲
by
mikmoila
2y ago
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.
17.
▲
JEP 468: Derived Record Creation (Preview)
(openjdk.org)
2 points
by
mikmoila
3y ago
|
0 comments
18.
▲
by
mikmoila
3y ago
Good point, isn't this the partial compilation?
19.
▲
by
mikmoila
3y ago
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 an interpreter with Truffle by Adam Ruka: https:&#
20.
▲
Helidon-Nima-Example
(github.com)
2 points
by
mikmoila
3y ago
|
0 comments
21.
▲
by
mikmoila
3y ago
Of course, this is not fully comparable to Akka, but you might find this interesting: https://github.com/ebarlas/game-of-life-csp
22.
▲
by
mikmoila
3y ago
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 thread runs stages belonging to different requests in an in
23.
▲
by
mikmoila
3y ago
Jetty can be used with virtual threads: https://webtide.com/jetty-12-virtual-threads-support/
24.
▲
by
mikmoila
3y ago
SC will be a preview level API in Java 21: https://openjdk.org/jeps/453
25.
▲
by
mikmoila
3y ago
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 into non-blocking mode. When an I/O operation inv
26.
▲
by
mikmoila
3y ago
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 to complete.
27.
▲
by
mikmoila
3y ago
One at a time, not concurrently.
28.
▲
by
mikmoila
3y ago
"callRemote" simulates a blocking outbound http-call.
29.
▲
by
mikmoila
3y ago
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 thing to do.
30.
▲
by
mikmoila
3y ago
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?
More ›