4,904 karma · joined July 1, 2020
meet.hn/city/37.0481715,-112.5285237/Kanab
No, testing and code audits also work.
No amount of use of the software will tell you what else the software does beside what is intended (exfiltrate data, etc); testing and code audits both help with that.
These are separate problems, though. You can clean a page by updating its backing store without purging it from memory; and purging a clean page doesn’t require a write. It’s definitely reasonable to take advantage of idle IO resources to clean dirty pages, but pages should only be purged (clean pages first, usually) when there’s an immediate need for them for something else.
No, Mac laptops use LPDDR, currently LPDDR5X.
How do you figure? Assume the average Apple cell phone replacement cycle is somewhere between 3 and 4 years. At the longer end, you’d need the sell-through rate of the Duo compared to other phones to be less than 0.04% to hit your number. We know from the Mini and other phones that Apple tends to avoid designs that it expects to have less than a 5% sell rate, two orders of magnitude higher. Even if you assume they’re aiming for 5% of dollars instead of units, and you take into account the non-Apple market (which certainly should not be unit-weighted for folks thinking about app revenue), you’re off by well over an order of magnitude.
I’d wager the future lifetime spending of someone who owns a $4000 watch on other watches is at least one and maybe two orders of magnitude greater than the general population.
If the code is written by an LLM, then it can't be copyrighted, and a license can't be applied.
I think this statement is insane. The benefit of computers is that they allow complex behaviors to be defined and implemented. The benefit of software is that it’s the lowest-NRE way of defining those complex behaviors. UI doesn’t come into it, except in a few edge cases like desktop computers, phones, appliances, etc. A climate model’s “benefit” comes from its output, not the form in which it generates output or takes input.
There's lots of great software out there that you interact with every day that was written by a small number of developers to clear requirements. Your car ABS brakes. Your coffee maker. Your brushless drill. Your TV remote. Think of the fact that majority of the microprocessors and microcontrollers that you interact with every day have software that you never think about, because it just works and gets out of the way. (And think of the cases -- maybe your dishwasher, your smoke detector, whatever -- where that's not the case! It really drives home how incredibly pleasant just-works-without-thought really is.) It's only these big, large team, overly complex systems where the expectations are so low that even the crap that is a current web browser is considered acceptable, let along "not sucking."
The Macs? No, they go up to 614 GB/s, nearly an order of magnitude more.
It isn't, though. That rating is for circuit sizing. Power supplies are rated by their output power. If you assume an 89% efficiency for the power supply, and assume 1.0 PFC, and assume that it must be able to supply its rated power at the critical corner (low voltage), and assume zero margin on the current rating, then this is a 1068 W power supply. More likely its design spec is around 1000 W; it certainly can't be 1440 W.
Americans. The same population as most of the beneficiaries.