Twitter | Search | |
🆆il 🆂hipley needs an acid vat Jun 6
Biggest complaint about SwiftUI is “VStack”is a shitty name. Especially since the varieties are “VStack,” “HStack,” and “ZStack.” You know, for vertical, horizontal, and zepth.
Reply Retweet Like
🆆il 🆂hipley needs an acid vat Jun 6
Replying to @wilshipley
The other (real) complaint is there’s no good reason this was secret. It’s not like Apple just invented reactive programming. This could have been done with community input.
Reply Retweet Like
🆆il 🆂hipley needs an acid vat
Apple’s making this common mistake where they’re like, “Oh boy, we created something amazing with help from a huge community working together — now we should add our own private surprise stuff because surely we know better than everyone else in the whole world combined.”
Reply Retweet Like More
Eric Van Der Binnt Jun 6
Replying to @wilshipley
At least one argument I can think of is wanting to proceed fast without forcing things down the throat of swift-evolution.
Reply Retweet Like
🆆il 🆂hipley needs an acid vat Jun 6
Replying to @Enzo90910
Yah this has been in the works for years.
Reply Retweet Like
Jeffrey J. Early Jun 6
Replying to @wilshipley
While I agree in spirit, in practice I side with Apple's approach. My experience with swift-evolution is that anything slightly out-of-the-box will be beaten down. One is better off developing on their own, then bringing fully implemented ideas back.
Reply Retweet Like
Manuel Maly Jun 7
Replying to @wilshipley
My theory is they wanted to lock down Combine APIs as much as possible because change requests from the outside would have slowed progress with SwiftUI code (constant refactorings).
Reply Retweet Like
Biappi Jun 7
Replying to @manuelmaly @wilshipley
i mean, it's not like the swift evolution process is bad at choosing naming and convention. *coff* *coff* fileprivate *coff* *coff*
Reply Retweet Like
Eric Van Der Binnt Jun 6
Replying to @wilshipley
Ok I am fooling nobody. This is just Apple.
Reply Retweet Like
Wojtek Czekalski Jun 7
Replying to @wilshipley @mpweiher
I am a little bit surprised it’s not open source. I expected the rendering layer to be private but I’d like to see the reconciler itself open.
Reply Retweet Like
Dan Jun 7
Replying to @wilshipley
SwiftUI involves the tooling of Xcode and there’s no way they are open sourcing that.
Reply Retweet Like