That link isn’t really easy to find from the home page is a large part of the gripe here. You have to click About in the footer, remain curious enough to click All Docs on that page (which Pricing isn’t usually a part of “docs”), then all you get is a Pricing paragraph that says “Plan options for individuals, teams, and enterprises.” Not very helpful until you realize the heading text “Pricing” is a plain colored link to this pricing page with more info. The whole UX of this site is garbage and what has fostered so many gripes here.
> Probably not. All side effects need to go through the js side. So you can alway see where http calls are made
That can be circumnavigated by bundling the conversations into one POST to an API endpoint, along with a few hundred calls to several dummy endpoints to muddy the waters. Bonus points if you can make it look like an normal-passing update script.
It'll still show up in the end, but at this point your main goal is to delay the discovery as much as you can.
As soon as you hijack the fetch function (which cannot be done with WebAssembly alone), it's going to look suspicious, and someone who looks at this carefully enough will flag it.
> The transformation of humans to spherical shape is gluttony not evolution. They should be forced to ride a bike until their silhouette returns to that of a human.
...GP's comment is a play on the "spherical cow" physics joke, and how models *will* have some unrealistic assumptions baked in, just so that the maths is easier to crunch through.
Counterpoint: Such a market *technically* already existed outside of FIFA, just that it was a more underground/grey/black market.
Strictly speaking, an external market being brought into existing ticketing systems would be net-neutral, since the following pros & cons should balance each other out:
(additional visibility into ticket prices & demand (+)) + (increased assurance of "this is the one place to get a ticket" (+))
==
-( (increased competition for a ticket (-)) + (perverse incentives of platform to increase ticket prices (-)) )
But because of their reputation, the negatives are weighed more than the positives due to their existing track record.
As such, the following constructed scenario should be considered: If it was a fully automated platform external to any party that handled such ticketing systems, would such a severely negative view still hold?
As noted by the other comments, Apple's M-series chips seem to use a 128-byte cache line. ARM doesn't mandate that their licensees must use a pre-specified cache line size: 64 bytes just happens to be the consensus-arrived standard.
> Any reason to believe Google's unit economics on AI are any different than the other players here?
Only when it comes to their TPUs, and sometimes that one thing may just be the difference to push them over the hump.
Per-token cost-wise, TPUs (& specialized processors in general) will beat GPUs every time. The efficiency difference between the 2 types is never to be ignored, & is likely why they can shotgun it everywhere.
> And Google is an advertising company. Mostly in search, and increasingly dependent on YouTube. Everything else is a net money loser, including Waymo, Gemini etc.
1) Each venture should be treated as a (relatively) isolated vertical slice
2) 9 out of 10 times, a venture just doesn't break even. That's just the nature of the business.
https://exe.dev/docs/pricing