STKFLT

Okay, so climate scientists openly researching and refining their theories around an extremely complex topic (carbon's continually changing relationship to every biosphere on earth) is evidence of... malpractice, conspiracy?

FWIW I was aware of the biosphere as a carbon sink because I learned it in middle school 20 years ago. Thanks for giving me a reason to learn about the interesting and difficult challenges in determining where and through which process that sinking is occurring :)

> If any Linux distro manages to replicate even 80% of the smoothness and functionality of a Mac trackpad experience, I'll switch

I find Niri to be a great WM for trackpad use if you are amenable to a scrollable-tiling workflow. All gestures are inertial like MacOS and to my fingers they often feel snappier and more natural than their macOS equivalents. Scrolling is consistent and natural, though which apps have inertial scrolling is definitely hit-or-miss. It perfectly recognizes three and four finger gestures. PikaOS (debian-based) and CachyOS (arch-based) both offer Niri as an option if you want to give it a try.

For context, my experience is on a 4 year old thinkpad which admittedly is probably best case for driver support but is definitely not the best touchpad hardware on the market.

I've never ridden a full suspension with a hub motor so I can't say, but my guess is that yes, it would make a pretty big difference with an aggressive rider or poor quality streets. It's not just keeping contact that matters, its the consistency and quality of contact, especially with a super torquey motor ready to jump at a twitch of your thumb. Its of course not necessary for commuter biking, but neither is basically anything on this premium product aside from the wheels and pedals.

Also to note, they are very much marketing it as a trail bike in addition to a commuter so it's not surprising they would spend a bit to optimize for ride quality and traction.

The biggest reason is minimizing unsprung mass, the performance of the rear suspension would be much worse with a hub motor.

I can't speak for all EVs but my Ford with a 400v hybrid system (DC-to-DC, no alternator) was able to keep operating perfectly with no 12v battery whatsoever. There was an assembly defect where the positive terminal connecting the battery to the fuse box eventually came partially loose and would disconnect as the engine bay warmed up. It would start up fine and drive with zero issues but then completely black out as soon as the car was turned off.

High frame rates (low frame times, really) are essential to responsiveness which, for those who appreciate it, is going to make much more of a difference day to day than the odd hiccup opening a large file (not that zed does have that issue, I wouldn't know as I haven't tried opening something huge).

I'm not sure what the process is like for Ubuntu, but if you just want something Debian-based then PikaOS has prebuilt niri ISOs.

> Am I missing something or is this WM/compositor more suitable to smaller displays which can not show all that many windows at the same time?

IMO smaller screens are where it shines, but you can also vertically stack within a column in Niri for similar density compared to tiling if you want.

> I keep track of which terminal goes where based on (among others) location.

I think this is a pretty nice benefit of Niri actually, having a second dimension to work with makes it much easier for me to keep track of windows because I can reduce the total number of workspaces and instead rely in part of relative location to other windows without being forced to fit all of them completely on screen. When I don't need my full screen real estate I often set up splits so that a little bit of the offscreen window is still visible and it makes it effortless to remember whats there.

Those are fair questions. This is what Apple says in the press release:

> Live Translation with AirPods uses Apple Intelligence to let Apple users communicate across languages. Bringing a sophisticated feature like this to other devices creates challenges that take time to solve. For example, we designed Live Translation so that our users’ conversations stay private — they’re processed on device and are never accessible to Apple — and our teams are doing additional engineering work to make sure they won’t be exposed to other companies or developers either.

We know it isn't necessary because Apple believes it is possible and are working on it. That's a pretty good indication that Airpods and their associated stack are currently being treated differently for a feature which fundamentally boils down to streaming audio to and from the headphones. It's not even clear how 'securing' live translated audio is any different from 'securing' a FaceTime call in your native language. I think a reasonable reading sans more technical information from Apple is that they give Airpods more data and control over the device than is necessary, and they want us to be mad at the DMA for forcing them to fix it.

Because the DMA legally obligates them to share those APIs when they are necessary to implement a feature for a connected device. The goal of the regulation is to promote healthy competition for connected devices by outlawing self-preferencing by massive players. Reasonable people can disagree about the goals or the downstream effects of the DMA, but creating Private APIs for connected device features absolutely falls under the umbrella of self-preferencing.