My one suggestion is that you might want to allow people to jump into the harder lessons right away vs having to go through the basics. The first few lessons being simple selects wasn't the most engaging. Just a suggestion!
You can't compare an API that is profitable (search) to an API that is likely a loss-leader to grab market share (hosted LLM cloud models).
Sure there might not be any analysis that proves that they subsidized, but you also don't have any evidence that they are profitable. All the data points we have today show that companies are spending an insane amount of capex on gaining AI dominance without the revenue to achieve profitability yet.
You're also comparing two products in very different spots in the maturity lifecycle. There's no way to justify losing money on a decade-old product that's likely declining in overall usage -- ask any MBA (as much as engineers don't like business perspectives).
(Also you can reasonably serve search queries off of CPUs with high rates of caching between queries. LLM inference essentially requires GPUs and is much harder to cache between users since any one token could make a huge difference in the output)
Thanks for saying the quiet part out loud here -- everyone wants to believe in education improvement but there's a harsh reality of the industry that is pretty unpleasant to confront.
I think the only hope would be to run a pilot and show such an improvement in student testing levels that it would be fast-tracked or mandated for approval.
Surprisingly large number of people at the beach for San Francisco (which is usually pretty cold).
These digital remasters give me a bit of an odd feeling though -- the technology to film at 60fps didn't even exist during this time, so seeing such high-resolution footage feels anachronistic.
This is the best explanation for both async/await and hooks that I've ever heard, thank you!
It also shows that although there might be some learning investment required to use the more modern version of both, it's well worth the effort. I can't imagine going back to callback-riddled javascript
Ever wanted to hear a spicy debate on any topic by some former presidents? Well now you can via the magic of ChatGPT, ElevenLabs, Three.JS, and React Three Fiber!
The founders can answer better, but a lot of traders are not just looking at individual stocks but rather packages of stocks together.
Say you want to invest in the health + tech space, but there's some risk that covid ends and gyms come roaring back. So then you want to minimize the risk by putting some money in the gym industry as well -- getting an entire package of peloton, apple, and 24hourfitness stock is actually worth more to you than the individual stocks on their own.
For those who want a rough programming analogy here -- this sounds like support for multi-row transactions in a SQL database where only single row edits were allowed before.
Now you can describe "buy goods A and B at $10 maximum, commit" and have the transaction either succeed or fail. Before you had to edit those rows individually and there's risk that you end up in a weird partial state, hence having to lower your bid to cover your risk.
Really exciting tech and it'll be great for these costs in market-making to be eliminated!
Yes they are, in a sense that the outstanding mortgage debt grows at a slower pace than inflation.
However the 3% is guaranteed for ~30 years, so it's likely the bank would still come out ahead in the long run if inflation settles down. It's also not an infinite money slot machine -- you can only qualify for so many mortgages (which require large down payments) and houses are pretty illiquid assets.
The forks don't "disappear", but they get overruled since the consensus has shifted to the majority opinion of the ledger. Thus all of the transactions on a local fork (that doesn't become the majority) are wiped out -- including possibly deposits in exchange for cash.
Given the precision of the points, lexicographical order on (x,y) would essentially be lexicographical order on just x, which then induces a lot of jumping around the map.
That sounds nuts; it seems like a huge liability that they are putting AP2 in the hands of consumers when it can be more dangerous than just the average driver...
They are probably misinterpreting your comment; at first I thought you meant Levandowski was the one who invented the LIDAR components, so he should be financially rewarded outside the normal Google comp system (by doing this whole steal-then-get-acquired strategy)
http://pcottle.github.io/learnGitBranching/?demo
Want to seen an obscene use of CSS transitions? See:
http://petermcottle.com