802 points | 40h ago | Discuss on Hacker News | Back to Radar
Repairability is fine, but when working at the scale that you even have a handful or employees and no dedicated IT or even slightly larger than that the hardware shouldn't be a work stoppage, so having hot spares for folks to be swapped immediately and having higher quality machines pays off very quickly.
Mac laptops are some of the highest quality longest last laptops I've worked with, I ran my 2015 mbp into the ground, it still works and was fine with Linux on it after all these years, but it made it a no brainer for me to get a Neo this year, if I get a decade out of this guy as well I will be happy.
In theory though, this somewhere Framework really shines: there's no hotter spare than a fresh part in a machine that's otherwise the same.
Maybe you work somewhere where your laptop's a thin client for you to access a dev environment remotely, but otherwise if my employer hands me a 'hot spare' I'm going to spend the rest of the day getting set up again.
It takes time and effort to keep Linux running smoothly on my Framework. I don't feel as confident about throwing the Framework in a backpack and traveling with it. I don't expect it to take as much physical abuse over time.
What do you think to the new framework pro models?
On top of that customer support is very good usually. You just call them or go to a store and they will offer a solution, but it could get very expensive if you are out of warranty, that's really the biggest downside. As a work machine for a business its something will just work out of the box and continue to work for years with very little maintenance, makes a lot of sense as a business decision.
Framework in its current shape is for tinkerers and enthusiasts, who are okay with stuff breaking and brainstorming with like-minded people how to deal with the fact.
Meanwhile the MBP is a workhorse which does what it's supposed to and when not there's AppleCare to replace it.
I've preorded a 3rd party dual USB-C expansion card for my Framework, because I love the idea of having even more ports for no reason.
The USB-A dongle card released recently is also on my list:
https://frame.work/pl/en/products/framework-wireless-touchpa...
The main selling point of this platform is that it's flexible, but unfortunately it's something so unheard of, that reliability suffers.
I've always been a big fan of the butterfly keyboards although my external keyboards are usually Topres or the rarer Fujitsu Libertouch variety.
Plus the OS doesn't allow remapping the keyboard to something sane.
Apple meanwhile fixed their keyboard issues last decade.
But Linux sucks on the Mac. It still doesn't support sleep.
Stinks because I need to replace an aging MacBook and was leaning Framework.
Is Omarchy on a MacBook the way to go for mobile Linux these days or?
My work MacBook crushes it in battery. That thing is so efficient. I have seen the new Intel Frameworks are looking good on battery, but I don't have hands on experience there.
If I didn't care for the repairability and modularity, I'd go MacBook for sure, which are generally long lasting machines as well in my experience.
I don't use it on battery much but currently it'll last maybe 4-6 hours? (Assuming typical web browsing / videos / coding.) So definitely worse than macbooks, maybe an hour or so less than my brother's (new) intel ultra laptop.
Build quality has been pretty solid. Only things that have broken have been my fault (keyboard stopped working after the Nth spill, usb connector (for power) is a bit loose after years of sloppy aim) and have been a breeze to replace.
Perf-wise, my only complaint is that I wasn't expecting usb bandwidth to be a bottleneck. Turns out I can't drive 3x 4k screens and fast-charge and have full ethernet bandwidth all at once (each to a different usb port, no dock). But I guess that might've been a unrealistic expectation.
I guess I should note that I've had a minor issue with the amd igpu crashing in a certain game under very specific conditions and the laptop occasionally failing to sleep / wake from sleep. But iirc the former is amd's fault and the latter is unfortunately par for the course on linux ime.
But yeah overall a positive experience. The laptop was definitely pricey for the specs but I knew that I'd be paying for the modularity + small-volume going in. It's also nice for peace of mind, not having to handle it as carefully, knowing its fix-able and trusting FW not to cheap out hinges and the like (previous 4 laptops have all died from hardware after 2-3yrs).
Perhaps OP was unlucky, but outside of this - I don't understand why there are so many companies with good products but terrible customer service. Shouldn't customer service be considered a part of the product?
Never feels good being left helpless due to (lack of) customer support.
I do generally like my laptop, and got it for a great deal, but it's a bit long in the tooth now.
One anecdote: Could be a one off? Several people having the exact same problem. Nah, I don't want to chance it.
Funny enough, too, my current laptop is a replacement. The first one I bought had some issue. I brought it back to Microcenter and they replaced it without any issues. I've had to return a laptop to Dell before, and again, no real problem doing so. OP's story sounds like a nightmare to me.
Its a linux distro. You can use a tool - especially an open source, free one - without supporting the founders.
If you have a problem with free as in speech, Linux and FOSS isn't for you.
Is your objection based on the use of AI at all? or do you have something specific that the maintainers of Omarchy did with AI that you can cite as problematic. Most of Omarchy is just a bunch of preselected defaults on top of Arch, so there’s not really a lot of point to having humans format nix package lists.
You're being disingenuous right now, stop that or go back to Reddit.
> Is your objection based on the use of AI at all?
Personally, it is. Objectively, I'm sure they have more than simple config files to maintain: the glue linking Hyprland and Quickshell, their CLI tool used to interact with plugins, etc... basically everything in there https://github.com/omacom/omarchy
I'll never trust such a distro to be as stable as Gentoo, for example.
But in truth, they were never aiming for the Gentoo or Alpine crowd, so my opinion really doesn't matter. The real competition is probably PopOS.
------
First look at the first script I could find (https://github.com/omacom/omarchy/blob/quattro/bin/omarchy) and I don't see a `set -eu` and some generally bad shell scripting that doesn't even now about case or parameter expansion.
...Wait, they use bash/shell extensively and don't even have a ShellCheck CI? What is this clown distro? Use a real programming language if you don't want to bother.
I was truly just trying to have a conversation and understand why a distro might be called "problematic" with no one willing to actually tell me what the problem was. I'm not an OS programmer so I genuinely don't know why AI use on the kernel is fine, but AI use in a distro is to be shunned. Most of the hate I see about Omarchy is based on who is involved rather than a real criticism of underlying technical issues. You are the first to highlight any actual specific problems, thank you
I didn't mean to touch a subject that is so personal and emotional that you feel the need to attack. I really am just trying to learn.
It's also worth saying this, but anytime someone posts a review, or in this case a whole AI written blog, about something, there's a good chance that person is an outlier unless there is significantly more examples. Folks are a lot more prone to complain online than they are to compliment. That this user was so lazy they AI-wrote this blog post also doesn't help their credibility.
That said, I have been using it as my daily on my desktop for about a year and threw it on an old 2016 MBP to see what the experience was like, and I will definitely be putting it on my M5 MBP when it becomes stable.
Fine on a desktop that's always plugged in, tho.
2. Install https://cua.ai/docs/lume
3. Create MacOS and Linux VMs ad libitum.
4. Profit!
Have run old thinkpads for ~20 years but anyone telling you they run Ubuntu on Thinkpad and have never had to mess about with firmware issues, had battery/standby problems, or had to open it up for repairs is talking shit
Making entire computers is hard, and making then upgradeable is even harder. Getting warranty work and customer support right is table stakes for selling a computer, though.
Too bad being wasteful and short-tempered usually works better.
Spending hours of OP's time seems more wasteful than shipping two small items to me.
They're often "not worth it" for things like laptops (where in a pinch you can grab one at Walmart) but for servers or other one-offs even small businesses can get value from it.
Have you had the same experience?
Turning off smt (and nohz_full; it’s not a network server) lets the cores clock down cleanly. Got that trick from the intel manual and learned about clock domains from a Verilog programmer. Has worked reliably on many Linux systems.
Even found that one of my i5 servers never had smt to begin with, which explained its more consistent performance.
Had been poking at this for at least 5 years prior with powertop(8) to no avail.
EDIT: nosmt also effectivle doubles ram cache size. For my work the extra hyperthrrad is useless, because there are rarely mixed processes where some to integers and the others do floats. Bottlenecked on ALU and cache, mostly matrix stuff.
I think this is the part I don't get. The support team isn't what created the cost, the team that created the problem is. If you want to reduce support cost, you fix the problems that make people contact support, so people don't need to contact support. How big does X need to be for a CEO to approve the statement "You can save $X if you decide to make everyone who has already decided to give you money and has a bad experience absolutely hate your company"?
Consequently developers really like to hole-themselves in, as it's comfortable to spend all day, every day just solving those problems that you imagine in your own mind, instead of actually facing any real problems coming from actual user input....
Thank you for your reasoning.
Aren't many laptops only profitable because they take money from pre-installed antivirus, VPN, and other junk software?
However, Framework should be an exception as they are in their own niche.
I get that Apple's stuff is soldered on or cannot be modified. But honestly, is that really a deal breaker? This stuff has gotten so good that I can't remember the last time anyone opened their computer up to fix or upgrade things. These things have a 8+ year life span and get OS updates for nearly that long too.
I don't know, I guess I just want to get a computer that just works, have it be automatically added to my Apple Care family plan for any damage, and then just get to doing what I need this tool for.
Yes, to me it is.
> These things have a 8+ year life span and get OS updates for nearly that long too.
And I have desktops with components from 15+ years ago that I could upgrade throughout the years, not at the mercy of a single vendor, without creating a ton of e-waste...
> I want a computer that just works
This is a false dichotomy. We absolutely can have modular and repairable computers that "just works", and we absolutely can have a company that builds them and is better equipped to handle exception customer support.
Google famously did the math and found that providing human customer support for their product would cost billions and chose instead to fully automate support.
Apple did the same math, and hired tens of thousands of Apple Store employees worldwide, almost doubling the size of the company. Of course, in the end this is a margin/profit trade-off, but be aware that different companies make different choices.
Apple require sending the laptop away somewhere, and waiting days for it to come back.
Looking at this I'm kind of glad that that's the direction I went.
Consumer protection laws exist for a reason. Collect all the documentation and file a chargeback. This is the only way the problem will actually get escalated.
It is somewhat unfortunate that "chargebacks", like "talk to the manager", have become cheatcodes because their genuine utility has gotten drowned out by a flood of mis/ab-use.
Sure, chargebacks can be abused but what about OP suggests that’s happening here? They spent over three months troubleshooting, exchanged thirty support emails, supplied photos, videos and reproducible diagnostics, tried replacement parts, and sent the laptop to Framework's repair center. They also explicitly asked for replacement parts or a refund back months ago.
chargebacks can be abused but what about OP suggests that’s happening here?
The fact that none of the facts you listed are valid reasons for a chargeback.https://errorempire.com/us/guides/us-chargeback-process-cred...
https://fedlaws.org/credit-card-disputes-and-chargebacks-dea...
https://fedlaws.org/what-is-a-credit-card-chargeback-rules-d...
https://www.cnbc.com/select/what-is-a-chargeback/#how-to-req...
https://commoner-law.com/rights/consumer-rights/chargeback-r...
https://www.moneycrashers.com/credit-card-chargebacks/
https://legalknowledgebase.com/can-i-dispute-a-credit-card-c...
I'm sure there is misuse but if the good you receive in return for the money is non-functional, I think a chargeback is the appropriate step if support decides they aren't interested in fixing the problem themselves.
See https://www.americanexpress.com/en-us/credit-cards/credit-in...
I bought the Framework 13 before launch, and received a machine from the first batch. I later bought their main board upgrade kit and their screen upgrade kit and I did a full upgrade on the machine and rebuilt it. The reason I could justify that was that I would take the old main board and slip it into their Cooler Master case and use it as a spare machine.
But there was a bug in the Intel chip they used in that main board that prevented it from booting properly inside of the Cooler Master case, and going back and forth with support, what they wanted me to do was disassemble my other computers to troubleshoot the one that should have just worked. They didn't offer a replacement. They didn't allow me to send it in to have them fix it. When I explained that I didn't want to disassemble my working machines to fix my broken machine, they stopped replying to me.
This, coupled with the horrendous battery issues in the first version of the Framework 13, led me to conclude another purchase from them would be a big mistake.
Still happy with all six of my System76 purchases.
It sounds like the problem was Intel's and not theirs, yrt they still went out of their way to help you.
But, during this period I've been buying computers steadily from System76, and they have been incredibly supportive when I came to them with an issue (to be fair, I've only ever had to work with System76 support once, but it was a very positive experience).
So no, I don't think it's fair to assume that I would have had the same experience with any OEM. Different OEMs could choose different chipsets, and they could choose to be more supportive.
Why would they take responsibilty for thirdparty hardware.
Edit: TIL, thank you to the repliers.
The Coolermaster case is sold on the Framework website: https://frame.work/products/cooler-master-mainboard-case?v=F...
The key value proposition of the Framework laptop was that it was modular and could be rebuilt as needed with different components so we could maximize reuse. All I'm saying is that when I tried to actually fulfill that promise, I came up empty.
imagine you buy a car and the electronics stop working and the manufacturer says "hey your problem is with bosch, go bug them" - you didn't buy anything from bosch, you bought a car and dealing with defective bosch parts is the manufacturer/dealer's problem, not yours.
So your analogy would be: I took the engine out of the car and put it in my bosch, and now it won't work.
Taking the engine out of the car and putting it in a truck and complaining to the car manufacturer that the engine is not compatible with the truck.
I linked it in my other reply, but you can still buy the case from Framework, right now: https://frame.work/products/cooler-master-mainboard-case?v=F...
It still seems odd to me that if this is a common problem and not a random defect, that everyone who bought it should have the same problem and they would get enough feedback to change their compatibility list.
A thought just occured to me: how do you know it's a bug if you didn't bother troubleshooting it with the help from the company?
Original comment you replied to:
> The reason I could justify that was that I would take the old main board and slip it into their Cooler Master case and use it as a spare machine.
It says "their Cooler Master case".
Did you... read the rest of the post after "bug in the Intel chip?" It sounds like they did not, in any way, help GP.
Microsoft, to their credit here, really tried their best to patch around Intel's fundamental brokenness, but it literally did take them years to bodge up a solution to make it sort of work like it was supposed to. I only stuck it out becasue I really needed pen and touch capability.
Intel is dead to me now. And in today's AI world, Intel is irrelevant, anyway.
Also I realize how cliche it is to show up on the internet in a linux discussion to you you are holding it wrong aha.
I myself prefer the track point so thinkpads are basically all I have left for that and I know loads and loads of people don't use it so it is basically just branding at this point.
There's your problem
Ubuntu has their certified hardware list: https://ubuntu.com/certified/search?category=Laptop
The Arch wiki also maintains a list: https://wiki.archlinux.org/title/Category:Laptops
So many things that didn't work under Ubuntu worked perfectly under Fedora. Lid suspend to ram. Webcam. Microphone. WiFi.
TLDR: I'd try booting a live CD with some other distributions before deciding to make do with Ubuntu.
Note: I'm on my second XPS 14 because the first one had a BIOS error within the return period, so I returned it rather than gambling, and bought a second one which has been fine.
Is there a computer that's not overpriced nowadays? With the global chips crisis I think nobody knows how much a computer should cost anymore. The manufacturers are totally taking advantage of it and slapping any price they want, and will continue to do so for as long as they are able to sell.
My XPS 15 had 3 battery failures. 2 Under warranty.
After the 3rd failure I tried to find a third party replacement (because of the Dell track record and the fact that Dell was sold out of the battery at that time...) only to find out Dell has battery DRM and won't charge non-OEM batteries. Basically the machine would boot and stay on until the initial charge died- super cool.
My MacBooks and ThinkPads are workhorses... If given a Dell I would sell it to fund a used ThinkPad.
You also have less intentional issues. A lot of their X1 line generations were terrible, problematic screens, poor cooling, battery issues, BIOS issues, etc. Not just on 1 or 2 devices, but problems that I could see on batches of thousands or more. Apple devices were for years infamous for screen, GPU, keyboard issues, cooling issues (the last Intel models were something special, to put the last IBM models to shame) and so on.
Nobody collects full reliability statistics on the big manufacturers because the data isn’t available so you have to hope that when you buy from a line of laptops you didn’t land on the problematic one.
In the past few years I had better luck with Dell than Lenovo (again, talking large scale, for my use I stuck with some older Lenovo models).
I’m a bit soured with Lenovo ATM after buying a desktop to scavenge the PRO line APU (for the ECC support), wondering for a hot second why it’s so much cheaper than an identical HP, only to find out the CPU can’t be used on any non Lenovo system. Bought another equivalent HP which runs cooler and consistently moderately faster.
I had a MBP with the screen delamination issue - Apple didn't care, called it cosmetic, until after I'd got rid of it and decided it was an issue.
I had a MBP that had the mainboard issue - I could reliably and repeatedly make a fresh OS install kernel crash on apple.com in Safari, in front of the Genius, but because it passed their diagnostic tool, sucks to be me.
Butterfly keyboard issues.
An MBA that had a charging circuit issue with small water ingress on the magsafe port? Laptop works fine, Apple and third party battery diagnostics report battery healthy, just can't be charged. Go to Apple, expecting something reasonable? $300, maybe, after time and materials?
"We have a quote for you, it will be $950..." (to repair a $999 laptop!) "Perhaps we should get you looking at a new Mac instead..."
I think there's always extremes to stories like these and I've definitely had my share with thinkpad from dead pixels to month long support correspondences.
author's frustrations are completely valid and i do hope framework improves
Still have my “bento box” and fire it occasionally if I need legacy software that neees to run on a malware-eque OS (read: Windows 10-ish and later)
Then I tried to close the laptop, and my thumb touched the screen. NOT hard, very gently, but somehow it was enough to puncture the screen, and it stopped working shortly thereafter.
This seemed like an obvious defect: I have used laptops for decades, closed them literally thousands of times, and never punctured the screen in the process. Lenovo refused to fix it.
I went to a 3rd party (U Break It We Fix It or something like that), which was a separate nightmare, but after a month they gave up.
So I paid for a Lenovo warranty, even though I'd have to wait like two months before I could send the laptop in. After two months I finally did and EVEN WITH A WARRANTY LENOVO REFUSED TO FIX IT. They literally wanted to charge me about 90% of the original purchase price, with the warranty.
So, I guess they have multiple warranty levels, and I picked the wrong one but FUCK LENOVO for selling me a defective screen that broke the moment the lightest pressure was appleid and then refusing to fix it.
The 13 pro has been a very good machine for me. Excellent battery life, good performance, just smooth sailing. My one criticism is the speakers are crap. I know they improved them, so I have to imagine the original 13 speakers were even worse.
The reason I grabbed the 13 pro was because framework featured an upgrade path from the original 13 to a 13 pro by swapping out relevant parts. That's what sold me.
Note that the advertised upgrade path is not available yet, and won't be available any time soon: there's a reasonable guarantee that no upgrade parts will be available for purchase until at least February 2027, and quite possibly long after that.
Hardly their fault
The mainboard/ram/storage that would be most impacted by AI companies isn’t the problem here: in fact, Framework does let you order those now through the same batching process as the full laptops. What you can’t do is upgrade your current mainboard to the pro chassis, even if your current mainboard is their latest amd one and the full pro could be purchased with the same mainboard.
Other components cam simply be out of stock because manufacturers shift their production to components in demand for AI.
Why building PC chassis if there is a high demand for server chassis for datacenters
Given all the bring-your-own options they currently have, they could have even just added a bring-your-own option for the mainboard.
Ive read you can tune something around DSP with software. Here is a random reddit thread about it: https://old.reddit.com/r/framework/comments/18cngrn/improvin...
I have a PipeWire/WirePlumber DSP I'm thinking of publishing. Others have made EasyEffects profiles.
Is a PipeWire DSP lighter than EasyEffects? I’d be definitely interested in that, EE sounds great but it feels like it’s not as optimized as possible.
How do you know that? Is this a known issue you ran in to? Or did it stop working after you swapped it out and then you refused to troubleshoot?
The bug is in the handling of power cycling RTC battery. Basically, if you leave the main board unplugged for weeks and then try to power it up, it'll refuse to boot, and there is a complex set of LED diagnostic codes that they had asked me to take a video of and send to them, which I did. They had asked me to pull the real-time clock batteries out of other machines and insert them into the main board as part of the troubleshooting and I said I didn't want to do that.
You can read more about the issue here: https://www.reddit.com/r/framework/comments/vdo3i6/buyer_bew...
I, on the other hand, wish I'd gone with a Framework instead of System76.
My System76 devices keep breaking and because they're a few years old already, obtaining replacement parts is a challenge. And forget about upgrading them or giving a laptop a second life as a desktop.
Their old machines can be picked up from the referb shops for from as little as 10% to 20% off their original retail price.
Over the years I’ve had multiple Dell and HP laptops and mini-desktop machines that have been in excellent condition when I got them, and each lasted me years.
That said, this was more than 15 years ago, I have no idea if they still make them similarly.
The PC I took to college before that was a Dell, too. I had issues with my monitor...repeatedly. Each time it went, they overnighted a replacement to me under warranty, no charge to me at all.
It's been a while; I hope for their sake their support has stayed at that level...
Framework (i personally love mine, but I haven't had to deal with support yet) Lenovo (I have an X1C for work; it's a great machine, but very expensive, not repairable, and I had significant issues up to 6 months after the model I had was released with the wireless drivers on LTS) System76 (expensive, feels subpar) Dell (lolno never again)
I wish apple provided official support for asahi, but I don't see that happening anytime soon.
Even some level of unofficial support might be a game changer. It doesn't seem crazy, except in the cultural sense: modern Apple views their stuff as the supreme ultimate and for them, interoperating with inferior technologies is kept to a minimum. They don't even understand the concept.
Financially, it could be a win for them in a way that the support for running MacOS on clone hardware never was back in the day.
https://asahilinux.org/docs/platform/security/#apples-unspok...
Not the best built machines but certainly good enough (my 2015 Mac book being my gold standard)
Thus, it’s really hard to tell how big of a quality problem a product has; versus an acceptable low level of bad luck with specific product/service/staff.
In isolation, these sorts of reports are useless. Every product has problems, no product is perfect, no QA process weeds out every single defective unit before it goes out to a customer, and no company has perfect customer support reps who will always do the perfect thing, every time.
Sure, aggregate statistics about support issue count, severity, and how the company deals with those reports are useful and important, but one-off comments in a place like this just don't tell us much.
For example, I bought the second and fourth(?) laptop they put out and am very happy with them. One issue was there was a problem with the power cable jacket opening up. Suppose support could be a bit faster but they sent a new one after I mailed a photo in.
Let it be a warning to everyone else, early product/early company, expect adventures. You're going to have to help them out, even to make them do the right thing. Believe they're capable of learning however, and don't think this "never again" rhetoric is helpful in that case.
(And if they ghosted OP for a good reason, then they've only lost one customer, and it was intentional.)
But the data points for ongoing shitty support make future purchases a real gamble. Based on the article, it sounds like they haven't learned at all.
The only place I’ve ever had real consistent support has been apple. Unfortunately I don’t love their products, so it’s kinda a rock and a hard place.
My framework has been great, and I’ve gotten a couple for my kids, but this story is a real bummer to hear.
If you’re small and trying to compete against a behemoth, decent support is one of your best options. Because hardware is pretty much a commodity.
I really agree with that. Support is one of the key places where you have an opportunity to turn unhappy customers into lifelong customers.
And then I just yesterday did the Cooler Master swap, new mainboard into the laptop chassis, old mainboard as a server, and it went without a hitch, both machines running just fine.
I also don't know the battery issues you're referring to, I don't remember dealing with anything super horrendous in the 5 years I've been using this laptop, but my battery is currently in good shape, probably 6-8 hours on a full charge, which is impressive for a 5yo battery.
The battery issues I'm referring to are that when I put the laptop into standby, it'll go from 100 to 0 in about 15 hours. I don't think it's that interesting of a bug since so many people have been discussing this for so long, but I did note that the Framework 13 suffered from that as well.
Modern Intel hardware has an active standby on windows that it goes into when you close the lid with the charger connected. If you unplug the charger first, and then put it to sleep then it lasts way longer.
This is not a Framework specific issue though, at some point dell had a service advisory out for some of their machines, to not let it suspend with the lid closed, as it will cook the screen! My 10th/11th gen Intel HP would be warm to the touch while it's on standby.
I've given up on proper sleep unless it's a mac. These days I just save and close everything, and shut the machine down.
I also went through 3 hinges on my 1st gen Framework 13 laptop, because the hinges were so weak they couldn't hold up the screen under its own weight.
My thread cataloguing my issues with the Framework 13 got so long, the moderators closed it.
My trackpad stopped detecting clicks. So did the replacement that I bought because it was out of warranty.
One of the buttons for the expansion card removal fell off. Framework replaced that under warranty.
The speakers would cause the keyboard to rattle until I took off the shift keys and adjusted the stabilizers.
I really wanted to believe in and support Framework. I support their mission. But man, everything I've gotten from them has been junk.
That completely tracks. I've found their support to be extremely lame at best.
You can literally see exactly what I bought and when I bought it but you still need me to crack open the case to get the serial number on the mainboard whose widespread, notorious defect you aren't going to repair, but instead offer a lame workaround part for me to install myself instead?
You need a recorded video of the lid of my laptop gradually sagging downward while I type before you can send replacement hinges under warranty, even though the defect is common and why the fuck would I want to scam you out of little fucking hinges that I need to install myself anyway ytvutyf023f498020923r8
Yeah.
Conversely, I'm a bit iffy on System 76. The main reason being, the build quality of the physical device. From a pure computing viewpoint it's fine. Maybe better than fine. But the case is really falling apart. Lots of cracks, and broken fan slats, and such-like. I mean, it still works and is usable, but it just doesn't feel like a high-quality build, so I'm not sure I'd buy from them again.
Fully agree with you about the awfulness of the support, but I think the picture you paint of their hardware is too negative based on you having gotten the bad one.
On a 16 I thought for an employee, he had two full ssd corruptions. FW sent new SSDs, but they didn’t really care to diagnose the issue. Turned out to be a bad motherboard only after I refused to accept a third ssd.
On my 13, the battery dies in shutdown, constantly. Linux OS, if I don’t shutdown completely it’s dead in a day. If I shutdown completely it’s dead in three days. I have a surface pro 3 and 5 with OLD batteries that last months in shutdown.
Other units have had bad trackpads, keyboards, webcam, randomness like the keyboard light going in and out, and I had a screen die just outside of warranty.
YES, all these issues would be fixable with just one tool. The economics of replacement parts is wildly different when I look back to how much I’ve had to spend on the four frameworks we have vs the thousand non-frameworks we’ve gone through.
I want to like them.
Battery life is abysmal. That is even after the battery upgrade kit was installed.
Recently I swapped the bezel, which was easy, and hey, you can do it. But I never had the wish to replace it with literally any other laptop I ever owned. But on the framework, the plastic bezels somehow disintegrated, and I basically had loose strings of it hanging around.
This results in Framework and companies like that, being more bespoke. So they do not have the volume of scale. When its a one man or small team, your support tends to be great because your talking directly to the core.
When a company like Framework grows a bit, the amount of issue tend to grow also. So they are required to get a lot of staff and the core (hardware and support) itself gets water down somewhere (often support). Aka cutting costs on those expensive humans...
Its actually hard for companies to jump past that, where they get the production volume to force cheaper prices from supplies (on the hardware side), to compensate for the increase human factor.
You notice over the years, with a lot of companies this trend. Where if they are small, great. You brag about them, their customer base grows thanks to the good word to mouth, and after a while you start to notice new names, less well informed, more bugs and issues. What used to be a great personal experience is now replaced with the venire of a large corporate structure, but not the same level of flexibility to get personal accountant managers, etc.
There is this gap that Framework falls under. And they are having a hard time passing this, with the known results. Also the entire hardware market going crazy really does not help given that they are already producing bespoke / more expensive items. They have the drag of a large company but not the advantages of a large company. And getting past this hurdle is often the difference between a Steve Jobs and ... some name you never heard from. Yea, not the best examples but that is the first name that comes to mind lol
I really love the module system, the screen ratio, the linux support, the 180° hinge. But I think it is fair that the frequent QA problem is a dealbreaker for a lot of people (especially at the price point that they ask). For me, as long as they don't fix this, it will mean that Framework stays a niche manufacturer for enthusiast.
If that were the case, we either wouldn't be talking about it here (we're talking here only because framework _is_ widely popular), or he would have already done it (if "opening any ticket" would help).
All 3 issues were easily fixed with replacement parts that other laptops couldn't get.
However. My old laptop was 5 years old and never had a single issue that needed any fixing...
It has been years and I'm hopeful that it has changed, but I had an extended back-and-forth on a fan that was whining. It was taking forever, involving photos(!?). In the end, I just ordered another fan as I got sick of dealing with their support.
I first had to use it as a professional dev device in late 2025, before that it was just a light personal laptop for me. It suuuuucked as a dev device for me. I got a Macbook Pro again.
Their customer support experience is slow and really infuriating, even for design faults they admitted and for things they offer free replacements.
If they have 10 different "people" to handle a single ticket and act like it's new every time, they have the staffing to handle a ticket like this. Anyone justifying a support person's refusal to read ticket history is part of the problem.
All these guys had to do was order a new keyboard. If they demanded a refund for the not-working keyboard they'd get one. I know, from experience having handled dozens of Framework laptops, Framework absolutely will do this.
You'd think someone offering consulting services would be a bit sharper..
The criticisms of the ticket ownership posture are helpful (depending on how accurate they actually are), I have forwarded this along to someone high up in Framework's support branch of its org chart I have a good connection with.
The other keyboard, the one the customer already had, was the one that was obviously not working perfectly.
_
> if a customer complains about a keyboard issue that we can't reproduce, we replace the keyboard anyway.
The obvious thing to do. Not doing this is the mistake Framework made.
_
> shouldn't have to pay for the replacement part out of pocket, that's literally the entire point of a warranty.
An in ideal world, no one should have to do anything.
From a logistical standpoint, competent people know how to make results happen. As someone operating in a business I would order a new keyboard.
Could just send the entire laptop back.
_
What I can say for sure, when I have had to make sure that developers and other users are operational, not a single person went with more than a day of downtime just because one (or even two or three) laptops had issues.
Framework is awesome. I am personally responsible for more than one dozen of Frameworks being deployed and will probably be responsible for many more.
Ah no, that is not "obvious". It's entirely possible that they put the keyboards into a test harness that didn't actually test the things that were reported broken (module appearing as a numpad, c key inserting a backspace), and the technicians were not trained or allowed to go outside the testing parameters.
They did offer replacement after about 4 emails.
I am a bit surprised a fault this bad couldn’t be caught during QA. But they’re also a small company and I’m just waiting now for my replacement to come. May be more on intel’s side too than them.
More details on my issue here https://community.frame.work/t/laptop-13-pro-core-ultra-x7-3...
There are several changes we made earlier this year to drastically shorten the number of back-and-forths to issuing replacement parts when submitting a support request, and we’re working to streamline that further. We’re also improving the RMA->quality->engineering pipeline to make sure we capture learnings and make fixes from field failures.
As I have experience working customer support in IT for a few years, I know good support is both hard and time-consuming. Systemic change is hard too. And to add to the list of difficult to impossible tasks: Staying always truthfull, while providing helpfull support-replies is like near-impossible for most organisations.
Best of success for your endeavours!
Your customer base are above average technical people, yet you insist on treating them like clueless noobs.
Thankfully, your products in general are great when they work, but so is every other brand.
If you need to have strong technical people in support, you’ll be overspending in salaries for people that will likely move fairly soon to better positions (a lot of tech people started in support, i did myself).
If otherwise you don’t spend enough you get to keep the books in check but then you have support people that are not very technical and mostly read from a script.
And there are a ton of other things that happen behind the curtains as well.
Support seem easy but trust me, it isn’t.
This is true of most jobs. That doesn't mean I expect companies where the job is required to routinely fail at them, mostly because they are unwilling to invest proper resources.
Framework is not unique in having shitty support. It is an absolute epidemic, which is why companies are able to get away with it. But the fact that almost everyone sucks at it doesn't mean we shouldn't call the problem out loudly when we see it.
Completely useless comment.
At no point did I suggest not to do support, and Framework is indeed supporting its customers.
This is unfortunate because, especially for technical folk, support interaction is the backbone of user experience.
If they could innovate here a lot of things could be overlooked. Costco + early Amazon often did this pretty well tho.
This is the primary reason i buy used iphones - someone else pays the apple tax, i take the phone to apple and for a reasonable price, i get a new battery and i keep the value of the phone and battery for around six years. No other phone manufacturer offers that proposition.
I also chat with the apple staff while i wait and they are paid decent wages. I certainly think they deserve higher wages, but their wages are not bottom of the barrel. The strongest evidence is that staff turnover is relatively low.
One of my early jobs was working in support for a web-hosting company just after the dot-com boom. They did a lot of things wrong (or at least cheap), but they also got a lot right, especially their support teams. They understood that customer service is the face and reputation of any business, not just a cost center.
They provided good training, fostered a positive atmosphere in a variety of ways (important when your job is a constant stream of unhappy customers), and supplied a lot of free food and company outings. I wouldn't say it was an _awesome_ job, but it was a good one, especially for where I was at the time. There certainly are parts of it I miss. (Mainly some of the unique characters I got to work with. It feels like everyone in modern tech companies all have the same personality.)
The quick fix for any company in this situation is to require that technical people across the company take responsibility for customer support. Of course, they don't want to, hardware designers and software engineers can't imagine anything worse, but they've got to be exposed to how real customers are experiencing their work to have any hope of doing a good job. The exposure can be direct (in a crisis) or indirect (through technical support staff relaying).
If I were the Framework CEO, I'd be taking over customer support myself. A nightmare, but necessary to understand why their support is so bad.
And this is how it should be: an enthusiastic developer can churn support tickets in their free time much much faster than dedicated support staff does full time.
Louder for the people on the back
In the same way a bad medical diagnosis makes things harder later on, or bad legal advice, etc
But especially in the "silly" cases, this is extra disappointing. The case in TFA is not "you're holding it wrong" or "weird technical bug that happens once in a very while", it's a very clear issue of "should do A and it doesn't"
I like your idea but I can also imagine that quite a few technical people will not have the necessary communication skills for being in customer support. They will need additional training if you want to unleash them onto your paying customers.
‘Oh, yeah we have been seeing this bug, tell the customer to flash this version.’
That’s a known issue and the fix is going through Qa
Sounds like there was an issue with that part, rma.
The amount of tickets your pros can clear while skipping the script is insane.
Additionally, it can turn up or handle bugs that aren’t handled by the script.
We all read the diagnosis on this post and knew the part was bad about 3 minutes in and it’s not even our project.
Products are priced and launched with an initial BOM cost and anticipated labor cost for repairs. Prior to the AI buyout, service and support was already running into real issues with the costs of labor increasing very quickly. Now, the cost of service parts has also skyrocketed. This means that the initial overhead in the cost of the machine is no longer able to cover the intended dollars put aside for repair.
This is not just happening in computers. This is everywhere. Support and service were struggling everywhere coming out of COVID, prior to the jump in component costs due to labor. Now it is a bloodbath as logistics costs have also jumped due to fuel costs. Add into this that the vast majority of manufacturers build in lower-cost labor environments, but repair generally happens locally near customers. In these situations they are facing repairs that can cost more than building a new machine.
The future of support is going to be grim for the coming years.
I had a similar issue with Apple once and that was their recommendation (as it was within their return window).
Perhaps that approach isn't practical today, but maybe there are some useful threads in there to pull on.
I wonder if it's because it is a small enough team that they have the correct person respond to support calls each time, but it was the best experience I ever had.
Also I had to make videos and photos and then email them which couldn't handle large files so I had to organise my own hosting and share links.
Basically they don't seem to have thought it through yet
Since you seem to have experience with this, the principle that I've seen work "best" in my own limited experience (and I wonder how it matches with your experience) is to keep the barriers between support and product development as low as possible:
1. keep the company as small as possible in general (which lowers all communication barriers everywhere, and helps with cash flow—fewer salaries, smaller office, low overhead)
2. Early on, have the same engineers doing product development and support. Later, have heavy, regular communication between the teams (including managers and senior ICs on both sides. Maybe rotating the managers would work? I don't know. Once you have more than one level, I don't know anymore, but maybe do the same thing with directors and senior managers?). This hurts growth, because you're understaffed to begin with, and you're impeding the staff you have by giving them tons of unplanned support work. But IME it means that product development is happening at the right level of abstraction.
If the product you're building requires big company support (or training or product development), and the revenue it brings in can only support a small company, then you should change what you're building. It's very hard to change what you're building if the company is very big.
So if, for example, support is boiling because your product is flaky, and engineering is too small and too busy to fix all the problems at a reasonable pace, you probably have a design problem(s) and expanding will make it more entrenched. Instead, you should simplify the product. Then expand (with an understanding of the real costs of different parts of your vision), and repeat.
The state of hardware is about as bad as the state of software lately.
I do have a T470S which works perfectly well, a Macbook Pro M1 16GB and hopefully soon a Mcbook Pro 2019 i7 64GB, so I'll do fine.
I have interacted with support before when a usbc thing I got was bunk. Two emails, and then they sent a replacement. Support might be better in Taiwan though, for all I know. Certainly shipping is fast here...
I think this feels like it must be true, but is it actually, in practice? Plenty of SW people don't know a ton about HW.
I recognize that maybe all those people are on Macs :)
I have no experiences or relations with Framework whatsoever nor I intend to have, but having seen some support exchanges about products with supposedly above average technical customer base in the past I'd be willing to side with them on this particular point.
I am not disagreeing on support quality, but the price is very steep and ultimately paid by the customers.
To my surprise, ChatGPT replied immediately with "When you said 'refund', I assume you meant 'discount', so I've taken the liberty of issuing you a new coupon, please use it for your next order and I'm sorry for the problem".
I was blown away, I fully expected four days of back-and-forth while I explain my issue with my discount code that wasn't working.
Often enough customers are wrong about the root cause and their insight into fixing the problem is fairly shallow.
But knowing how you’ve treated them will make everything easier regardless. And your coworkers in any kind of service role are almost adversarial. If they weren’t incompetent you wouldn’t be dealing with a repeat customer.
When the customer is correct all along and you’ve exponentially increased how badly you’ve treated them.
So far, I'm happy with my Framework purchase... but haven't needed any support yet.
I can't imagine how frustrating the experience would've been had I not had another machine to use for work.
Also their business practices seem extremely sketchy to me, one of the first things I asked when it arrived broken was if I could return it for a refund. They refused claiming that the return window had expired, and the window does not start when you receive the item, but instead when you order it (it took ~4 months after order to ship to me).
It was a real learning experience. Now I record every support conversation I have.
You know your customer service is bad when you are unable/unwilling to accept a sale for several thousand dollars.
If you want actual support for your thinkpad, you need to pay the premium for on-site support. The pricing for 1-2 years is usually not that bad (relative to the price of a moderate thinkpad). The techs are hit or miss, but at least they come to your place with the parts (sometimes requiring 2 visits but it beats sending the laptop away for weeks/months).
So, experience with support was very good. I have no clue what that support option costs. It's either expensive as hell or a bad business for Lenovo if I am not an absolute exception with my failure rate.
Why?: because most of the time (>75%) its a clueless noob issue that is solved quicker by doing that.
That being said, there are ways to do it that doesn't make the person on the other side feel like you are being condescending... And it is important to strike that balance...
This story may not be big, but it's strongly indicative, because the problems reported show systemic issues, not one-off flaws or unlikely coincidences. Hardware has one-off flaws and unlikely coincidences. A process of handling things that revalidates an address for over a week and makes repetitive demands of customers troubleshooting the same issue is a systemic failure that is avoidable if any one of the many agents handling the issue gave a shit. This is relevant to me specifically because this kind of failure is not bad luck, it is about how the support organization is run.
Given that this encounter was super recent, it must have been even worse. Hard to imagine.
I love everything about framework as a company, but the approach to customer support has left a very sour taste.
An amazing product with terrible support is something I would not buy again.
I have companies that are still on my shit list years later because of how badly support dropped the ball (hello HP) such that I don't care how good the next product is they'll not get another order (WinWing most recently earnt their spot on the shit list).
But it sounds like the process is not working here. Support people were not identifying the glaring issues, even with the keyboard at hand
This does not inspire confidence
It's not like selling to a country is just changing the address on the label...
I bought a chasis kit recently and the touchpad is faulty, or acting faulty ( physically getting stuck depressed), and the amount of back and forth for the serial number of part X, then Y, then firmware of Z, etc.. maybe there's a technical reason for that but i just considered myself beat into submission and gave up.
after mainboard upgrades, touchscreen upgrades, and various other upgrades over the years and being excited about framework, it's weird to have all of my enthusiasm get derailed over support for a touchpad.
This should be a case of the engineering team getting the faulty device for debug (and ideally getting all the relevant information so they can do the work with some semblance of parity with the customer's setup) -- and the other half is the customer gets a functional piece of hardware to swap in.
If Framework is worried about sending out hardware before receiving hardware, the policy is a simple one; when we get the hardware, we'll ship your replacement.
---
and the amount of back and forth for the serial number of part X, then Y, then firmware of Z, etc.. maybe there's a technical reason for that but i just considered myself beat into submission and gave up.
This is the standard 'debug over the phone' thing and engineers will do this while collecting information to try and recreate the problem you're having. It may be because the engineers are too close to the process? If you think about it, the RMA process is actually a sales process. You're essentially selling an already sold user on continuing to be a user.Oh no. It should be "we have sent you a replacement - once it's installed and confirmed working, pack up the broken one and send us in the provided box with the provided pre-paid return label".
In reality many people will NOT take the second option, but will be happy it was there, and the company probably never bothers billing for incorrect advance RMAs.
For example Dyson is known to provide exceptional support for their vacuums. They often even replace damage for free that was clearly the user's fault. But their products are really expensive. Probably not much more expensive to manufacture than their competitor's products for half the price. They probably don't even lose money if they have to send a replacement once.
Buuuut, I'll argue against the point that these are faulty units. Everyone gets the same PSU in their Desktop. That thread (and many others like it) are full of people claiming that their _specific_ PSU fan is loud and defective and demanding that Framework should replace it. And then are surprised when the replacement sounds exactly like the old one.
I bought the Framework Desktop anyway after reading these threads, and after owning it for almost a year, I have to say that the fan noise doesn't actually bother me. I have had laptops and desktops with FAR noisier fans that ran either constantly or intermittently so I guess I'm just thankful that modern PCs don't sound like vacuum cleaners anymore.
Then take action internally.
You need to touch some ground, your work doesn't end after the sale is made.
I've been there with Framework. It's incredibly frustrating and I wouldn't even consider buying another one of their products until they've conspicuously turned this around over an exteneded period of time.
Me and my GF filed a report with every proof to mastercard for a chargeback (that framework contested), but after Mastercard investigation, they ruled in our favor.
This is a scam company. Never ever buying again.
Malice / incompetence etc. etc.
And this will go on for many, many steps. And when you finally get to the end of it, they'll say "sorry, you'll need to replace this keyboard, and it's out of warranty, so you'll need to pay for it yourself" and you'll have spent many hours over a period of weeks just to get the answer that you were 95% certain you were going to get in the first place.
It is true that they were out of warranty and couldn't reasonably expect a free keyboard. It is true that your support helped them identify that the keyboard was the issue, so it was a successful diagnostic in some sense. But the experience for the customer is super terrible and infuriating.
What would you want as a customer in that situation? What I'd want is to get an email like "Hey, I'm really sorry you're having that problem. As you probably know, you're out of warranty. There's a pretty good chance that you're going to just have to replace the keyboard, but if you're interested in trying to debug it to make sure the keyboard is the problem, we're happy to work with you on that." And then if I did want the debugging, I'd love to get a single document containing the debug steps that I could work through in one sitting.
That's why I think your insistence on "let me see your case to identify if any steps were done wrong here" is off-point. The problem isn't any particular debugging step or any individual case, it's that your whole process is fucked and customer-hostile in its conception.
Really? This was the drastically improved process? :D
I'm rooting for you guys. Framework is a great concept and I want it to succeed. Good luck.
Just a little background: https://www.youtube.com/watch?v=6UUOyGd5UkU
Editing this to add on: A firmware update bricked the TPM functionality somehow. :D
It's a bit fun the first time to assemble from scratch, but it's annoying the second time, and it would mean you know the laptops actually work when they get sent out! The article's issue for example would've been caught if someone had assembled the laptop and powered it on, and not then disassembled it again for the experience of assembling a DIY laptop kit. My understanding is that this is actually the process Framework uses — that is, assembling and then disassembling — and I can't imagine disassembling has a zero percent fault rate, nor does asking the customer to re-assemble.
Your laptops are really nice and I want you to succeed. There's a reason everyone else ships assembled laptops though, and I think you should do it too. It wouldn't harm repairability, or compromise your principles: I think it would just reduce churn and support tickets from broken parts and laptops, and reduce customer frustration.
You'd think that would make the disassembled version more expensive to produce.
Showing 400 of 607. Read the rest on Hacker News
Comments are loaded live from Hacker News and are not stored by Mid or Real.