![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
When my pixel 5a decided to stop using the screen, I was able to do a full phone backup using the OTG to plug in a keyboard. Ridiculous but was a fun troubleshooting moment
When my pixel 5a decided to stop using the screen, I was able to do a full phone backup using the OTG to plug in a keyboard. Ridiculous but was a fun troubleshooting moment
I have no complaints with the framework keyboard, is there a particular issue you’re concerned about? The track pad is almost apple quality. Certainly better than most laptops I’ve used.
Love my 11th gen framework, but there is an issue with the 11th gens where the CMOS battery will die rather quickly. If it does die then the laptop needs to be plugged in to turn on, even if it is fully charged. Framework is aware of the issue and will send a free replacement battery or, if you can solder, a mod that will eliminate the issue for good.
Still love framework and would definitely recommend them - but the 11th gen line (their first product) has a few gotchas
Not sure your budget, but you might be interested in one of these https://us.starlabs.systems/pages/starlite
I’ll start this by saying I’m not familiar with either model, but as a general rule, always go x86 when you can. The Intel processor is going to be much better supported. You might get the snapdragon version to run, but it likely isn’t supported by mainline Linux.
That being said, touch screen support on Linux is improving rapidly, but still isn’t quite there. Make sure you’re aware of the user experience before buying so you won’t be disappointed.
Also, my unsolicited 2 cents, I would try to avoid buying lenovo. I’ve had the unfortunate responsibility of fixing a few of their products (an all-in-one and a few laptops, including a new thinkpad) and can confidently say their reliability, and repairability have greatly diminished. They use cheap parts and are in general, poorly designed.
Onshape hands down. Browser based so there’s no compatibility issues. It’s super easy to use and pretty powerful. Its free for hobbiests (the caveat being your models will be publically accessible). We use it exclusively at work and it’s been awesome.
I’d love a good Foss CAD package but there are too many issues with the current ones for me to make the jump.
Kinda has been. I did my iPod like this 2ish years ago
I’ve been using migadu and its been great so far
Downloaded from the KDE store
The command was rm -rf $pathvariable
Bug in the code caused the path to be root. Wasn’t explicitly malicious
Yeah that’s the one I meant. Damn, that’s too bad
Does the “prevent sleeping” toggle in the power icon on the task bar work in this case?
Gotta throw my vote in for tumbleweed. Its IMO the best distro to get the latest packages while still maintaining stability. Their built in roll back feature is great.
Software not being well supported is kinda a sticking point. Though honestly its becoming less and less of an issue each day. Flatpaks are available for almost everything, distrobox covers the rest. I really haven’t run into any situation that prevented me from doing what I wanted. I’ve been using it for a few years now across my desktop, laptop, and my computer at work. Suse is enterprise Linux after all, its still got great support
I meant the host computer, raspberry pi? I was giving my phone opening time as reference, should have made that more clear.
I’m also on a pixel fold. The performance is fine for me, but I’m hosting home assistant on a VM running on a server with Ethernet to my networking switch.
What are you running home assistant on? On my pixel the app only takes ~2 seconds to open and load on 4G
KDE Neon is going to be better supported than installing plasma on Ubuntu. Option 2 will be less of a headache long term I think.
The slightly heavier line weight and slight rounding definitely make a huge difference
Oh cool, that’s great
Ah interesting, thanks for the info!
This isn’t a joke. Often times rewriting features like this will allow the code to be more streamlined and use the latest KDE library features. This is brining new features using modern and more maintable code that solves long standing issues. Fixing the old code sometimes isn’t worth the effort for a variety of reasons (based on unmaintained libraries, the original code might have been written a while ago so it’s had many revisions of fixes that necessarily complicated the code, etc.)