| ▲ | ploxiln an hour ago | |
I love the Framework mission and product design, I bought a FW13 AMD about 3 years ago and it's been great. It's been great for me because I never want to talk to "support", I love that there is an official place to buy replacement parts for fair prices, and fix it myself. Some keys on the keyboard failed after 2 years, got replacement keyboard for $40, fixed, nice. Also good troubleshooting help from other technical users in the forums: usb ports died once, reboot didn't fix it, force battery disconnect/reconnect fixed it. But Framework has a problem with support employees, and firmware development/release management. Probably great people who work hard, but just not smart enough. I've seen a number of very believable stories about support asking for a bunch of screenshots and sending replacement part after replacement part, for what is a firmware bug or hardware design flaw that is by that point well known and characterized by expert users on the forums (and with home-grown hacky fixes which demonstrate the precise original flaw). The framework desktop PSU fan, the FW12 chassis cracking, usb-c charger compatibility, original FW16 heatsink with liquid metal ... How about the Intel 12th gen year-of-firmware-struggle where there were silly file mixups - the left vs right retimers in the linux package, the windows beta release needing a "hotfix" for the model detection, but then the final release being the original un-fixed installer, for a few days until the community complaints got through. Sloppy EFI shell update script. Just basic failures of skill and attention, where external expert users are able to diagnose and fix it. FWIW I also isolated a minor bug in the ACPI code to a particular couple bytes: https://github.com/FrameworkComputer/SoftwareFirmwareIssueTr... ... but no movement in a year. Not a big deal in the grand scheme, but you gotta be able to at least fix the easy stuff! | ||