1 Followers
4 Following
11 Posts
Hobbyist iOS developer, spending most of my time focused on SwiftUI on the client side.
Timothy Ryback on Hitler’s Terrible Tariffs. “By seeking to ‘liberate’ Germans from a globalized world order, the Nazi government sent the national economy careening backwards.” Hmm, sounds familiar… https://www.theatlantic.com/ideas/archive/2025/04/nazi-germany-tariffs-trade/682521/?gift=j9r7avb6p-KY8zdjhsiSZ5SRVYhols_ScRpkh12-5LE
Hitler’s Terrible Tariffs

By seeking to “liberate” Germans from a globalized world order, the Nazi government sent the national economy careening backwards.

The Atlantic

Ok thanks for the feedback. I get the optimization angle, but it seems a little heavy-handed.

That said, I probably wouldn’t have brought up the question at all except that the actual run-time effect wasn’t totally orthogonal to my expectations. Inefficient? Yes. Tossing out the dupes? Sure. But randomly drawing one of the entities in the wrong place… perplexing.

To be fair, the error did say it would cause unpredictable results so I guess I have to accept it!

🤪

Just out of curiosity, does anyone have any insight as to why the #SwiftUI implementation of ForEach requires unique/hashable entities?

I get that it's more efficient to not do the same operation on multiple identical entities, but I had a strange bug where I wanted to draw multiple paths to the screen, and having a matched set caused all paths but the first to be misrendered or not rendered at all.

I fixed the bug, but I'm curious about the design choice. Any perspectives out there?