8,577 karma · joined July 21, 2009
>Wether you like it or not, it's a significant step. Modulating content to maximize the attention-reach of your audience is scientifically significant. Again, that we use this for bullshit is a side-effect of your broken and time-local culture, it doesn't invalidate the progress we made along the way.
One of the most significant applications of Einstein's work was to vaporize hundreds of thousands of Japanese civilians.
I think the most surprising thing to me is the lack of interrupts. If you read this, jstanley: did you struggle much with that decision? I think of interrupts as nearly universally available on 8-bit micros, much less 16, but I have also wondered before how important they really were for what those machines ended up being used for. The (S)NES polled their controllers' shift registers in a really inefficient way, but it turned out fine. On the other hand, though, the vertical blank interrupt was pretty critical to their software and, of course, it became extremely common for NES cartridges to add extra chips to raise interrupts on particular horizontal scanlines. But, aside from neat graphical tricks, maybe interrupts just weren't all that important?
Not only that, but, IIRC, they charged more for a PC bundled with OS/2. This was a result of all the groups within IBM having been moved toward being run like individual businesses. So, the OS/2 business charged the PC business (whom they treated like any other customer) more than Microsoft charged for a copy of Windows.
At least that's what I heard at the time.
EDIT, upon reading the bottom part of the first page of the linked article: And double the cache, more cores on the Neural Engine, and maybe doubled media processing, assuming I'm reading all of that correctly.
I don't have statistics on it but it seems very likely that the latter model gets hugely more uptake.
Where? I don’t see that in what they wrote.
But maybe there's an extra complicating factor of TSan causing significant performance penalties making it impractical for it to be on in release builds?
- Things might be less likely to break. Certainly the default settings are the most likely to have a test case associated with them. How likely is it that there's a test case around the unique combination of the 35 parameters you've configured that are relevant to the particular operation you're attempting?
- It may be better. A number of times I've heard of some odd default and thought "that's obviously wrong" but given it a chance and learned to like it. Definitely change things that really are important to you, but vendors often put a lot of effort into making good defaults.
- If you're a developer, a less configured system is more likely to be similar to what an average user uses, giving you a more similar experience to them.