Live data from Hacker News

Closing this as we are no longer pursuing Swift adoption

github.com

331–332 of 332 posts

Re: Closing this as we are no longer pursuing Swift adoption

#331

Earlier quoted context omitted.

In the last years, simplistic languages such as Python and Go have “made the case” that complexity is bad, period. But when humans communicate expertly in English (Shakespeare, JK Rowling, etc) they use its vast wealth of nuance, shading and subtlety to create a better product. Sure you have to learn all the corners to have full command of the language, to wield all that expressive power (and newcomers to English are…

>But writing and reading are asymmetrical and a more expressive language used well can expose the code patterns and algorithms in a way that is easier for multiple maintainers to read and comprehend. It's exactly the opposite. Writing and reading are asymmetrical, and that's why it's important to write code that is as simple as possible. It's easy to introduce a lot of complexity and clever hacks, because as the auth…

Then you should write assembly only. Like `MOV`, `ADD`... can't really get simpler than that.

Problem is, that makes every small part of the program simple, but it increases the number of parts (and/or their interaction). And ultimately, if you need to understand the whole thing it's suddenly much harder.

Surely you can write the same behaviour in "clever" (when did that become a negative attribute?) or "good" way in assembly. You are correct. But that's a different matter.

Re: Closing this as we are no longer pursuing Swift adoption

#332

Earlier quoted context omitted.

Avoiding interacting with LLVM as a user doesn't mean you've created something equivalent to LLVM. And if the C compiler you use is clang then you're still literally making use of LLVM.

So what you're saying is that C source code is the (only) stable LLVM ABI ;)

Haha, yes
Post reply on HN