That is really about as undesirable a behavior as possible considering how many programs humans kill every day.
3,300 karma · joined March 26, 2015
That is really about as undesirable a behavior as possible considering how many programs humans kill every day.
I’ve heard of a few cases of devs racking up bills fast, but it has typically been due to inefficient context usage. Like they just have one super long session with Opus 1M and are getting killed with input token costs and cache misses.
With careful context management and some thought into good approaches to problems, I have personally only rarely even hit $1k in regular use.
I think the main problem with the 401k is that not enough people actually contribute to one. Or they don’t put in enough.
But I very much doubt the average person who’d invested enough over several decades in a 401k feels like they got fleeced.
But there are many funds that have different strategies, both passive and active. Such as by investing based on value, quality, dividends, etc.
I get that the average person doesn’t know this, but the 401k doesn’t inherently force somebody into broad market funds.
Also, iMessage kind of sucks too. There are many better messaging apps.
The problem is that many people in the US never even try those. They just see that Androids have green bubbles and cause problems due to SMS.
You embrace a popular open standard, add new features to your software that build upon the standard (but are proprietary), then watch as your competitors die off because customers become locked into your proprietary features.
Similar to how Apple hijacked SMS to add iMessage and introduced all kinds of features and the blue/green bubble styling.
For the longest time, they refused to support RCS, trying to keep people on iPhone by making texting between iOS and Android suck.
Of course, a lot of people switched to third party messaging apps because of how much Apple was intentionally ruining texting, so now Apple has had to adopt RCS.
So the “extinguish” part can be hard to pull off given sufficiently strong competition.
The rate of improvement has been fast. Maybe it’ll plateau soon, or maybe we’ll have LLMs improving themselves rapidly. At this point it’s too early to say.
I don’t remember where I heard it, but there’s a saying that people overestimate how much can be accomplished in a year and underestimate how much can be accomplished in 10 years.
If we get to 2030 and still people are wondering where the breakthrough is, then I think I’d be agreeing with your skepticism. But I just think it’s too early to judge that yet.
Oh the irony of telling somebody to instantaneously unsubscribe from something notoriously hard to unsubscribe from.
Me personally, I just go on the web chat every once in a while and say I want to cancel, and they give me a nice discount.
I agree that lower cost models will become a bigger priority in the near future, but I have to hard disagree that Anthropic’s strategy can be characterized as a screw up.
Sure, if they never shift with the market and their customers start moving to cheaper competitors, then it’d be a screw up.
But as of right now, producing the best coding model possible has led to insatiable demand. To the point where they’ve even eclipsed OpenAI, forcing them to change strategy to compete.
No idea why you’d say they have critically underinvested in product when Claude Code dominates and they’ve also released popular tools like Cowork and integrations for Microsoft products at an incredibly rapid pace.
Cost is becoming more of a factor, and no doubt they’ll work on that. There’s no reason to think they won’t be able to release cheaper models if they optimize for that rather than improving performance.
Eventually either the supply will go up or companies will start buying fewer overpriced GPUs.
Either way, the price per token will come down as hardware improves and supply and demand reach equilibrium.
Supply will eventually catch up with demand. Then the prices will come back down.
It was a strategic mistake for Apple to not focus on gaming. But realistically, the AVP was always going to be way too expensive for basically anything.
Maybe if you could pick one up for like $800 and there was a lot of great 3D immersive content, it could take off. But even then, I feel like it’s just not a product category the average person is that excited about.
There is an incredible gap in the search literacy between different users of Google. Some will accept what they find in the top links, no matter how dubious the source.
And Google is trying to make something affordable enough for a mass market, ad-supported audience.
They aren’t hyper focused on enterprise like Anthropic is. And that’s okay. There’s room for different players in different markets.
The price and lack of content and developer interest have been the main problems.
And ultimately, people just don’t seem that interested in this product category. Meta ran into the same issue, though at least they targeted gaming where there is a decent niche.
VR/AR tech seems cool and futuristic, but hasn’t quite found its killer app yet.
Though if you look relative to the team size and resources going into it, a project like Deno can still be considered ambitious. Creating an alternative ecosystem to nodejs is a large undertaking.
There’s no way they had time to review the code. This just seems so wildly irresponsible for such an important and high profile project.
But it is used to implement various parts of Windows, such as the File Explorer, so any improvements are helpful for general system performance.
98: great. ME: bad. XP: great. Vista: bad. 7: great. 8: bad. 10: great. 11: bad
I also wish that they’d make WinUI work on macOS as well similar to Avalonia, but I think they probably won’t.
Not to mention that there are differences in ecosystem, familiarity, and ergonomics that may make a team want to stick with Python.
“Just use Go” is not really actionable advice in most cases.
If it’s very large, especially if the tool needs to refer to documentation for a lot of custom frameworks and APIs, you often end up needing very large context windows that burn through tokens faster.
If it’s smaller or sticks with common frameworks that the model was trained on, it’s able to do a lot more with smaller context windows and token usage is way lower.
They’ll still use even smarter LLMs badly no doubt, but I’m thinking that maintainers of open source projects will be able to more effectively use LLMs to review potential PRs to weed out the truly bad ones quickly.