Alex Grebenyuk

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 😆

Do not like this. I wish you had to explicitly specify where you need localization.

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

You drop iPhones? 😨

100% battery capacity after 5 months with 80% charging limit and never dropping below 20% – min-maxing the shit out it just because I can.

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 😬

[Pitch][Concurrency] Starting tasks synchronously from caller context Hello everyone, Continuing the trend of a few proposals improving the usability of Swift concurrency, especially focusing on task execution semantics... Recently we shared the [Pitch] task priority escalation handler APIs, which should be entering review sometime soon. And today I'd like to propo

Incoming new #swift concurrency proposal: making it easier to bridge async and non-async code!

Pitch thread: https://forums.swift.org/t/pitch-concurrency-starting-tasks-synchronously-from-caller-context/77960

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.

Swift got the syntax right. I think the only thing that annoys me day-to-day is that you have to add "_ in" in closures when you don't use the 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.

The problem with Severance is that I have no memory of how season one ended, as if my outie watched it and not me.

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.

Updating *.xcworkspace/xcshareddata/swiftpm/Package.resolved by hand because Xcode is incapable of doing it 🙃

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 😄

Does anyone know any great articles on using WKWebView in table cells? I'm looking for any potential pitfalls, the best strategy for cell-sizing, and what to look for in terms of performance.

I've set it up once and am still pretty happy with it. It took a bit of time to set it up, but it's a breeze to modify. Is there something you adjusted from this approach?

This still hurts

Time flies.

Robert Eggers has perfected his craft. I can't wait to see more from him.