Same. But even worse than all that: OAI erased Anthropic's red lines with the DOW, making it socially acceptable for every other AI company to do the same, creating a "race to the bottom."
I think OAI actually legitimately increased p(doom) for us all. Very strange behavior for a company that is supposedly concerned about x-risk.
2. Shit goes to 0. Your 401(k) invested into S&P 500 takes a dive (dump phase)
3. Retail holding bags (full of shit) phase.
Case study: Tesla, with a P/E ratio in the hundreds along with declining sales and TAM, is a part of the S&P 500 and, consequently, of many people's 401(k)s.
Well... in normal times they would be entering at the bottom of the index due to the company beginning to grow, the purchase of which is being funded by a firm exiting the index due to shrinking, so assuming you have bought and held units in the fund, most of the time an index fund is buying low and selling low.
And then when you sell your units, hopefully in aggregate the index is worth more than it was when you entered...
> It's really hard to justify $1000 for it when the Switch 2 is $450
For someone without an existing library, sure, but if you have a massive existing Nintendo/Switch1 or Steam library, that's going to drive your decision making far more than the price tag.
I think that's a factor for sure, but is less important (generally) as the price gap increases. The Steam Deck also has a disadvantage in that only some of your existing library will be playable on the device.
There's definitely a price point for some where it will make sense to rebuild your library on the Switch vs pay the higher cost of a Deck.
The nice thing about the Switch 2 is you can find a plethora of games at your local library (if you have one, that is). That's essentially how my wife played 20+ games with her Switch 1.
I watched a three hour video interviewing gaming hardware companies. One thing that came up was that pricing fluctuations don't actually mean anything in a market with zero liquidity. "When ram prices dropped 5%, recently, they probably only sold 20 units at that price."
I think feature flags, remote configs, and experiments are all the same thing. Semantically they differ in how you're applying the config and interpreting the outcomes.
>> Of course it writes a lot of code. It gets paid per token.
I don't buy it. I think a much more likely reason it leans towards adding code is because deleting code carries inherent risk: it can break things in major ways or minor ways or very visibly or invisibly. Adding new code, on the other hand, is a lot safer: the only parts that can break are those the AI touched inside its own working context. So it doesn't have to go down rabbit holes and potentially create bigger and bigger messes.
Then local models shouldn't suffer from the same problems, but they do. They just aren't trained in the direction of "less code == better long-term maintainability" I'd say, rather than some grand "increased-token-usage" conspiracy.
You can certainly steer them a bit to reduce the issue parent talks about, but they still go into that direction whenever they can, adding stuff on top of stuff, piling hacks/shim on top of other hacks/shims, just like many human developers :)
Training data is the masses of code from everyone.
Restrict that data to just the best of the best, the tersest of the tersest, and we’d see better output. I don’t think people are sharing that kinda stuff (Jane Street’s gems stay locked up), and even if they did my presumption is that it’d be too narrow and demanding for general audiences.
Big hopes for the long future, damned to some degree of mediocrity in the near term mass product.
Anyone considering leaving AWS and thinking they'll transfer all their data for free [1], I've got news for you: It's a lie.
AWS takes as long as possible (for me it was a month) to respond to the initial DTO request,
then require you to submit a multi-page form answering a barrage of questions about why you're leaving, where you're going to, what services you used, and estimated data egress. A week or so later, if they approve the request, you're not allowed to begin DTO until 60 days after the approval.
By the time you can egress your data for "free", you've been stuck on AWS for 3-4 months since you first made the decision to leave.
I might be reading the pricing wrong but you have to pay per hour for the port plus per GB transfer? And looks like the cheapest is $0.02 per GB? Is that really the 'cheap' option? That looks fine for a TB or two, but still crazy when getting closer to PBs.
But to be fair, I deal with several customers that are in the double digit petabyte scale. When you’re operating at that scale, and have 7-figure AWS bills on a monthly basis, AWS is suddenly a lot more available to you and much more willing to accommodate pretty much anything.
I've heard stories of bills like that and is wild to me.. I built a SaaS that had just over a PB in data and our monthly was low 5 digit and largest part was S3, and co-location was already on the table. I can't imagine getting to 6-7 digit a month.. I understand how it happens with rapid growth, but even 6 months of that I would be scrambling for other hosting options.
You do but you can actually negotiate discounts with AWS when you get to Direct Connect level. It's only cheaper than the other options. It's never acceptable.
This is why we're slowly and quietly moving back to a couple of cages in a DC. Well we were until the AI companies bought all the fuck RAM and SSDs.
1) Brockman ($25M) and Altman ($1M) both personally donated to Trump/MAGA.
2) Anthropic pushed back against DOD's demand for unrestricted use of AI to kill people while OpenAI eagerly said "please use ours!".
reply