Perception: A back-port of Observable

pointfree.co

29 pointswallflower5 comments

I love seeing backporting efforts like this.

> But by some accounts, less than 50% of devices are on iOS 17

What are the current numbers? My reflex has been to check Mixpanel, but I don't know what a good source is these days. They have it at around 64% at the moment.

https://mixpanel.com/trends/#report/ios_17

What the hell happened to D3. All the latest tutorials began to be highly observable dependent, to the point that I prefer to use older D3 libraries just so that I can work my way through someone else's 2015 tutorial and come out with code that seems at least lean and clean.

This appears to be a different Observable (for Swift).

As both a D3 enthusiast and an iOS dev I find this comment oddly compelling. In fact I have always felt SwiftUI to be reminiscent of D3 given they are both declarative frameworks — I always think about d3-selection every time I am chaining modifiers in a SwiftUI view.

I usually disambiguate the Observable website by referring to it as "ObservableHQ", also I thought they were more focused on the relatively new framework Plot than d3 but I agree trying to translate d3 examples from ObservabelHQ cells to plain ol javascript is a severe PITA.

Glad to hear I'm not the only one struggling with this

Reply on news.ycombinator.com