@tyil @SuperDicq @Vivaldi

“Generally a browser's most important thing is their engine.”

Think more, and you'll realise that #Vivaldi is an #exception. It's only #sellingPoint, as I said, is the #UI. There are many other #privacyFocused #browsers, #VivaldiBrowser's #powerfull #features are what keep it #afloat TBH.

"It's somehow fine for them to take the work of others, but this doesn't go both ways? Does this not sound a bit weird to you?"

If they make their work #available to be accessed by anyone, they'll die in the end. #VivaldiTechnologies is a much smaller company compared to #Google and #Mozilla.

"But even with Mozilla actively trying to make Firefox the worst it can be, the debloated forks are nowhere near as popular as the main thing, so your whole argument falls flat in reality."

No, it doesn't, because #FF was released much earlier than V. This means it had much more time to become #popular enough to keep it's #userbase, while Vivaldi wouldn't.

"forks are unlikely to become more popular than the main thing to begin with. They'd have to really fuck shit up to make a fork suddenly take all their marketshare, and at that point its just the market working as intended."

Yes, for more popular browsers. But for new ones, this is not true.

Jokes aside, the #Enshittification and #Enfattening of #Cars as well as spread of #CarCentrism #Propaganda from the #USA is a massive issue.

• #Affordable, #accessible and #available #PublicTransport is a non-negotiable necessity even if we don't give a fuck about #ClimateChange simply because at this rate, people will soon be unable to afford anything.

#Greedflation needs to be actively combatted by #regulation and that also means setting the right #incentives...

• For example, keeping Public Transport affordable and thus induce demand (See #DeutschlandTicket) is one way.

• Another Option is to prioritize #PersonalLightVehicles over #SuperUselessVehicles in terms of #RoadTax, #Parking and #regulation.

The #Netherlands were once almost as #CarCentric as the #USA [ @notjustbikes can propably vouch for that looking into the History, digging up 1960s & 1970s Amsterdam as example.] but they chose to do something about it with the fact that as a #German I can vouch for the fact that the Netherlands have excellent roads and far less traffic due to viable alternatives.

Since the dawn of SwiftUI, I've been using the (ill-advised, for multiple reasons) custom `if` view modifier as a last resort, which uses basically the same technique as the @davedelong's "Backport" system (with the same downsides, I imagine).

But you can't put an #available(…) check inside an `if` view modifier, and I've been annoyed by this for years. It turns out I just needed to make a slight change to make this work. 🙏