News for hackers. Stuff that matters.
Re:Swift Concurrency Roadmap by novok on Friday October 30, 2020 @09:06PM (#24948262)
Autolayout vs CSS is just a trade off on what layout algo you want. Haversine layout systems tend to be more computationally inefficient than flexbox actually, but more powerful. Yes the original programming API was horrible, but that was a quirk about how apple does API review, and they were mostly expecting you to use IB to do your autolayouts, and stuff like SnapKit put a sane API on top of it soon after.

TBH Obj-C once you looked past it's ugly syntax is a better developer experience than swift today if your making large-ish apps. Today the debugger is still buggy, build times are still way slower and swift code bases create stutters in unresponsiveness inside Xcode to this day. And it was way worse back in the swift v1-3 days.

TBH I think swift could solve a lot of their build speed issues if they removed type inference beyond a very basic set and brought back fine file grained importing like you have with C and Java. You still get %95 the benefits with a couple of features that most IDEs like IntelliJ with java are shown to be NBD.

Stuff like Flutter & Kotlin Multiplatform might make a lot of this stuff moot although, and swift will be regulated as an iOS compatibility layer and a nicer looking C++

Re:Swift Concurrency Roadmap by rudedogg on Saturday October 31, 2020 @02:20AM (#24949518)
> Haversine layout systems tend to be more computationally inefficient than flexbox actually, but more powerful.

I think you meant Cassowary instead of Haversine: https://en.wikipedia.org/wiki/Cassowary_(software)

Re:Swift Concurrency Roadmap by novok on Saturday October 31, 2020 @03:27PM (#24954440)
oops, brainfart :)