I had pixel 7, broke a screen and got a pixel 8. Apart from desktop, which I dont use, I haven’t noticed almost any significant day to day difference between the two.

Oh, definitely I’m not saying people should just jump the gun and replace their distro for one without systemd immediately. I certainly won’t, at least not without thinking about it for a while. But I also think that denying the controversy exists is not good. This is definitely controversial, for some people even a deal breaker and there are valid, real reasons why. For the rest, it’s good to look at what options there are, see that there really isn’t an appropriate alternative for systemd in some cases and realizing that a successful fork would be a good thing. Also, a long time criticism of the community has been that systemd does too much and it being against basic Unix philosophy. I always thought of it not being a big deal, given its modularity. But I now realize that it centralizes control and design decisions to a single org and that is certainly a weak point IMO. So a fork makes a lot of sense, but it is at this point a mammoth of the project, so it will be really hard to maintain.

Yes, but what’s wrong with this? If you gather engineers that are capable to maintain it - what is the downside? Systemd could always have used a bit of competition, I think most of us can agree. Most of the forks of systemd will fail, but most of all projects fail after some time. I don’t think this situation will harm systemd ultimately and it shouldn’t.

I agree with all that you’ve said. But why add it now? Why haven’t they added it a long time ago? Or if now they remembered, why not other extra optional fields that some people might want, like gender, sex, any other field? Oh, it would be too political? I see…

Wow, some good news on Lemmy? Sign me up!

Yeah, im in a similar situation. Curve doesn’t work in my country and banks don’t have their own solution. And google pay won’t work on my grapheneos pixel.

At least the last one won’t happen, as banks would have to be on board. And banks are not on your side with this one.

It would affect a lot of users, then it will indirectly affect you too, as a lot of devs won’t be as interested in maintaining their apps for so few users. But I hope it will at least give a bit of a push to developing postmarket os. I personally am sure going to get a second hand phone to install postmarketos too and hope I can contribute at least a little bit. I am prepared to suffer, at least a little bit for the right cause.

Removed by mod

Calm down dude, not everyone expressing an opinion is automatically a pedo. I also get enraged to a thought of a child getting hurt, but don’t lose your brain. Like you could have argued that the doll is not where a pedo would stop, it would encourage him to move on, or that a doll like that existing is normalizing pedophilia, but instead you raged out. Censoring exchange of opinion does the opposite of preventing pedophilia. Instead, I’d be interested in a study that would explore whether having dolls/cartoons etc would do anything to decrease the number of child molestation in any meaningful way. If not - I’m on board for banning stuff like this. This argument against banning dolls, though not being particularly strong, does express some logic. Your comment actually does more harm than good by jumping the gun so hard, IMO.

There is an extension for Firefox for blocking shorts. You lose the shorts button and any short you access through a link is converted into a regular, full size video.

I agree with everything. Compiled, GC language was weirdly missing. Also, I think that exceptions are not a particularly good error handling solution. But it’s weird to have a GC abstraction and goroutines built-in, yet not have support for any other abstraction for programmers. Just seems not well thought through language from the start.

True. But I would argue it makes more sense comparing python to rust than go to rust. Scope of use cases for python is more similar to rust. Other than that - sure, you can compare Haskell and x86 assembly too, though it would be of little use.

I’m not proficient enough in Go to say how good or bad it is, but I have tried it in the past and it made and immediately not like it. Verbose syntax, no null safety or any error handling, no templates at that time, people literally copy/pasted the code of containers for different data types and did find/replace on it. The only feature that was kind of convenient is goroutines. For my money, Kotlin and even Java were more modern looking and would prefer them to go any day. Also not apples to apples comparison, but far more similar than rust.

Is it just me or does comparing go and rust make very little sense? Other than being popular and relatively new, they have almost nothing else in common. Rust is multi domain language design to be as versatile as possible, very intentionally limited with a set of carefully chosen constraints. Not intended to be particularly easy or quick to use, by design. Go is very clearly web-biased, centered for backend, microservices, not universal by design. Syntax very C like, verbose, feels low level, but actually batteries included. Really, the only thing in common with rust is that it is very popular with developers, but again for very different reasons. People who like rust often hate go and vice versa. You can tell by the comments in this thread too.

Well, there’s hydrogen, but that has its own downsides. Like it’s a bit explody, for example.