Kotlin
huginn
Lmao starfield most innovative gameplay
I think 19 reuses of a single rocket is more impressive here TBH
Not even close to the second time. It's happening constantly but is getting missed.
Too many people think LLMs are accurate.
11 years? Nevermind use the laptop for sure haha
You'll probably save money in the long run using a pi.
Also: ::
in Java is method reference. In Kotlin it's reflection.
I'd say if you care a lot about distinguishing contexts it's really the job of the IDE to highlight syntax.
Don't write code as though you're going to read it in plain text imo.
-
Emergence is the whole being greater than the sum of its parts. That's the original meaning of emergent properties, which is laid out in the first paragraph of the article. It's the scholarly usage as well, and what the claims of observed emergence are using as the base of their claim.
-
The article very explicitly demonstrated that only about 10% of any of the measures for LLMs displayed any emergence and that illusory emergence was the result of overly rigid metrics. Swapping to edit distance as an approximately close metric causes the sharp spikes to disappear for obvious reasons: no longer having a sharp yes/no allows for linear progression to reappear. It was always there, merely masked by flawed statistics.
If you can't be bothered to read here's a very easy to understand video by one of the authors: https://www.youtube.com/watch?v=ypKwNrmuuPM
Here's a white paper explicitly proving:
No emergent properties (illusory due to bad measures)
Predictable linear progress with model size
https://arxiv.org/abs/2304.15004
The field changes fast, I understand it is hard to keep up
Their paper uses industry standard definitions
Here's a white paper explicitly proving:
- No emergent properties (illusory due to bad measures)
- Predictable linear progress with model size
https://arxiv.org/abs/2304.15004
The field changes fast, I understand it is hard to keep up
Have found, not will find.
There are so many spam sites with LLM content.