Objection. Your React is ultimately turning into HTML so you DO have to learn HTML + CSS. You just have an abstraction over it.
Objection. Your React is ultimately turning into HTML so you DO have to learn HTML + CSS. You just have an abstraction over it.
The big AI corps keep pushing depreciation for GPUs into the future, no matter how long the hardware is actually useful. Some of them are now at 6 years. But GPUs are advancing fast, and new hardware brings more flops per watt, so there's a strong incentive to switch to the latest chips. Also, they run 24/7 at 100% capacity, so after only 1.5 years, a fair share of the chips is already toast. How much hardware do they have in their books that's actually not useful anymore? Noone knows! Slower depreciation means more profit right now (for those companies that actually make profit, like MS or Meta), but it's just kicking the can down the road. Eventually, all these investments have to get out of the books, and that's where it will eat their profits. In 2024, the big AI corps invested about $1 trillion in AI hardware, next year is expected to be $2 trillion. Only the interest payments for that are crazy. And all of this comes on top of the fact that none of the these companies actually make any profit at all with AI. (Except Nvidia of course) There's just no way this will pan out.
How does OpenAI keep this load? I would expect the load at 2pm Eastern to be WAY bigger than the load after California goes to bed.
I wonder if that's related to this.
So now it's 2 cables: 1 from the hub, 1 from the monitor. Both USB-C.
WTF guys?
My Apple monitor from 2009 just worked with 1 cable (no power, but still).
* waterfall
* design up-front
* source control systems that
* defaulted all files to read-only
* required you to "check-out" files, potentially locking other devs out from editing them [1]
* probably didn't have unit tests so "deploying to prod" meant "doing a full QA pass, done by human beings"
* there was no CI/CD (We had "Build Engineers")
In this context, pushing a change to SVN/git/hg, having tests run automatically, then having CI/CD push new code to production, all as a side-effect of one engineer push a button? That was moving fast, and occasionally, breaking the whole website. But we got better tests, better CI/CD, metrics, green/blue, ... We learned it was unequivocally better than the old way.[1] Reserved Checkouts: https://www.ibm.com/docs/en/clearcase/11.0.0?topic=ucm-check...
Didn't they change names months ago? I know them as Codeium.
In theory, react developers ought to be able to code against the react API in typescript, without seeing the "raw" HTML+JS that gets delivered to the browser.
So what's failing those developers? Is it the tooling, the abstraction itself, or something else?
Probably helps a lot to keep abstractions from leaking.