Lenovo announces the first Arm-based ThinkPad

Sorry, but no. This is the kind of misinformation that causes people to wind up with $2000 paper weights.

ARM in the cloud and ARM on the desk-top (aka, SBC and Laptops) are nearly entirely different ballgames - certainly from a user UX perspective. Basic boot support, standards around device tree, actual driver support, firmware, quirks, ecosystem challenges due to vendors and the nightmare of a gazillion kernel forks.

I was actually shocked to see that Snapdragon 8 Gen 1 already has upstream support, but AFAICT that's not a tablet/laptop chipset. And the one that is again seems to only be seeing Windows support. The other mobile chipsets with decent suppor are few and usefuls even fewer - maybe three and that's including Librem/Pinephone.

Maybe you can find me an example of the 7c/8c running, anywhere? There are at least some DTSI for some 7c boards, but again, absolutely zero consumer hardware in the wild. I spend time every month looking and the options for running a proper upstream kernel, on an Android based laptop or kernel, and every time "upstream support" is added as a crtieria, the options drop to zero.

I've never wanted to be wrong so much before, but again, I look into this pretty regularly and am involved in some development efforts that expose me to some of these realities first hand (I run everything on aarch64 except my gaming PC). It's sort of amazing, actually, to boggle at how much collective time has been spent by some many random devs at random companies and then painstankingly re-discovered by OSS folks, especially for phones/SBCs.

(granted, if you can boot upstream, it's all downhill from there these days)

Given the same diagonal size, a more-square display has a greater total area. So a 16:10 13" display has more area than a 16:9.

No up to date number ( Because I no longer care as much ). Before pandemic and chip shortage the trajectory was OLED will be cheaper than LCD by 2022/ 2023. That is excluding other benefits like thinner display so you could fit larger battery and higher res ( spec ) numbers for better marketing. It is only a matter of time before LCD get completely squeezed out on Smartphone.

Who needs 28 hours of battery? I mean the big step is that you can run a an extended working day, lets say 12hours, but at least after 16 hours you should be able to plug it in, shouldnt you; best next to the bed you are resting then.

I'd encourage you to do your own research on this. The kind of research where you assume you're getting a soon-to-be-abanonded piece of techno-capital-consumerist ewaste, and critically evaluate anecdata against a rubrik composed from spending time researching the hairy corners of the space. This comes from a bleeding heart optimistic burned almost too many times.

Here are some items to look for: - a device tree for the chipset for your device - a u-boot fork or patches for the chipset/device/both - a Chromebook built with that chipset, due to how ChromeOS development is done - any sign of commitment from the chipset manufacturer

This topic is a lot like early Android bootloaders before... one of the early Motorola devices. Before there was a set of expectations/framework-support/etc for unlocking. That first unlockable Motorola device, there was 9 months of every wise-guy on the Internet swearing it was just a matter of time. And often it is, but only due to what amounts to luck.

Hint: there's a reason that every single Linux enthusiast isn't running a ARM laptop. There's a reason that Linux folks are excited about the Linux on M1 project even though it means jumping through hoops and reverse engineering and playing ball with Apple.