This is about sane, stable defaults. If you want the extra performance far beyond the CPUs sweet-spot it should be made explicit you're forfeiting the stability headrooms.
945 karma · joined March 21, 2013
This is about sane, stable defaults. If you want the extra performance far beyond the CPUs sweet-spot it should be made explicit you're forfeiting the stability headrooms.
And yeah, having Arrow Lake running at its defaults is just a waste of energy. Even halving your TDP just loses you roughly 15% performance in highly MT scenarios...
Not a coincidence, though - these two still use those legendary OM602/OM605 diesels of its predecessor series.
Interestingly, most benchmark controversies back in the day are now expected behaviour, i.e. game-specific optimizations with no (well, in this age of upscalers and other lossy optimization techniques, probably even somewhat) visible image degradation. A gaming-specific driver with no game-specific improvements in its changelog would be considered strange, and it very much works with executable detection.
Back in the day, there was still the argument that drivers should not optimize for benchmarks even when visually identical, because it wouldn't show the hardware's real world potential. Kinda cute from today's perspective. :)
But of course there were the obvious cases...
The Quack3 lowering filtering quality as shown above, of course (at least that one was put into the driver as a togglable setting later on).
But the most cheeky one has to be nVidia's 3dmark03 "optimizations", where they blatantly put static clip planes into the scenes so that everything outside the predefined camera path from the benchmark sequence would simply be cut from the scene early (which e.g. fully broke the freelook patched into 3dmark and would generally break any interactive application)
The loss of compatibility wasn't even the biggest issue here - it was the loss of functionality. WM6.5 had a huge enterprise feature set, only rivaled by Blackberry (and probably Nokia to an extent). Then came WP7 and had...literally nothing. They didn't even support Exchange ActiveSync in the beginning.
This was enough for a not insignificant number of devs to drop out of the already small market and lower the already limited app supply even more.
From the perspective of a European carrier back in the day: This would probably have been true in the early iOS/Android days, but by then we were wayy in the "There's an app for that" era. All metrics we had back then showed potential app availability being the tie-breaker and the "WP has no apps" perception the biggest reason for consumers to avoid it.
This presumes that the human mandating tool use, the human making the mistake, and the human held responsible are one and the same.
And yeah, you can see with those two latter terms where the issue lies :)
Those two were traditionally actually used this way in the safety and security context - I think I even have the script for the "Datenschutz und Datensicherheit" lecture I had on uni in the '90s lying around somewhere in the attic.
But their meaning has changed and muddled so much over the years - probably not helped by the fact that "Sicherheit" is much closer to "security" in colloquial usage, and probably vice versa(?) - that they stopped being useful and used in this context.
As someone who has a lot of .NET projects at work it's a bit of a bummer since the dogfooding would have been a huge benefit for .NET, but I honestly can't argue with their choice.
It's just something the writer of the article should probably have at least mentioned when going full hyperbole with the title (hey, after reading this, it might actually be justified! :) ).
Rereading the article that focuses on the one thing that isn't a standout (the installation itself), though, I can't help but chuckle and think "worst sales pitch ever". ;)
sigh At least try to look for examples that aren't so completely, utterly wrong. Which "flying jet aircraft" would that even be? The only one where you could even start to make that argument would be Heinkel's He178 prototype. Apart from the fact that it was explicitly designed to be monetized militarily...where do you think those funds came from in late 30s Germany, at one of the leading military plane manufacturers? (and please don't say Lufthansa...they didn't operate on a "free market" even since their inception in 26, and certainly not after 33).
You can't spell jet aircraft without military-industrial complex. Hell, even the first 707 family variant in service was a military one (KC-135).
Edit - almost overlooked that nugget:
>Externalities, such as pollution, are not free market, and are in the purview of government.
Ah yes, privatize profits, socialize costs. That kind of free market. I shouldn't have bothered.
Very true, or as I like to put it: everything is a tradeoff.
Over decades of programming, I'm fairly certain my preferences for things like function/identifier length could be plotted along a damped oscillation curve. :)
I could recite lots of personal accounts of perfect service from Lenovo/HP/HPE business service (Mainly X/T-Series at Lenovo, Elitebooks/Z Workstations at HP, Proliants and general server/networking infrastructure at HP and later HPE) and terrible "business" service from Apple. Then what?
>The difference is that Apple actually rolls out repair programs and has the infrastructure to fix things in a relatively consistent way. You can take a broken machine to a store, talk to someone who can usually solve your problem, and almost always walk out with a solution.
And that's an idealized version not consistent with reality. "This is not an issue on our side" (very much related to my examples) is not a solution. Hell, in enough contexts "Bring in your device, we'll look at it, maybe repair it and you can collect it sometime later" isn't either (and for the longest time Apple didn't offer anything else - oh, and BTW: at least here in Austria, Apple Care Enterprise on-site is very much done via subcontractor...).
>Pretending other vendors are more accountable just doesn’t match reality. They’re not immune to problems. They’re just a lot better at quietly ignoring them.
Neither is this. Again: repair programs/recalls and associated infrastructure aren't exclusive to apple, they are expected standard in business service. And begrudgingly doing those recalls after (or shortly before) a judge orders you to isn't the high standard you seem to make it out to be.
Too bad you had an issue with your on-site technician - but honestly I don't understand why you allowed them to repeatedly send him back after that mess...
Yeah, and I explicitly stated that this isn't what I was criticizing.
>The difference is that Apple, after enough pressure, actually fixes things. They create repair programs, offer recalls, and have the infrastructure to make things right. Most vendors don’t.
Which simply is bullshit.
I don't know why you feel the need for a play-by-play - I know, I was affected by several of them. And every single one of them was Apple reacting only after prolonged active denial and deflection culminating in lawsuits. There's nothing to defend here. That's shitty service.
Kinda sad that that you feel the need to bring random other issues into the mix (Coil Whine, really? LOL, remember the MBP "Moo"?) coupled with outright lies (of course HP issued recall programs - for both the NVidia GPUs and the batteries).
>The service experience isn’t perfect, but it exists. With most other vendors, you’re stuck mailing your device to a third-party contractor who might show up late and leave you worse off.
No, with serious vendors, you're not. It seems you've never experienced real business on-site service. (And yes, it was still cheaper than AppleCare.) Compare that to wondering with every visit at the service center whether your problem will even be acknowledged as such or you're gonna be gaslit. (And I'm speaking from experience.)
> But pretending they’re worse than companies who ghost their customers when things go wrong doesn’t line up with reality.
Neither does pretending that's all that exists (or even being close to the norm with high-end gear).
Sorry, but this is a joke. "any other vendor did not care to stand behind their product"? Give me a break.
Apple has been time and again the champion of denying issues with their products until lawsuits forced their hand, often settling without admitting wrongdoing. Bendgate, Batterygate, MBP nVidia, MBP AMD, Butterfly keyboard, just off the top of my head. (Again: My criticism here is about how Apple handled them.)
"You're holding it wrong" is a meme for a reason (that didn't result in a lawsuit, though IIRC)
All those off-center keys have been grouped, offset and/or specially shaped since ages for a reason - to immediately and unambiguously settle your fingers there with minimal error when you have to move you hand away from the homerow anyway.
Exactly this. I've given up hope to expect an old-school TP keyboard with its ridged concave keys providing perfect tactile feedback even when not depressing a key, but there's basically no standard laptop layout out there anymore optimized for efficient touch typing, with existing consistently grouped and offset(!) off-center key groups (4-group f-keys, pgup/pgdn/home/end cluster, arrow keys). And some key travel to go with tactile scissor keys to reduce bottoming-out would be nice.
(Oh, and why I find the "tactile feedback" so important, see the wonderful "Pictures Under Glass" rant.
https://worrydream.com/ABriefRantOnTheFutureOfInteractionDes...
Not directly related to keyboards, but the premise remains the same. Hands feel things. :) )
Among a few: The keyboard switch from the old 7-row (whose pinnacle was at the x220/T420 era with double-height esc and del) to the new 6-row (with later ever decreasing key travel) to the current x9 (which is basically just a yoga keyboard with no trackpoint, no key grouping, and the loss of pgup/pgdn). Things like the modular battery options vanished. The case got flimsier over time with e.g. the magnesium rollcage first vanishing from the display, then from the base. (And no - from enterprise experience - the carbon fiber composite isn't generally "as good or better", esp. for failure modes like punctual force on the display. Or...grabbing the laptop by the display and using it to fan your BBQ, which doesn't faze my old X41 :) ).
Where MS actually did groundbreaking UI/UX work was in the 00s, ironically for most things not Windows - Media Center, Xbox 360, Zune/WP.
And of course they had to ruin it with botched product management and their bulldozing Metro/UWP everywhere strategy. The Windows 8.1 UX on a tablet was actually pretty good. Too bad it a) sucked on everything else, b) app integration was spotty due to relegating Win32 to second class.
(from book in books
where book.pagecount > 100
&& book.language == "Chinese"
&& book.subject == "History"
&& book.author.mentions > 10_000
from pet in book.author.pets
where pet.is_furry == true
select pet.favoriteFood)
.Distinct()
But it also demonstrates the...erm, chronic "halfassedness" of LINQ's query syntax form with distinct() not available there and having to fall back to method syntax form anyway...That's the biggest "what if" omission of the TMS9918 for me - I wonder how the 8-bit landscape would have evolved if it had even minimal support like the scroll registers of the VIC-II...