30 karma · joined July 6, 2020
Areas they could improve - what ever the heck is going on in their diffing ui for source control.
I'm doubting this is a comparable setup for the vast majority of swift users. Is it unfortunate for people who land on this edge case - yes.
My experience shows it's fast and our iOS apps build faster than a feature parity Android app.
At least 6 years old.
You're commenting on a post about an update... that they apparently don't do? What?
I'd say this is pretty disappointing that they keep pushing these kinds of mass surveillance laws "just in case".
A preferable alternative is to have the hosts moderate the content they serve that is publicly available. But there are cons to that too - what content should be reported etc.
I like the UI. What do you think they making worse?
Skill issue. *ViewRepresentable exists.
How could you know that? Not all the 'no's show up as a proposal. The proposal template also has an "Impact on ABI" section which you can use to guide your "can I ignore it"-sense.
> It sure feels like Swift governance is broken.
What is the actual problem though? Not enough features that you would use? But I don't see how this is a governance problem
Java governance: slow at times but mostly sane. C++ governance: I won't even open this can of worms. Swift governance according to you: too many features I will ignore.
I find you can do apply java and javascript type thinking to swift but they're less preferred.