They would have to sign another contract for another 24 months to get it, nobody was getting an upgrade on the existing contract because it’s just a bundle of Google services (One, YT Premium etc.) and financing on the phone. And if you don’t care about the services, Google’s two year financing is cheaper than this bundle.

Also looks like it’s removing an important visual affordance (i.e., which areas you can click to drag the window), unless I’m misinterpreting it

The top bar has been full of buttons with no whitespace for a year or more now, that’s not new (you can still drag the window using the whole bar, but it’s definitely not intuitive and made me subconsciously do Win+drag to be safe many times).

This seems to be a relatively minor visual update to have the left sidebar fill the whole window - maybe they want more space for shortcuts at a given window height? No clue.

Edit: never mind, checked again and it’s literally just a tiny visual update with no change to the actual content of the sidebar, but it takes some space away from the top bar.

Just focused on the stick to the left

Another pic: https://lemmy.one/post/2912284

(…) systemd is linux only. Ask why?

It is well known that systemd’s service management is built around cgroups, which is a Linux-only concept for now. Other OSs have their own ways to accomplish similar things, but adapting to that would require huge changes in systemd.

Am I able to run system-journal without any other systemd components running?

No, the only part of systemd project that doesn’t depend on systemd core is systemd-boot. And there’s also elogind, which is an independent project to lift systemd-logind out of systemd.

But honestly, I don’t see the issue here. You can’t use systemd’s components elsewhere, but your previous complaint was the opposite - that systemd is everywhere, as if you were forced to use networkd, resolved (which pretty much no distro uses AFAIK because it’s way worse than other DNS resolvers), homed, timedated etc. when you use systemd as init.

Also, I have a correction for my previous comment: systemd-journald is not an optional dependency, as it’s used as a fallback if the configured log daemon fails. I’ve only learned after writing that comment.

I know it’s hard to tell from the photo, but it’s way too narrow for that. It is a part of a bike path now, and there’s actually a sign on both sides of the underpass instructing cyclists to dismount because there’s barely enough space for two bicycles going opposite directions to pass. So I doubt it was ever meant for anything other than pedestrians.

From this point of view is systemd disaster because it is almost everywhere in the system - boot, network, logs, dns, user/home management…

That’s almost like complaining that GNU coreutils is a disaster from KISS point of view because it includes too many things in a single project - cat, grep, dd, chown, touch, sync, base64, date, env… Not quite, because coreutils is actually a single package unlike systemd.

The core systemd is big (IMHO it needs to be in order to provide good service management, and service management is a reasonable thing to include in systemd), but everything you listed are optional components. If your distro bundles them into one package, that’s on them.

A lot of it is actually already required. I can’t find any comprehensive list, but each new release since Android 10 (when modular components / Mainline became a thing) adds new components and makes some older ones mandatory for Google Play devices.

The eSIMs in phones are reprogrammable with new “profiles”, and Android can store multiple profiles and reprogram the eSIM with whichever one you want to use. Non-programmable eSIMs are only used in embedded devices.

Android 13 also has something called eSIM MEP that allows it to do dual SIM using a single eSIM chip.

Edit: here’s Android documentation for developers on eSIM MEP: https://source.android.com/docs/core/connect/esim-mep

Do you keep your phone charged above the battery saver threshold? My (fully updated) 7a sometimes decides it doesn’t want to do tap to wake when the battery saver is on. Never had an issue above 20% battery.

But even then, I still don’t get why that has to be the case. Linux still supports drivers for very ancient hardware.

Linux is kinda infamous for not having any stable driver interface - it doesn’t really have a concept of drivers in the way Windows does, Linux drivers are just indistinguishable parts of the kernel and their only way to interact with the rest of the kernel is to use the internal kernel functions that have no stability guarantee.

The idea is that if someone wants to change any of the internal functions, they will also be expected to go and find all parts of the kernel that would be affected and update them to work with the change. That works great for “drivers” that are part of Linux, but it makes maintaining out-of-tree drivers a nightmare.

This isn’t going to get any better until either Linux gets a stable driver API (fat chance) or SoC manufacturers decide to release their drivers under GPLv2 and go through the effort of mainlining them into the kernel (also a fat chance - current situation works great for them and guarantees more sales of new SoCs).

deleted by creator

Nothing wrong with someone picking a non-FOSS license for their work. And it’s a direct port of an existing closed-source client for Reddit, so there was never any reason to expect a different license.

It’s just another option with its own pros and cons. I wouldn’t pick a proprietary app if there’s a FOSS one that works for me, but I’m happy others have the option to decide for themselves what they value.

Ugh, I hate doing the TLS handshake. They don’t even give you enough time to work it out nowadays :/

I’m not defending Sync (I don’t even use it, I’m more of a Slide/Infinity guy; I’m just here to see how other Reddit app ports are doing), but Lemmy is not “months old”. It’s been a thing since early 2019, the recent Reddit drama just gave it a massive push bringing its userbase from negligible to tiny.

It generally tries to avoid updating apps while the phone isn’t charging, connected over WiFi and currently idle - I myself only charge the phone when it’s running low and I pretty much never get automatic updates (I have AppNotifier installed so I do know when it happens).

From time to time I let the phone charge overnight (with an alarm set so that the adaptive charging turns on) and it always updates all the apps during the night. I’m pretty sure the two hours it takes for normal charging is just too short to reliably trigger updates.

It’s a beta feature that’s currently off by default, but it’s pretty clear Google wants to force it eventually