Hmm. I've never been asked to do formal proofs for my code. Where does he work?

I skimmed through what the TX governor/attorney general/whatever it's called said, and I don't think he even understands "privacy". All he's bothered about is that the data is going to China instead of American companies.

Probably not, because it costs a lot more CPU cycles.

Or a lot if you use privacy extensions.

Cloudflare's automatic checks (before you get the captcha) must be pretty close to what ad peddlers do.

> the data/power standard supported by the physical connection isn't optimal

How polite. It can be useless, not "not optimal". Especially since usb-c can burn you on a combination of power and speed, not only speed.

> 1. This is great and Mozilla is listening to it's core fans

It's not great. Great would be "we'll stop wasting money on extraneous features and we'll concentrate on making Firefox the best browser".

This is damage control.

> torrent search levels of trustworthy

Proper torrent search sites have a comments section that you should check before downloading anything :)

They do have a point though, because you can't continue to use a phone made by Apple in 2010.

I would if I could!

Apple has been a mess since they lost Steve Jobs.

> One of the differentiators between iOS and Google was a lack of ads

Newsflash: the first slot in an app store search is an ad that is not marked as such. Your extra $100 are already wasted.

Here's a nice ad I ran into recently:

https://imgur.com/a/sq1HFHK

I was trying to install microsoft authenticator and the first "result"... I don't want to know what that is.

If they add more ads at the top I suppose I'll have to only use external searches to install apps.

You say it's not marked as an ad, but in that image there's a clear blue "Ad" label. Are there cases where that label is not present?

Seriously? I haven't noticed it.

Maybe it's clear to you... or you work in marketing and have a different definition of "clear".

Note that this is a screenshot from a hi dpi iphone that went through a few upload/download/reencode cycles [1] so it lost all density information. On the real phone screen the "Ad" thing is extremely tiny and unnoticeable.

[1] Downloaded it from my work chat where i posted it as a warning to my colleagues a couple days ago.

A clear blue ad label!! Is this sarcasm? Your remark is so dystopian, you full accepted this as normal.

Btw, I'm checking now, the label "ad" is not there, it's just highlighted. Or is it that blue tag? I thought that signified in-app ads? Shouldn't the highlight itself have a label? Probably this is some A/B test optimized BS, that tag was the option where most people WRONGLY clicked on the stuff they didn't search for.

When I came from Android I first couldn't figure out why app store search was so bad. Dumb me, expecting the highlighted option to be something most relevant to ME and MY search, no it's most relevant to some paying company and can even be a scam. And you and me can reason through this, but my kids get this BS as well, the grow up with this as normal.

You search for something, you don't get what you search for. This is our normal.

Absolute disappointment on day 1 with iOS.

My next phone will be something like FairPhone with e/OS or Sailfish. Or I'll wait for that Graphene hardware partner stuff to finally be revealed. I'm so sick of this bs. You pay a lot of money for something and they slap you with ads. Same on smart TVs, my Philips Hue system (hundreds, maybe thousands of euros I spend on that), ads ads ads.

This is the same experience on Play Store. 100% of the time, the top result when I search is NOT what I want but something completely irrelevant or downright fraudulent and/or misleading. And Google is complicit in this fraud by even selling no 1. search results.

I'm surprised that this wasn't brought up during trials as an argument against Apple's supposed "curated" walled-garden. There is a bunch of dangerous scammy junk on there.

I think I ran into one of the most dangerous situations without looking for it. What happens if you install the first result and put your microsoft account credentials in...

OMG, this requires it's own submission here on HN, I suggest you do it, this egregious. How low has Apple sunk. This is "the luxury brand" people.

Meh.

Context: we're migrating to MS cloud services at work from Google so everyone is setting up accounts, authenticators etc. Pretty seamless migration overall btw, guess our admins worked like dogs.

So I post this screenshot in a work chat as a warning (that's why i still have it). All my Android using colleagues tell me "it's the same in the Play Store, watch what you click."

So it really is normal, wherever you go. We're not even surprised about it, let alone outraged.

We've lost.

Or maybe Apple lost. I haven't used their store for application discovery since i had an iPad 1 and it was the latest model.

Yeah it's so cheap! The whole app store feel like that: I go there to install an app I know and need, and am immediately slapped in the face with anime girl dating games. WTF. I feel ashamed if people would see my screen like that.

Absolute garbage experience, and I came from Android expecting to "the luxury platform", I paid 2x what I usually do for a Phone. What a disappointment in step 1.

Were you paid to learn it?

Because last time I wrote systemd units it looked like a job.

Also, way over complex for anything but a multi user multi service server. The kind you're paid to maintain.

Why would a server use a different init system than a desktop or embedded device?

Why wouldn't you want unit files instead of much larger init shell scripts which duplicate logic across every service?

It also enabled a ton of event driven actions which laptops/desktops/embedded devices use.

> Why would a server use a different init system than a desktop or embedded device?

The futzing around with resolv.conf(5) for one.

I take to setting the immutable flag on the file given all the shenanigans that "dynamic" elements of desktop-y system software does with the file when I want the thing to never change after I install the server. (If I do need to change something (which is almost never) I'll remove/re-add the flag via Anisble's file:attr.)

Of course nowadays "init system" now also means "network settings" for some reason, and I have often have to fight between system-networkd and NetworkManager on some distros: I was very happy with interfaces(5), also because once I set the thing on install on a server, I hardly have to change it and the dynamic-y stuff is an anti-feature.

SystemD as init replacement is "fine"; SystemD as kitchen-sink-of-the-server-with-everything-tightly-coupled can get annoying.

> Why wouldn't you want unit files instead of much larger init shell scripts which duplicate logic across every service?

Indeed, that criticism makes no sense at all.

> It also enabled a ton of event driven actions which laptops/desktops/embedded devices use.

Don't forget VMs. Even in server space, they use hotplug/hotunplug as much as traditional desktops.

>> It also enabled a ton of event driven actions which laptops/desktops/embedded devices use.

> Don't forget VMs. Even in server space, they use hotplug/hotunplug as much as traditional desktops.

I was doing hot plugging of hardware awo+ decades ago when I still administered Solaris machines. IBM/mainframes has been doing it since forever.

Even on Linux udevd existed before systemd did.

> Why would a server use a different init system than a desktop or embedded device?

The server and desktop have a lot more disk+RAM+CPU than the embedded device, to the point that running systemd on the low end of "just enough to run Linux" would be a pain.

Outside embedded, though, it probably works uniformly enough.

I think you're way overstating things. Systemd units can be complex, but for most things they are dead simple to write.

> a multi user multi service server. The kind you're paid to maintain.

TIL. Didn't know I can get paid to maintain my PC because I have a background service that does not run as my admin user.

A systemd service can be:

  [Service]
  Type=simple
  ExecStart=/usr/bin/my-service

If this is a hard job for you well maybe get another career mate. Especially now with LLMs.

The thing to me is that services sometimes do have cause to be more complex, or more secure, or to be better managed in various ways. Over time we might find (for ex) oh actually waiting for this other service to be up and available first helps.

And if you went to run a service in the past, you never know what you are going to get. Each service that came with (for ex) Debian was it's own thing. Many forked off from one template or a other. But often forked long ago, with their own idiosyncratic threads woven in over time. Complexity emerged, and it wasn't contained, and it crrtainly wasn't normalized complexity across services: there would be dozens of services each one requiring careful staring at an init script to understand, with slightly different operational characteristics and nuance.

I find the complaints about systemd being complex almost always look at the problem in isolation. "I just want to run my (3 line) service, but I don't want to have to learn how systemd works & manages unit: this is complex!". But it ignores the sprawl of what's implied: that everyone else was out there doing whatever, and that you stumble in blind to all manners of bespoke homegrown complexity.

Systemd offers a gradient of complexity, that begins with extremely simple (but still offering impressive management and oversight), and that lets services wade into more complexity as they need. I think it is absolutely humbling and to some people an affront to see man pages with so so so many options, that it's natural to say: I don't need this, this is complex. But given how easy it is, how much great ability to see the state of the world we get that SysV never offered, given the standard shared culture tools and means, and given the divergent evolutionary chaos of everyone muddling through init scripts themselves, systemd feels vastly more contained, learnable, useful, concise, and less complex than the nightmares of old. And it has simple starting points, as shown at the top, that you can add onto and embelish onwards as you find cause to move further along the gradient of complexity, and you can do so in a simple way.

It's also incredibly awesome how many amazing tools for limiting process access, for sandboxing and securing services systemd has. The security wins can be enormous.

> Because last time I wrote systemd units it looked like a job

Last, an LLM will be able to help you with systemd, since it is common knowledge with common practice. If you really dislike having to learn anything.

Yeah, I've been using Claude and Codex to create bespoke systemd services for my random tools and automation stuff and have been really impressed by how easy it is and how rock solid they are once setup. It's really nice not living in constant terror that a reboot, network connectivity loss or gentle breeze will cause my duct taped scripts to collapse under their own weight.

Somehow that's never enough though.

I dunno man. The past was a shit show & you seem extremely resistant to trying at all.

I struggle to figure out what it is that the systemd haters club actually struggles with, what is actually the hard parts. I do in fact sometimes use a 3 line .service file and it works fine. It feels like there is a radically conservative anti progress anti learning anti trying force that is extremely vocal that shows up all the time everywhere in any thread, to protest against doing anything or learning anything. I really really am so eager to find the learnable lessons, to find the hard spots, but it's almost entirely the same low grade discursive trashing with no constructive or informative input.

It feels like you use emotional warfare rather than reason. The culture I am from is powerless against that if that's all you bring but I also feel no respect for a culture that is so unable to equivocate what the fuck it's problems actually are. Imo we all need a social defense against complaints that are wildly vacuous & unspecific. Imo you are not meeting any baselines for taking your whinges seriously.

> unable to equivocate what the fuck it's problems actually are

... or doesn't care to discuss it any more. RedHat's push was succesful, linux is not a hobby OS any more, you won.

I can agree with you that linux needed something better than sysv init.

I can't agree with you that this monolithic solution that takes over more and more services is better.

> Because last time I wrote systemd units it looked like a job.

Fascinating. Last time I wrote a .service file I thought how muhc easier it was than a SysV init script.