> 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.
Yeah, I didn't feel like looking up the exact details, so thank you for adding that. I didn't know that it was rebranded like that, I was just baffled at the outcome. Our mechanical engineering professor was responsible for the ICE breaking system a long time ago and those guys were all extremely good.
The other aspect is that there is a whole host of periphery issues, one of which is track maintenance, making it so for a lot of segments the ICE will not reach its top speed.
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.
no i wont. it is literally that simple. the regular device has 3 gb of ram. the flagship has 4gb for 4k and released 4 years ago. also yeah i do try to avoid anything gtk but not for any particular reason. i just prefer qt.
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.
You make it sound like the Redpine card ended up being shitty because of RYF efforts. The Redpine card was chosen because of its internal flash, but the fact that the vendor failed to properly support the advertised features (and even removed some that worked before), abandoned its mainline driver and pretty much halted the firmware development after SiLabs acquisition is orthogonal to that and could have happened with a different card as well. So nice it was a replaceable M.2 card, isn't it? ;)
> Why? There's no Android port for that device and they keep mentioning LineageOS.
The LineageOS folks are working on supporting their OS on Linux-first devices running a close-to-mainline (not AOSP) kernel. So it could go either way. Of course if they do choose an Android-first device, their efforts would ultimately also make it easier to run a mainline kernel on it as shown by projects like pmOS.
> 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.
Is there any actually relevant alternative to this oligopoly? Apple doesn't sell to third parties, NVDA lacks a baseband and so does (to my knowledge) Broadcom, and it's been ages since I saw anything from Intel in the mobile space.
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.
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.
> "USB-C 2.0" in the specs reveals that. DisplayPort Alt Mode requires at least USB 3.0, the PinePhone Pro would be a Linux phone supporting that.
That's not quite accurate IMHO, as the OG PinePhone also supports the feature, despite being USB 2.0. The fact that PINE64 only got it working in PinePhone hardware revision 1.2a maybe also reveals why few phones (whether they support USB 2 or 3.*, e.g., the Pixel 8 was the first Pixel phone to support the feature) actually support DisplayPort Alt Mode: It does not just add cost for parts, but also makes the design more complicated (and may require multiple design iterations to get right, which are expensive).
So: If DisplayPort Alt Mode or somthing like "USB-C video out" is not mentioned, you can usually safely assume that the device does not support it.
> 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.