At least as of a couple months ago, `ty` was actually being developed in the `ruff` repo (per an pdocast interview the devs did on Talk Python), so that might be why the `ty` repo looks empty (and pulls in ruff as a git submodule).
I've been considering this as my Android exit plan (as part of a slow rolling de-googling effort, even before the recent "sideloading" news). Are you using it as a daily driver? I'm sort of surprised it doesn't get brought up more.
Yes, I used SailfishOS as a daily driver since ~2014 until last year when I moved to the Furi FLX1. The FLX1 has been my daily driver since. SailfishOS is much more polished, but it's not fully FOSS, and it follows upstream much less closely. FLX1 is basically in-sync with Debian testing, with the exception of kernel.
> FuriOS allows for running apps inside a container running Android codenamed Andromeda. This container has complete integration with the host and makes all Android applications work like native applications
Yes, both (official) SailfishOS and FLX1 offer decent/good Android app support. Not every app will work, but when I have needed Android (rarely, for basic stuff), the applications have worked.
Interesting. I had a poke at postmarket, which wasn't ready in comparison with SFOS. Would you say the FLX1 is at better stage in development than postmarket?
You're comparing a Linux OS (postmarketOS) to a device (FLX1). I think you meant to compare postmarketOS to FuriOS : )
FuriOS (and its base Droidian) are at a better stage of development for devices made to run Android using the old Android Linux kernel, whereas postmarketOS is better for devices made specifically for Linux, like the Liberty Phone, Pinephone, etc. Droidian will not even work on them.
I'm not familiar with postmarket, but I imagine it shares a lot of the same phosh+GNOME app ecosystem, in which case, the apps aren't in a better state.
In terms of polish and app/dev ecosystem, I feel SailfishOS still rules, but it's getting harder to justify using/development, with it's increasing divergence from upstream.
The only detractions on the software side that I ever see are about it being a “hack” via Hallium, but to be frank, the device actually ships and is usable today. Linux purists probably need to stop complaining.
It does seem like there’s been a backlog with the latest orders though - maybe due to tariff hell? I keep wanting to order but their forum has a few people being thrown for a loop on the order side, so…
My kid is a bit young, but this is the laptop he'll be getting in a year or so to replace the garbage Chromebook he's currently using (which has steadily gotten flakier since purchase).
First class Linux support is requirement #1; Framework's repairability on top of that means there's not even anything else to consider. It will be the third Framework in our house. My wife is happily using the second, having easily switched to Ubuntu from Windows 10(?) when the video cable connection in her Dell XPS flaked out and made the screen useless.
FWIW, I believe DNF (as of 5?) is now written in C++.
But as a long time Linux user who always has to use a Mac at work I've been consistently floored by how painful Homebrew is to use, to the point that for my latest corp-issued MacBook I switched to home-manager and I'm not looking back.
I've written some fairly complex stuff in Ansible. It is mostly declarative but you should be careful with assumptions about its idempotency, especially if you reach out for community modules.
I don't think this was ever really a concern. Google and device manufacturers already have ways of publishing non-GPL portions of a complete Android distribution.
