There still may be Opus->Fable type bump when they finish training larger models. Remember, Grok 4.6 is still Opus-sized and they have larger models in training.

"Claude did implement multithreading in JS but we don't want to mantain a fork of WebKit" - jared apparently

Just @AGENTS.md should be enough, as @s is CLAUDE.md are inlined (and !`ls` are executed)

The ones who accept rewrites are expected to support it indefinitely.

That's why Jared didn't consider using it for Bun even if it's undeniably better, they don't have human resources to support it

1. Owning your own company stock is not having money, it's merely ability to control the company. Elon tries to be BDFL of his companies, so selling the stock is not really an option.

2. Stock valuation and money are not the same thing. As you could've noticed from the recent Bitcoin price drop, the moment you start selling it it starts to worth less. Tesla is bubble-priced, so it's sell price is at least 5 times less then valuation

3. Even if you get the money, distribution is much harder problem then you think after agreeing with this sensense. IIRC it was Musk who said "So you say you can fix the world hunger for $nnn? Bring me the plan how you are going to do it. Noone brought me a plan so far".

Sure. If you completely ignore the ability to borrow against your assets at extremely low rates. And those assets include stock.

Since I know russian well, here's a proper translation for y'all

    FUNC FACT (N);
       NAMES: P;           (* variable names *)
       1 -> P;
       FOR I FROM 1 TO N ::
          P * I -> P
       DONE                (* endif *)
    RET: P                 (* return value *)
    END;                   (* end of function *)
    
    FOR N FROM 0 TO 6 ::
       ? "FACT(", N, ") = ", FACT(Н)   (* print *)
    DONE;

If it's purely bot traffic, then Anubis could help

You could have seen it on some websites already

https://anubis.techaro.lol/

anubis only works against lazy scrapers, and at a cost to your users. I'd prefer people not use it.

Bot traffic comes from machines that usually have a lot of idle cpu (since they're largely blocked on network IO as they scrape a bunch of sites in parallel), so they can trivially solve the anubis "proof of work" challenge, save the cookie, and then not solve it again for that site.

The only reason scrapers don't solve it is if the developers were too lazy to implement it... and modern scrapers also do, codeberg stopped using anubis because modern scrapers were updated to solve it.

The "proof of work" has to be easy or else people on old cell phones couldn't access your site (since an old android phone would start to overheat and throttle trying to solve a challenge that would take a modern server even several seconds), and it also consumes your cell-phone user's batteries, which is a really precious resource for them compared to the idle cpu on a server.

Just to add to the two negative replies, I find Anubis to be the only system that doesn't ever get in the way. My browsers have Javascript enabled and, so far, it never took more than a fraction of a second to complete the checks

Every other system I've run into has constant false positives, e.g. Google captchas will sometimes say I've failed and make me do the hardest level (if it wasn't giving me that already), Cloudflare regularly thinks I'm a bot, Codeberg blocked me before, Github signup captchas used to take ~15 minutes to complete and then still said "well you failed, try again", Github's general rate limiting has false positives (some days I browse a lot, other days little, and on the little days it'll sometimes go "slow down" with no recourse whatsoever, you're just blocked for an indeterminate amount of time), OpenStreetMap blocks my browser at work because I'm using Firefox ESR instead of latest stable and it finds that user agent string to be implausible, whatever the german railway operator uses since a few days is triggering on me constantly, etc.,

etc.,

etc. Constant blocks everywhere.

With Anubis, my understanding is that you do the proof of work (with whatever implementation you like, it doesn't have to be the Javascript one that they provide) and you can move on without ever doing any task yourself. The power consumption is a shame, but so long as attackers aren't even doing this much, the couple Joules it takes doesn't seem to be an issue

Of course, the attackers will evolve, but for now...

Please no. I'm a non-bot who gets stopped and turned away all the time by that menace. Anubis doesn't work without JS.

One of the things I give duckduckgo a lot of credit for is that while they're quick to interrupt me for a bot check (sometimes multiple times in a span of minutes) they'll let me identify ducks even on the most locked down browsers I use.

The amount of compute you get is not documented anywhere.

Cursor docs do say "You get $70 of api priced tokens on $60 tier"

Anthropic limits were 8.33x with free cached tokens, but those numbers themselves were a leak rather then an official statement

Cursor may be losing money only on $200 sub people who do over $200 of usage (it grants $400)

Everyone else pays them at API prices

And then you have a

    const CatDog = { bark(){}, meow(){} }

and

    const TreeCat = { bark: "oak", meow(){} }

and your code stops working

To make types discriminatable you need either

    type A = { bark: fn, meow?: never } | { bark?: never, meow: fn }
    type B = { species: "dog", bark: fn } | { species: "cat", meow: fn }
    or use instanceof with a class