vlaaad

Did we read the same Anthropic and Andrew Kelly's posts? Anthropic is not in the programming language market; their post about rewriting Bun in Rust is full of technical details that led to improving the end product for their users. Zig's response is a sour opinion piece full of personal attacks.

For context, I'm using Codex and have no interest in either Zig or Rust, so just observing this drama from the sidelines.

LMAO I'm not using it. No, I don't allow microphone access.

The implementation uses jextract-generated bindings, so it can be considered a light-weight wrapper around libghostty and a rendering layer that uses JavaFX. Works on Windows too (unlike Ghostty :P)

Yeah, I really enjoyed Crafting Interpreters, wholeheartedly recommend!

More like /r/cars bans all discussion of electric cars.

So a buy order for $122000M, and a sell order for $600M is presented as bad news for OpenAI?

Use the term, never define the term, classic.

CTE stands for Common Table Expressions in SQL. They are temporary result sets defined within a single query using the WITH clause, acting like named subqueries to improve readability and structure.

My AGENTS.md is usually `be concise` — it saves on the input tokens as well, and leads by example.

Unrelated, but I just can't stop myself from saying that I absolutely hate Spotify even though I'm a paying customer. Fuck you Spotify. You were supposed to be a convenient way to discover and listen to music. Now you are only convenient for listening to music, and absolutely terrible for any recommendations. This is sad really. Spotify had good recommendations. It's absolutely in a position where it can provide good recommendations — it has both a vast music library and a vast amount of data on user preferences. And it chooses to push procedural/ai-generated slop instead to earn more money. I thought that maybe buying $SPOT stock will make me more at peace with its greed, but it didn't work. Spotify fucking deserves to crash and burn because it sees paying customers as idiots who might not notice they are fed garbage. Fuck you Spotify, fuck you.

Saying "other single points of failure" makes no sense whatsoever.

Does this person also identify performance issues by reading the code? This is completely impractical.

Have you compared performance of your solution to rive?

I love this idea; I hope it gains traction. One thing that is not clear to me is file search vs unsaved files. It's common for agents to use, e.g., ripgrep to search the file system. But if the communication protocol includes read/write access to unsaved files, there is a desync in terms of accuracy.. rg can't search unsaved files.

Yes, though I also liked the overall point of the post. Spotify recommendations are shit, and any playlist made by Spotify is full of garbage. I guess Ek knows this and, perhaps unconsciously, sees himself as evil, doing what's legal no matter how bad it is, with his weapon investments...

The difference between 99% reliability and 100% reliability is huge in this case.

Not true, structured outputs enforce output formats with 100% reliability, e.g., https://platform.openai.com/docs/guides/structured-outputs says "Structured Outputs is a feature that ensures the model will always generate responses that adhere to your supplied JSON Schema, so you don't need to worry about the model omitting a required key, or hallucinating an invalid enum value"

Sure, but the need for accuracy will only increase; there is a difference between suggesting an LLM to put a schema in its context before calling the tool vs forcing the LLM to use a structured output returned from a tool dynamically.

We already have 100% reliable structured outputs if we are making chatbots with LLM integrations directly; I don't want to lose this.

I was considering making an MCP SEP (specification enhancement proposal) — https://modelcontextprotocol.io/community/sep-guidelines, though I'm curious if other MCP tinkerers feel the issue exists, should be solved like that, etc. What do you think?

Not sure; the schema of the Props argument depends on the value — not type — of another argument, so it's not just generics.

This little experiment reminded me about the magic of programming that we've all gotten used to.

We've been working hard on making it easier to import assets or generate scenes in the Defold editor. This post is a sneak peek of what's coming in the next Defold release. I'm happy to answer any questions!

Should we tell him?

Reddit's /r/chatgpt subreddit is currently heavily brigaded by bots/shills praising r1, I'd be very suspicious of any claims about it.

My thoughts exactly. His sequential program example is easily parallelizable. Maybe one of the takeaways should be that we need to work on converting more serial problems to parallel ones

Defold: https://defold.com/

Defold is not as well-known as Löve, but it seems to fit your description: https://defold.com/

no

Re https://where.durableobjects.live/ — why the hell are they still operating in Russia?

I can't shake off a feeling that "integrity by default" is a populist bullshit.

If a third-party library is not updated to not use require reflection, the speaker considers it "a red flag that it's improperly maintained" and suggests looking for alternatives. This is just plain ignorance: for particular domains, there are libraries that either don't have alternatives, or the cost of switching to the alternatives is too high. Are JVM developers going to pay me to write a replacement for every old library essential for my projects? This simplistic approach severely downplays the impact on what the speaker calls "old applications", i.e. the battle-tested, money-generating, useful applications.

Like, I get the usefulness, and I get that it's an attack surface, but it seems the author never had to deal with real-world projects where going into the internals of other dependencies to fix them or access hidden functionality is an absolutely crucial requirement that creates value for the project.

*Twitter stopped requiring authentication.