3 ms·
The presentation claims that Swift offers "progressive disclosure of complexity", but I don't really buy the argument. "Progressive disclosure of complexity" wo
by ngrilly 10y ago
The presentation claims that Swift offers "progressive disclosure of complexity", but I don't really buy the argument. "Progressive disclosure of complexity" works when you are learning a language and writing code, because you choose what language features you use. But it doesn't work when you read code written by someone else.
- coldtea 10y ago>"Progressive disclosure of complexity" works when you are learning a language and writing code, because you choose what language features you use. But it doesn't work when you read code written by someone else. So? Most app developers are small or one-person shops, and don't "read code written by someone else".
- ngrilly 10y agoThat's debatable. And even if it was true, most apps rely on open source libraries which are written by other developers.
- coldtea 10y agoThat's beside the point, since "Progressive disclosure of complexity" would still work for using those "open source libraries", as the most common case of bring a third party library into a Swift app would be to consume and/or extend its API, not refactor or maintain it. I've used lots of third party libraries and for the most part I don't care at all what's going on in their code as long as they work for what they do.