kimixa
Joined 10 years ago
Joined 10 years ago
And I generally hope that actually bills have a much higher required level of analysis of details and interactions than more general direction statements. Requiring that for every statement would just put a massive burden on the minority party, as they would have to always do that level of due diligence just to be "allowed" to propose a direction.
Or even proposing new laws by floating bills when they don't already have the guaranteed votes - or even know they'll never pass. I'm sure many here would also want to dismiss that as "pure puffery".
Really why do we let anyone but the current majority party say anything at all? It's just puffery.
For another narrative, it was 83,038 a month ago on Sept 29th, so is down 5% in one month. And one year ago it was 112,562 on Oct 29th 2025 - down over 30% in one year. Well into "bear market" territory.
Using "traditional" market indicators and definitions for things like bear/bull markets doesn't feel sensible for such a volatile market.
Now, do we think that's likely? Probably no more likely than then being "easily broken" for decades without being noticed by the academic cryptography community.
There's no getting away from the rocket equation - reaction mass is heavy. The sheer number of design compromises that need to be made to allow a cold gas thruster system means I can't see anything but ending up with an awful car for the sake of a few seconds "air time". And the rest of the time you'll still be (at least) doubling the mass of your car from the propellant plus whatever the thrusters, tanks, linkages and everything else weights. I guess you could leave it empty, then only charge it for the "Party Trick", but it still seems a lot of compromises for the occasional "Hey, this looks cool".
And then really only usable in a nice empty, flat, controlled environment - the "real world" driving experience has things like other cars, people, buildings and street surfaces that likly wouldn't appreciate what are effectively localised hurricane-force level winds from the car next to them.
This is a car rigged for a specific stunt. And there's a reason why people don't just drive around rigged stunt cars. They suck as being "cars".
Development and improvement is often very non-linear, assuming you can extrapolate forever is just as much guesswork as claiming it'll never change.
So I wonder if it's the other way round, Epic rushed out the boast because they knew the window that it would be even remotely correct to most users was closing.
I can see one of Nvidia's biggest fears is the inference hardware becoming commoditised.
This suggests it may be the source for over a quarter of all environmental micro plastics [0]
Some reports suggest it could be even higher, this article [1] references a pew report suggesting tyres could be the source for over three quarters of the micro plastics found in the ocean.
Though it's not as if they're just driving around for fun (most of the time), but not costing these sort of externalities means the market doesn't realistically consider alternatives even if they "should" be more efficient, so "cheaper" when all the /real/ costs are added up.
[0] https://www.port.ac.uk/news-events-and-blogs/blogs/protectin...
[1] https://www.euronews.com/2023/10/02/toxic-tyre-dust-this-sou...
Trying to separate out "per token" costs and possible profitibility from public information feels like a exercise in futility, it's too easy to play games with costs by trying to separate things still fundamentally required to actually have anything to /sell/ in the first place, like R&D and training. Even the current "Open Models" are somewhat loss-leaders, often reliant on significant funding and benefits from governments etc.
I think the only time we can /really/ judge the "true" break-even point is if the whole company breaks even.
I think one of the big differences is that the "Gate Contact Area" simply isn't the smallest "feature" anymore - but the ITRS that defined those names called it "feature size", not "gate size" from the beginning intentionally.
You probably could make a transitor with a gate size of a similar order to the "feature size", it'll just perform awfully to be completely useless.
It's not like ReBar is a single toggle "Make Things Faster", but a different option in how it can map gpu memory to the cpu. The driver still needs to use it - and decide where it's use vs the "staging buffer" approach would actually be be benefitial.
I do somewhat wonder if people's opinions about this would survive the current incumbent changing. From previous experience, I have my doubts.
> They don’t. They’re introduced all the time and then edited and revised.
Trying to claim that revising a bill based on feedback is the same as "no need to consider those specifics yet" is crazy to me.