Bliss:

  Installation
  
  Add two files to your project:
  
  src/im_anim.h
  src/im_anim.cpp
  
  That's it. No build system changes, no external dependencies.

Exactly! And add the demo file to see it in action.

Stating a 20-year trend like it's a new development :P

Some real hard-hitting "reporting outlandish self-serving claims by CEOs as accurate forecasts" journalism.

Dark gray on black text? lol

>> Rather, what we need to do is to calibrate the physical economy such that we can benchmark the monetary against the material. This enables us to avoid the futility of measuring the monetary only against itself.

Garden-variety Gold Standard quackery.

I kept having my bad vibes meter triggered by the italics so thanks for making the connection for me.

My spider sense was going off because they spend the first several pages constructing the most obtuse definition of Inflation without just saying it.

Wait, it's not obvious to me why this is quackery?

It makes people uncomfortable. That's the long and the short of it.

That may be 100% true, but the market can remain irrational longer than you can remain solvent, and in this case, gold has been doing awkwardly well under current conditions.

By the article's _own_ parable: if you were starving on a desert island, you wouldn't be relieved to be airdropped a briefcase full of gold. You're benchmarking money to money.

IMO, combining gold money arguments with observations about the price of gold is contradictory. If gold is money, then you should never wonder about the "price of gold" as gold should be used to price things.

Roughly half the gold produced each year vanishes into gold hoards. Half.

This has been going on for forty years. There's literally decades of gold production sitting in hoards all around the world.

Gold prices could get very strange very fast.

Aside from financially-motivated "testimonials," there's no broad evidence that it even works that well for coding, with many studies even showing the opposite. Damning with faint praise.

It depends on a lot of things.

I know JavaScript on a pretty surface level, but I can use Claude to wire up react and tailwind, and then my experience with all the other programming I’ve done gives me enough intuition to clean it up. That helps me turn rough things into usable tools that can be reused or deployed in small scale.

That’s a productivity increase for sure.

It has not helped me with the problems that I need to spend 2-5 days just thinking about and wrapping my head around solutions to. Even if it does come up with solutions that pass tests, they still need to be scrutinized and rewritten.

But the small tasks it’s good at add up to being worth the price tag for a subscription.

Do you feel like you begin to _really_ understand React and Tailwind? Major tools that you seem to use now.

Do you feel that you will become so well-versed in it that you will be able to debug weird edge cases in the future?

Will you be able to reason about performance? Develop deep intuition why pattern X doesn't work for React but pattern Y does. etc?

I personally learned for myself that this learning is not happening. My knowledge of tools that I used LLMs for stayed pretty superficial. I became dependent on the machine.

These are things I pull out like 2-3 times a year normally, so I don’t feel like that makes a huge difference.

I’ve been learning zig and using LLMs clearly did hamper my ability to actually write code myself, which was the goal of learning zig, so I’ve seen this too.

It is important to make the right choice of when/how to use these tools.

I think what’s clear is many people feel much more productive coding with LLMs, but perceived and actual productivity don’t necessarily correlate. I’m sure results vary quite a bit.

My hunch is that long term value might be quite low: a few years into vibe coding huge projects, developers might hit a wall with a mountain of slop code they can no longer manage or understand. There was an article here recently titled “vibe code is legacy code” which made a similar argument. Again, results surely vary wildly

It feels like it's creating economic activity in the tech sector the same way that walking down the street and smashing everyone's windshields would create economic activity for local auto shops.

Jeff Preshing was a longtimer at Ubisoft, and developed for Corel before that in their heyday. His blog makes for good reading: https://preshing.com/

"Exceptions are values within the system’s expected operating boundaries." This makes sense in narrow context, but as a question of intent - exceptions are not expected. Common example I encounter in prod are .net platform libraries which add security exceptions on system update w/o requiring app rebuilds.

Yes, exceptions often surprise us in practice. The distinction I'm drawing is more about categorical boundaries than anticipated boundaries: exceptions are part of normal control flow, they are catchable and can be handled. Assertion violations are different: if an invariant is violated, no subsequent action should be trusted.

Misleading use of the term "runtime" as it does not implement lua, but just links nonrust implementations into a webserver "runtime."

That's exactly how the term runtime is consistently used in the JS world... not sure it's misleading at all. Certainly less exciting/ambitious than if the interpreter was also rewritten, but its what it says on the tin as I understand the words.

V8 and JSCore are a runtimes, everything else is made up stuff by people without background in compilers.

That's not at all what a runtime is, in any context, ever. Where else have you seen this solecism? It's new to me.

First sentence of the Wikipedia article for Node.js:

> Node.js is a cross-platform, open-source JavaScript runtime environment that can run on Windows, Linux, Unix, macOS, and more.

First sentence for the Wikipedia article Deno:

> Deno is a runtime for JavaScript, TypeScript, and WebAssembly that is based on the V8 JavaScript engine and the Rust programming language.

First line of hero text from Node.js's site:

> Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.

First line of hero text from Deno's site:

> Deno is the open-source JavaScript runtime for the modern web.

> Where else have you seen this

Node.js is easily the most famous example. Also deno, bun, winterjs, and probably a bunch more.

Someone upthread just linked a bunch of other equivalent lua projects that also refer to themselves as runtimes: https://news.ycombinator.com/item?id=46036362

I've also seen discussions where wrapping the servo-browser-engine in a UI layer referred to the UI layer as a runtime, though I think that's a substantially less canonical use of the word than referring to the part of an implementation that takes requests from the interpreter and executes them in the surrounding environment as a runtime.

Yep. Specifically, the crate uses mlua: https://github.com/ArkForgeLabs/Astra/blob/f812bb0dc2881d740...