Open access typically means authors pay a publication fee, which leads to the same result of the government paying twice and the journal profiting twice.

Almost as if they shouldn't be getting special treatment in the first place!

  insertDrakeMeme()
  nah: Actor-Critic Models
  ayy: Actor Model

In seriousness, huge fan! multi-agent systems are inherently distributed systems, and we've solved the problem of organizing distributed systems before through actors.

...Just wait until we get multi-agent systems with enough agents to need distributed consensus!

This I didn’t know!

recover()'s semantics make it so that "pointless" use like this can be inlined in a way that changes its semantics, but "correct" use remains unchanged.

Yes, maybe some code uses recover() to check if its being called as a panic handler, and perhaps `go fix` should add a check for this ("error: function to be inlined calls recover()"), but this isn't a particularly common footgun.

> ... and perhaps `go fix` should add a check for this (

This is an impossible task. For a library function, you can't know whether or not the function is defer called.

Maybe this is not an important problem. But it would be better if the blog article mentions this.

'Not common' is comforting until you hit a codebase where recover gets abused and your 'safe' inlining breaks prod.

by future do you mean Future<T> or metaphorical future? :)

I see what you did there.

hey hey hey the world would be a better place if we all used JAX instead :)

There’s a known fix for SQL injection and no such known fix for prompt injection

There is one pretty simple change developers can make to protect against "prompt injection" though.

Not to take away from this cool project, but its design decisions are incredibly impractical.

I honestly can’t tell if it’s a cool project or just a md file someone with 0 experience had an LLM output.

Considering the use of 32-bit fixed point numbers, you can bet on that person having zero clues.

Even the crappiest FPGA has at least 18x18 multipliers, meaning that you could add a small exponent on top to get a floating point type with a slightly worse precision than single precision floats.

32 bit fixed point doesn't map to any DSP I'm aware of.

As far as I remember, they called it a Guild in all their developer documentation

Yeah that was the original name they came up with, and it stuck internally. Makes sense as they need to distinguish the "servers" from the actual servers.