@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.

@natpanferova How are you handling using liquid-glass stuff while mantaining compability with older iOS versions? For me it gets quite annoying to have lots of` if #available` and sometimes separate views...
I've used #available(macOS 26.0, *) 54 times and counting. I think that’s a personal record for availability macros needed to support a macOS release.

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

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

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.

The Best Country in the World for Drivers

YouTube
RPG Cloudheim gets new Demo on Steam
https://gamenews.ie/?p=46480 #steam #available #cloudheim #demo #game #news #pc #rpg - Follow Us! Like! Subscribe!
And that's #TheLifeOfaShowGirl baby 🧡✨️

I obviously #listened to it as soon as it was #available 🤭✨️🎶🌙
#FirstThought I was a little #confused 😅 I was expecting more #glitterpen #pop but this gave more #sophisticated #jazzy #pop, #folklore meets #midnight meets #lover with a #funkpop vibe? I #love it tho!
I think my #fav song right now would have to be #ActuallyRomantic but only cuz I #LOVE the #pettiness 😂
But I'm also #obsessed with #TheFateOfOphelia , #ElizabethTaylor & #Opalite 🧡🤍
Which was VERY #Fourthwing #coded #EldestDaughter (I thought this was gonna be my #1) , #canceled (I hope its not about Blake😅) & #FatherFigure
I'm so excited for #ALL the #musicvideos to be out, she #hinted at some #eastereggs but I need to #deepdive !
I hope she gets her #wishlist but I really hope this isn't #goodbye 🥲🧡

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. 🙏

The if #available(macOS 26, *) { … } checks required to call newer APIs from apps that still run on older OSes are really cumbersome to use in SwiftUI.

This technique from @davedelong makes this much nicer and easier: https://davedelong.com/blog/2021/10/09/simplifying-backwards-compatibility-in-swift/

You might still have to do some manual mapping of enums and constants, but that ugliness is contained, leaving your call sites clean.

Simplifying Backwards Compatibility in Swift

Every year as new OS and Swift versions are released, the question comes up over and over again: “how do I use this new thing while also supporting older versions?”. While we have a bunch of “availability” tools at our disposal (and I’ll be using them in this post), they always come across as somewhat cumbersome: we need to do inline checks, or we have conditional logic flow that obfuscates the intent of some of our code, and so on.

Dave DeLong

Had a great stream building a backwards-compatible web view component for my "Second Brain" SwiftUI app.

The new native #SwiftUI WebView is fantastic, but we can't leave users on older iOS versions behind!

I built a wrapper that uses `if #available` to choose the right component—the new native one or an older WKWebView implementation—all bundled up in a clean new #SwiftPackage.

You can watch the replay here:
https://www.youtube.com/watch?v=OlHahqE43gA

How to Use the New SwiftUI WebView (And Support Older iOS Versions)

YouTube