FuckButtons

When mythos was released - I guesstimated that we had 6 months until hackers had similar enough capabilities that we would start to see real problems in the wild. Unless there is some change in the trend line things are about to get really quite spectacular.

The rate at which software is produced has never been higher, nor has the rate at which it is thrown away for being broken and useless. It’s not at all obvious to me that if you control for both of those rate changes that the amount of useful software with a lifespan measured in years created per developer (ie, the software that actually has long term value) has actually changed all that much.

No, because these are not generated using any model available on their api.

Is this closed source?

Yeah I’m the exact opposite, thought is almost entirely auditory.

It doesn’t have a stable abi, how could it be easier? I would argue that the vast majority of what rust gives you comes at a direct cost of precisely the ergonomics of manual memory management. It’s a tradeoff that makes sense much of the time, but it’s still very obviously a tradeoff.

While this is true - and I see the same sentiment as i am about to make ad nauseam - it is kind of amazing how far the goal posts have moved in such a short space of time.

Not sure why ds cache costs are confusing? Their kv cache is absurdly compressed compared to almost everyone else.

if you think about that statement a bit more deeply, how else are you going to incentivize a society as a whole to take risks? If all the risk from your actions is ultimately your responsibility, no one would take risks, no one would explore for the sake of it.

That’s certainly the long term goal, but it seems foolish to abandon it without a solution to the problem.

>(I'd need a Lisp that runs in the browser, for starters!)

We would be in a very different world if Netscape’s exec team had let Brendan Eich just use scheme as he had planned to.

You could say the same about more or less any language feature - the thing is though that having a standard feature people can agree on is better than several people’s divergent opinions on which macros are sufficiently aesthetically pleasing.

You’re only considering the front half of the network though, classification is a helpful example for explaining the concept - but if it follows through to the output then you could quite easily imagine just shunting some activation from one branch of the representation tree to another to steer behavior. Which we already do with steering vectors - but if you could read off the actual topology you could do that with much higher fidelity.

So make one. Not everything is for you.