I don’t see anywhere that it’s something they specifically decided not to support. Probably they just haven’t gotten around to it yet? Multithreading is notoriously difficult to get right.
It says it isn't supported right in the readme. Just isn't clear on the "why" yet. Not getting to it yet is my hope. I maintain 14+ highly threaded ruby services atm, for context.
The EPA push for fuel efficiency made it easier to hit targets by selling huge trucks instead of small cars.
There is a value in safety regulation but the incentives as legislated have led to negative results. It needs to be fixed or repealed. Not sure there's a clean solution here.
Would it be possible to increase the cache duration if misses are a frequent source of problems?
Maybe using a heartbeat to detect live sessions to cache longer than sessions the user has already closed. And only do it for long sessions where a cache miss would be very expensive.
Because other than SWEs, very few other segments extract significant value from cutting edge AI at present. I suspect that for the average Joe conversing with their chat, GPT-4o was more than adequate (and really, when OpenAI tried to phase that out, the public revolted and they brought it back in).
So companies might pay good money for these models for programming but elsewhere, I don't see where they capture particular interest yet.
New companies can enter this space. Google’s competing, though behind. Maybe Microsoft, Meta, Amazon, or Apple will come out with top notch models at some point.
There is no real barrier to a customer of Anthropic adopting a competing model in the future. All it takes is a big tech company deciding it’s worth it to train one.
On the other hand, Visa/Mastercard have a lot of lock-in due to consumers only wanting to get a card that’s accepted everywhere, and merchants not bothering to support a new type of card that no consumer has. There’s a major chicken and egg problem to overcome there.
Gigawatts seems like more a statement of the power supply and dissipation of the actual facility.
I’m assuming you can cram more chips in there if you have more efficient chips to make use of spare capacity?
Trying to measure the actual compute is a moving target since you’d be upgrading things over time, whereas the power aspects are probably more fixed by fire code, building size, and utilities.
Measuring data centers in watts is like measuring cars in horsepower. Power isn't a direct measure of performance, but of the primary constraint on performance. When in doubt choose the thermodynamic perspective.
I mean a single nuclear reactor delivers around 1GW, so if a single datacenter consumes multiple of those, it gives a reasonably accurate idea of the scale.
I have expensive online subscriptions to New York Times, Wall Street Journal, and Washington Post. Nevertheless they are FILLED with ads/popups/videos that run automatically/dark patterns. Just saying: there's no refuge.
True, but that doesn’t invalidate what I said about the vast majority of sites that aren’t globally known, prestigious news companies that people are willing to pay an expensive subscription for.
Most publishers of content online are ad supported and struggling, and I want to make sure I’m contributing to their revenue somehow.
I don’t feel bad about blocking ads on sites I pay for though.
we live in a wholly unoptimized world because the available resources have been so high, while the benefits of optimizing have been so low. that has flipped now and there are tons of low hanging fruit to optimize.
I agree that benchmarks would be great, but thats only relevant to this one topic, not the overall agentic coded pull request concept itself
It's relevant in that it's an example that people are doing the easy part - the coding - and skipping the hard part - the benchmarking and proving it works and provides value.
A PR without evidence it works and expectations for the benefits using the new feature would bring is kind of worthless.
Who says it works if the “author” isn’t thoroughly testing and reviewing it?
People who do this want the fun part of pretending they’re implementing a feature without actually putting in the hard work it takes to make something for real.
They want the repo maintainers to do all the hard, boring parts while they have fun. As if maintainers of open source projects don’t have enough thankless work on their plates. Good luck with that!
reply