In use battery life is largely the same, though Intel has added some additional features with 12th Gen Intel Core that can improve in-use power consumption in some scenarios. The main optimizations we were able to land were in standby power consumption. For Windows users, this means longer Modern Standby before going into Hibernate. For Linux, more importantly since hibernate is atypical, it means being able to leave your laptop unplugged for much longer when not in use.
The standby performance was what kept me from buying a previous gen frame.work despite loving the mission and wanting to support y'all. I was holding my time until either the efficiency cores came along (if that has any improvement in standby? I'm not even sure) or if you ended up making AMD where I believe S3 sleep states still exist.
Very exciting to hear there's an improvement in this generation. Is that improvement due to intel changes, or due to frame.work changes? Can you quantify the standby improvement for linux in watts or battery % / 24h?
Does battery life significantly change between processor models?
This is a combination of hardware and firmware improvements by both Intel on 12th Gen Intel Core generally and us on the Framework Laptop specifically. This is with s0ix standby, and we see ~0.4%/hour typically in Fedora 36 on 5.17.6 with the settings in our setup guide: .https://guides.frame.work/Guide/Fedora+36+Installation+on+th...
> This is a combination of hardware and firmware improvements by both Intel on 12th Gen Intel Core generally and us on the Framework Laptop specifically. This is with s0ix standby, and we see ~0.4%/hour typically in Fedora 36 on 5.17.6 with the settings in our setup guide
For reference, on a Intel 11th Gen Lakefield (Lenovo X1 Fold), using a Vanilla Windows 11 Pro with the non-Lenovo Intel GPU driver downloaded from Intel Driver & Support Assistant, given the results of powercfg /sleepstudy I get a 6% of drain for 9h54 min (so about 10h) therefore 0.6%/hour in "disconnected" (no wifi activity) S0ix standby.
Before, with the official Lenovo driver, it was 0.5%/h (4h: 2% drain). I was hoping to get better results, but this isn't so bad with about 0 optimization!
S0ix has gone a long way, in both Linux and Windows.
Good point. For what it’s worth my last MacBook had a TB3 port physically wear out. Thankfully it was covered by warranty, but the connector saver concept is definitely compelling.
This was something that was more prominent during the Micro-USB era. The little metal "tabs" on the male end of microUSB connectors would start to wear out after a thousand+ plug/unplugs resulting in a loose connection that wasn't reliable.
With USB-C, the connector was designed consideration of a bunch of factors, one of which I would assume is lifespan of the end connectors - USB-c has thicker, more resilient plastic hooks built into the inside of the male plug and stronger mating latches in the female end of the connector.
It when You need to adjust cable multiple times until connection happen, and then work very careful to not move anything.
Ports sometimes are very fragile. My old laptop has only 2 of 4 USB ports working.
Connectors are rated for a given number of connect/disconnect cycles. For USB-A it's a minimum of 1500[1].
If your laptop has a cheap connector which isn't rated for more, and you do two cycles a day (start/end of day, start/end lunch), then you'll go through the rated number of cycles in less than two years.
Doesn't mean the connector will fail right away but it might start to act up. Connectors are not forever.
I just recently flashed a Gotek with this firmware to resurrect an Amiga A500 with a broken floppy drive. It works great with the addition of an OLED screen and a 3D printed bracket to mount it in the Amiga's internal floppy slot.
I'm also eagerly awaiting the support for Heathkit *.H8D format images so that I can more easily use my H89 without needing unobtainable hard-sector floppy disks.
> It will need to support the C interface components like PDO database drivers and the Laravel web framework.
Laravel does not have any C PHP modules in its codebase. While it makes use of drivers provided by them, it does not have any components that are written in C.
I read the original poster's post as Graalphp needs to support both PDO, the C extension, AND Laravel, specifically every language construct that Laravel uses.
Similar to Travis Goodspeed's goodwatch project, which is a replacement board for Casio calculator watches that contains a sub-GHz programmable radio. I've built a few of them and had fun writing software for it.
Another excellent addition to the form factor by Paul!
The first Teensy was my stepping stone off of the Arduino IDE and platform for modern embedded development. Library support and form factor make these excellent devices to integrate into one-off custom electronics projects.
With 4.0 it looks like we have an excess of IO and processing grunt, and I'm curious what the power consumption is like at the slower clock speeds.
