Problem is, display profile support for Wayland has been, at best, spotty until recently - and, there should be multiple accurate targets available on any good display panel.
My factory-seconds F13 (using 11th-gen Intel, still the best in terms of power savings) shipped with the older glossy display, which had a known, disclosed-as-cheaper LUT issue at lower brightness settings. After a couple of calibration rounds, it is spot-on and my go-to PC laptop.
Decent keyboard, too.
Of course, things are often more expensive in Europe (compared to the US) for zero good reason, so the F16 will always be at a proportional disadvantage compared to the F13. You may find that a much better fit.
Somewhat tongue-in-cheek, there will be three or four development tiers left:
1. model development and optimization,
2. data pool management,
3. downstream consumers of item 1, and
4. everything else
The conclusion of the article says that it's not the language problem either. Under the title "So, is Go the problem?" Or do you mean something else here?
Given that the title implies the opposite, I think it's a fair criticism. Pointing out clickbait might be tedious, but not more so than clickbait itself.
My factory-seconds F13 (using 11th-gen Intel, still the best in terms of power savings) shipped with the older glossy display, which had a known, disclosed-as-cheaper LUT issue at lower brightness settings. After a couple of calibration rounds, it is spot-on and my go-to PC laptop.
Decent keyboard, too.
Of course, things are often more expensive in Europe (compared to the US) for zero good reason, so the F16 will always be at a proportional disadvantage compared to the F13. You may find that a much better fit.
reply