Hacker Newsnew | past | comments | ask | show | jobs | submit | ta988's commentslogin

rigidity

Personally betting on the "crab bucket" mentality.

The question is, do they wear faster than they become obsolete, as in much more expensive to run than buying a new one with higher compute/watt. (and you can also factor in the ability to run latest models at usable speed)


It’s complicated. When you design with modern PDKs, you consider the expected duty cycle of the device, expected temps, and the wear and tear on the silicon all together. That affects the layout of the chip as well as certain choices about widths of various features. Generally, one designs consumer SoCs to last 10 years with the expected duty cycle (low). With more wear you could run out of your “years" much faster, maybe even before the warranty.


Apple has done the exact same with its iphone app store, lots of companies got shut down because of their app not beeing available anymore with no explanation. The problem is with exclusive app stores.


I don't often praise Apple, but their kernel hardening on macOS has been in the form of a deliberate, decades-long plan to move kernel extensions to userspace by providing the appropriate SDKs. Meanwhile Microsoft is running around like a headless chicken.


Apple requires notorization for applications outside their store too.


Word on the street is that Anthropic is roughly at half that. Hard to know what they include and not, and what their real, non-subsidized costs are.


yup and begging for retailers money.


that's why they have to open through banks and other less valuable more sliced share system.


You are assuming they have things to hide about QC...


I want that on my waffler


They can't fix it if claude code isn't up, nobody understands the code anymore. /s(a little)


But how much of that is real as in has measurable positive impact vs random decision making.


That sounds like a problem with the people producing and consuming the messages, not a problem with the protocol itself :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: