569 karma · joined July 18, 2018
Someone else here said we could get the model via OpenCode Go for $10/mo and get about $120 worth of credit, so I decided to give it a whirl. My first month is actually $5.
In the 3 hours I've been using it I've burned 3% of my 5-hr, 1% of my weekly and 0% of my monthly.
It's fixed 3 or 4 issues in my C++ game, despite not having visual capabilities to see the screenshots I was trying to give it. One-shotted them too.
Luna struggled with what I thought was an easy task (had to replace a few ASCII chars with the correct unicode char but kept choosing incorrectly).
I'll keep using it.
> Protobuf even marks the required keyword a hazard developers must avoid. These rules exist because a single definition is forced to serve every document ever written against it. TSON removes this burden because schemas are immutable.
I personally don't have a problem with them. They've grown on me. Thought they looked icky before I actually had to use them. Now I see their merit.
I don't understand how this helps. That just means I have dozens of schemas for the same data set. How is that better? I'd rather have one lowest common denominator schema for the entire data set and be forced to validate.
I mean I guess because the data blob specifies its own schema I can use that schema to ensure the blob is valid but then what. What is my code that processes this data supposed to do? `if(schema1) { ... } else if(schema2) { ... }`. How is that better?
The moving tabs issue we can fix but just not moving them.
And the vertical space issue is much less of an issue now than it was then because we have higher resolutions but the answer to that is to start closing tabs when you can no longer see your content. It's like a quiet little nag that says you have too much stuff open.
The "for agents" is a bit of a turn off for me. Are they just trying to jump on the AI hype train or is this really AI-centric? Because if its for agents and only agents then I guess I should expect it to get progressively worse for humans but its for humans & agents then maybe it stays a nice clean human-friendly language.
But I guess they didn't want to put a "Slow" button on their PC towers.
What they did was kind of clever. When the agent calls the old API/uses old args, I guess they told it to tell the human to fix their skill and 'upgrade' to the new API. They even provided a skill upgrader skill.
Anyway, my agent tried calling it the old way, must have received some sort of error message and then diligently reported to me that my skill needed upgrading and we should be doing it some new way.
Kind of like reverse feedback I guess? Not the AI giving feedback to them, but them giving feedback to me via my AI.
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
Which variable? `i` is clearly initialized to `0` and `it` doesn't have an initializer per se... it starts at the first value of the container.
It almost seems like an abuse to put 2 unrelated things in the `for(...)` but that's what they did.
It was in the middle. $165k.
> At the time of writing, about 4% of Bun's Rust code sits inside an unsafe block (~13,000 unsafe keywords across ~27,000 lines / ~780,000 lines), and 78% of those blocks are a single line — a pointer that came from C++, or one call into a C library.
I don't know much about Rust but I imagine this is safer than 100% 'unsafe' code in Zig or C++.
I suppose rendering is a component of a game engine too though, not just physics. I don't know how to do that reliably. Even if you captured pixels, it'd be annoying. If you've ever tried doing screenshot based diffing on web you will know that slight changes in aliasing in Chrome bugger everything up. Things that should be equivalent randomly aren't but not in a way that any human would care.
Seems a bit disappointing, but the 3 overlapping questions example was impressive.
Not sure I'd want to put an adhesive patch on my neck every morning so I can silently talk to an LLM in the cubicle farm. I hope this is not our future.
Very cool tech though and surprisingly good results for so little training.
I think time might be better spent improving a lip reading model (no adhesive required), assuming we're unable to read brainwaves directly.
Might not be a bad idea to formalize this process with a skill.
Also the task list (checkmarks) render poorly in PDF.
Also why wouldn't rendering the same doc twice produce the same byte output?