Recent submissions

Comment · 5 days ago
6.0 re branded as terra?
Comment · 20 days ago
I've been vibe coding plenty of apps for personal use, especially to replace free Google stuff; I'm doing it for lack of trust and control those apps give me. Even more would apply to Adobe stuff.

Innovation in Adobe products? Really? I mean, really? Are you serious?

And the main argument is performance on high resolution?

Comment · 22 days ago
I guess they are investing in the team rather than on their demo product
Comment · 27 days ago
Kde html -> webkit -> blink (which is the html of chrome). There is a huge work around the mere rendering engine, to the point that its way more common to fork the whole browser rather than just the low level engine.
Comment · 1 month ago
> it would make absolutely no sense to sit on it.

Yeah, it does, it might be misaligned, a snapshot of the going on training, bigger than they can serve publicly, not yet completed the full training pipeline.

If you see the knowledge cutoff you can see that sol 5.6 finished the initial main (+stage edited) of the training pipeline on Feb 16, 2026 but it was publicly released on July 9.

The opposite would be weird: if they do NOT have an unreleased in-house model that would be really odd.

Comment · 1 month ago
Claude code is a terribile harness, visibility is below zero, require a terminal session per each workspace, remote access makes you wonder if you should give copilot deluxe + a try. And according to the TOS you can't you whatever you want
Comment · 1 month ago
As a reference i burn 1% percent for every 40 minutes of sol on average
Comment · 1 month ago
Not going back to anthropic as i love the alignment of 5.6 sol, but I'll start looking around
Comment · 1 month ago
why
Comment · 1 month ago
The UX seems nice, but the scope is way too narrow. I would be actually lazier for me to to just rebuild it inside my own harness (exactly as i want it) than start looking at yours.
Comment · 1 month ago
I'll quote myself:

> It's not AI that's ignoring the law! It's the OAI that's breaking IT!

> I hope every single journalist who tries to pin responsibility on an LLM gets 100 days of continuous painful diarrhea.

Comment · 1 month ago
> but more important is that this is not the first instance of AI agents ignoring laws on accessing online information.

It's not AI that's ignoring the law! It's the OAI that's breaking IT!

I hope every single journalist who tries to pin responsibility on an LLM gets 100 days of continuous painful diarrhea.

Comment · 1 month ago
Nice idea! Didn't think about that; a single linear memory allocation could do the trick
Comment · 1 month ago
> <200ms for 45 questions at once

Considering your own question length: ~120 characters x 45 divided by 4.1 ~= 1317 tokens.

So question processing at 5.5k PP(around the actual PP speed of GPT5.6 Sol) it would take around ~0.24 seconds + the context processing.

Computing the output should be around ~20ms (at 50 tok/s), computing 45 tokens in parallel.

> have 0% malformed output

Pretty trivial; only the allowed output is selectable :)

So, I keep repeating myself: Jev was a low-hanging fruit all along; no one cared, and probably no one will in a few weeks?

Comment · 1 month ago
By design it can't be significantly slower than Jev: the prompt processing (AKA PP) is exactly the same on both and will take most of the time. Then you can process every single "question" in parallel, just predicting one or two tokens (if an answer is ambiguous with a single token) per each question, again in a single batch.

So, fast in the LLM space and comparable with Jev.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton