well it's new battery feel so far, just got the machine less than two weeks ago. Haven't done any long battery-related work yet. My previous Dell XPS13 had the battery puff out and it actually wrecked the mainboard in doing so, so I'll be watching out for any negative experiences like that here, that I can open the machine right up in 30 seconds to attend to issues like that should be a plus.

Luckily there are battery stats. On a 7840U with power-profiles-daemon installed and PCI power saving turned on (but not wifi or audio power saving, or VM writebacks, I don't feel those are worth the power savings), it draws 3W if I'm doing absolutely nothing with the screen on its dimmest setting (I mostly use the laptop in bed at night), and 5-11W while web browsing on Firefox.

It goes up to about 13W while watching youtube, even though it claims hardware accelerated video decoding is on.

6-7 hours of browsing in Firefox, 4-5 hours when doing work involving occasional building/compiling, 3-5 hours of 2D native Linux gaming, 2 hours or less of 3D AAA gaming through Steam/Proton.

Yes they work (plasma 5 KDE on arch). On the 55Wh battery with a 7840U, it loses 2-3% per hour when asleep, so I set up suspend-then-hibernate after an hour (though setting that up was a pain in itself).

They work, but on gnome you might have to disable the `hid_sensor_hub` kernel module.

Nope. It's a mechanical trackpad with similar pressure issues (super stiff in the top corners, a little softer in the top center, best in the center and bottom). I switched to tap-to-click.

very similar. One would think they're on a macbook when using this laptop. I have it set to use "area" for left/right click and it works better than my older macbookpro where the trackpad had lost some of its responsiveness at some point.

Besides the actual hardware, I think the biggest problem is the software implementation of trackpads in Linux (at least in libinput/Wayland). Even running Linux on my Macbook, the trackpad experience is vastly inferior to macOS.

I don't care too much about gestures, but mostly about stable palm rejection and proper acceleration curves. The current implementations sadly provide neither.

IMO not close (I spend the majority of the day on my work macbook). It's especially apparent when scrolling or moving the pointer small amounts, and especially near the edges of the trackpad, where you need to make bigger movements for it to work.

Your mileage may vary as people have different sized fingers and such.

It's a far cry even from my old Google Pixelbook, which is a (distant) second best touchpad I've used.

I have a thinkpad also from work and I've never liked thinkpad keyboards, and I especially never liked the trackpad-buttons-on-top thing (it's a key reason I dont use thinkpads normally). I've been through several thinkpads ( as we have to swap out every few years) and while they get nicer each time, they still carry along that old-school "lets have lots and lots of small keys" thing.

Framework's keyboard OTOH is very similar to a macbookpro, keys feel a little higher and more tactile and also the layout is simpler than how my thinkpad has them laid out.

truth be told im mostly using an external keyboard so far, havent really gone anywhere w/ the laptop yet.

I don’t have a Thinkpad, but the plastic surface of the keyboard feels like a slight step down from other keyboards I’ve used (like my Logitech MX Keys). It’s not as smooth — the plastic of the key is rough, almost chalkboard-like. I haven’t used it in-depth enough to determine any pet peeves about the layout. But overall, I like it. If anyone ever offers an upgraded key cap set, I might go for it.

The fingerprint sensor is shared across all framework laptops. It was about as fast and reliable as you can expect a fingerprint reader to be.

Fedora 39 is the "official" way to go on the AMD board due to the newer kernel. Installed without problems and all hardware worked on boot.

The biggest issues are setting up a workaround for staying in sleep/suspend while the lid's closed but plugged in: https://community.frame.work/t/tracking-framework-amd-ryzen-...

And flipping a VRAM flag to avoid GPU memory allocation issues: https://community.frame.work/t/tracking-graphical-corruption...

Neither of which is Fedora specific, and both of which might be resolved via update.

I went straight for fedora 39. The two issues I had were 1. the initial BIOS update hung, and I had to run it again - elsewhere, someone who had this problem had reported that it bricked their machine, however I was able to get through it: https://www.reddit.com/r/framework/comments/17jzj40/bios_upd...

Then for 2., there's a kernel param I had to set to avoid a display issue, that's mentioned here: https://www.phoronix.com/news/AMD-Scatter-Gather-Re-Enabled , I had that exact problem.