Hey, it was out of date, so I decided to remove it.

And constructs like Text("hello" as String) that folks use are atrocious.

> all text for display is inherently localized

Except when it's coming from a property. I agree about the localization. I don't necessarily agree with this inconsistency with the API, which tripped me multiple times. As did the need for verbatim. In UIKit, it was never an issue.

Build my own SwiftUI with my own API design choices? I'd love to. The first thing I would do would be remove generics and add delegates. 😆

Text needed only two APIs:

Text(localized: "...") - localized
Text("...") – non-localized

As a non-native speaker, I don't know what verbatim means 😆

What I noticed is:
case - drops occasionally
no case - drops never

You drop iPhones? 😨

But Swift was introduced in 2014. Surely, nobody uses any Objective-C APIs or frameworks now, 10 years later? <sarcasm>

It finally stopped doing that after a few months of not using it for development 😬

There is probably a way to catch this. I’m mainly thinking about the scenario where you have one closure, non-ambiguous, and you don’t use any of its parameters. If there are multiple parameters, and you need one of them, it’s fair game to ask you to specify what you don’t use.

Yeah, that makes sense. The compiler could probably still show an error only when it is actually ambiguous. It’s uncommon to have more than one override like you’re describing.

I suspect that it’s needed to separate the parameters from the body of the closure. I would’ve probably preferred parentheses for parameters.

I’m constantly stressed out for the same reasons.

That was a good call. I’d probably look for some extended recap or something like it. I remember the first few episodes pretty well.

Carthage was probably my favorite due to its simplicity and reliability, but I prefer source distribution. I think my only problem is that Apple consistently seems to bite too much than it can chew and tries to be too clever. It shows in nearly every developer tool or features that shipped recently.

It’s non-scrollable. It works totally fine, especially if you pre-render on scroll. I’m just looking for the last potential optimizations and other ideas for improvement.

I want the web view to be interactive: text selection, links.

There is no limit to how complicated the HTML can get. I do have control over CSS, and I'm disabling JS.

I need to render HTML, so I'm kind of out of options, unless I want to re-implement a web-browser 😄