As a trackpoint user, I am glad it's off by default.
Because of scrolling on Thinkpad keyboards (using the middle click), I had to turn that feature of every time, especially while working on longer documents I would otherwise accidentally paste stuff at random places.
+1 - switched to Sway (and thus Wayland) in 2017 and it was okay then to only improve over time. At some point I switched xwayland off, as there were env vars to make everyhing I needed run natively on Wayland.
These days my setup is less radical/minimalistic, as I went back to GNOME (Wayland) about four years ago.
> because a lot of essential features only work in phones which are extremely expensive with less specs compared to its peers and in normal phones
I assume you are refering to the Librem 5? These days the Google Pixel 3a is coming close, as multiple people report reliable phone calls. Camera is still lacking, but once libcamera add auto-focus and the device gets a driver for the focus actuator (already in the works), it's going to be just as competent with better battery-life for less than USD/EUR 100. On the more pricey side, the Fairphone 5 has a good mind share and contributor count, making it quite likely that remaining issues are being solved soon.
With not-quite current hardware as supported by Pocketblue, performance is not that much of an issue, despite the OnePlus 6 being introduced in 2018. GNOME Shell mobile is quite smooth on it.
That said, if you want to start without the entire Linux desktop stack, you can, and there's even a project that already does something like that IIUC: https://sr.ht/~mil/framebufferphone/
Nitpick regarding apps: https://flathub.org/en/apps/collection/mobile/1 is the better link IMHO, even if not all apps in it do actually perform great on mobile [0], and some apps that work well on Mobile are not part of the collection due to lacking some bits in app metadata [1]. Help with sorting this out is very much welcome :-)
This is a really cool project, and IMHO the most important new-comer in the #MobileLinux distro space in a long time, as it takes a model proven on desktop, building upon a well-run distribution (Fedora) and applies it to mobile.
I have yet to attempt daily-driving it, but just trying it and easily switching mobile shells (e.g., from Plasma Mobile to Phosh) so easily[0] without have weird side-effects from the previous environment has been quite exciting!
> The new ICE's speed is actually lower than previous generations.
While not the fastest ICE, the new ICE-L (assuming you refer to it) with a top speed of 230km/h, is not actually slower than what it is supposed to replace on most routes: InterCity trains, topping out at 200km/h.
ICE-L, btw, was planned to be a IC train, but just like before with IC-T/ICE-T (same top speed of 230km/h), and IC X (ICE 4), DB management has a tendency to decide next-to-last minute, that new vehicles must earn money and thus get rebranded ICE, which is both more prestigious and (at least in a fictional world without "Sparpreis") pricey.
TL;DR: This would be outrageous if ICE-L was to replace ICE 3 (neo; 320km/h +) services - but it is not.
Please note that user reviews are only out for the FLX1, not the FLX1s, which is about to start shipping soon. That said, as they went with the same SoC, hardware enablement is hopefully going to be fine and the software will work as well as on the FLX1.
I have their FLX1 device here, but I have yet to spend more time with it (instead of my postmarketOS daily driver I am writing this on). It's humongous (the s is going to be smaller), which is holding me back - but feel free to ask questions.
What's nice is that it's 5G hardware, and as they use the (4.19 IIRC) Android kernel they have a lot of hardware working which would be a huge struggle on mainline (think photography, finger print, ...). The Android integration via a Waydroid fork is also decent (but 'basic waydroid' is IMHO fine too, the hardware just needs enough RAM), and overall, it feels quite polished and the team is responsive in adressing customer feedback where they can.
Initially, due to the PinePhone not using libhybris but a mainline kernel, the SailfishOS browser and mail app was not working at all. At least the browser was fixed; mail later on AFAIR too. Generally, judging an OS that has officially supported hardware by an unfinished community port is not something I would call fair or useful ;-)
That's their US made patriot phone, the regular less than half of that. Also, please read up on the concept of economies of scale.
If you go with postmarketOS (good!), and don't want to touch anything that touched Purism, better avoid anything GTK (Phosh, GNOME Mobile and related apps). While Purism did not make a competitive phone, their investments into libre software went great and keep paying off.
I am pretty sure that it's not going to be the Librem 5, despite Purism's efforts to get it RYF certified (which, thinking of the Redpine WiFi card) went so far that they seriously impacted user experience.
Why? There's no Android port for that device and they keep mentioning LineageOS.
Even the PINE64 PinePhone would be more likely, as that has Android support and even some LineageOS 22 support [1]. The Replicant project had eyed it as a target device [2].
That said, I'd expect a different device, and, assuming LineageOS supports one, and I would not be suprised to see a device that's not powered by a Qualcomm, Mediatek or Samsung SoC.
Climate crisis and WW2 do not compare. Many people died in WW2, but entire animal and plant species were not wiped out.
We're killing what we eat (and what we eat is nurtured by) at a rapid speed, at scale. This will first show in bearable price increases (as it already does with coffee and cocoa) and only get worse from there, think famine (in regions where this has not happened in a lifetime).
Good luck with keeping a civilization 'stable' when people are hangry at scale.
And the worst part is: While war can be ended, un-extincting is not a solved problem at all.
That said, Google Play is not really the thing to compare this too. F-Droid could be. Summing up the "Show all ..." counts, F-Droid clocks in at 6147 apps, and it started way earlier (2009? 2010?).
Some of these F-Droid apps (specifically those created in QtQuick or Flutter) should also run with very minor tweaks on #MobileLinux.
Also, there's more than these 720, some are just very hard to evaluate (because they are for hardware or services I don't have/use), which then keeps me from adding these apps.
Honestly, given my experience from distro hopping, I am certain that collecting solutions across distributions and implementing them in one can go very far. It's almost as if distributions contributors too rarely try out other distributions to then steal what the other distribution does better.
Small enthusiast distributions with a bit of a hype can gain good features in by just pulling in knowledgable users missing things from their previous distro - and they can move a lot faster than the Debians or Fedoras of the world can, no committee decisions to be made first.
The accidental pasting definitely kept happening to me, likely due to my bad habit of highlighting sections while to focus on them.