And none of his claims about the problems with frameworks are true. Frameworks are trivial to create and use. In fact, with most of my apps, the app itself is just a simple wrapper around a bunch of frameworks.
Which, by the way, is also how Xcode is set up. Have you looked how large the actual binary is? On my system, it's 35K.
-rwxr-xr-x 1 root wheel 35K May 1 22:12 Xcode*
Holy compression, Batman! No, actually, they just moved all of the actual code out into frameworks. Just like the clang and llvm teams put all their code into libraries, which gives us tools like the static analyser and Xcode-integrated syntax tools.
So even if I don't have plans to share the code yet, I still just put it in a framework target that's in the same project as the app itself, which takes around 30 seconds, and afterwards is no extra effort.
And the idea that only Apple can create software that is worthy of reuse...well fanboys be fanboys, but it actually isn't true.
No, let's skip technical details and your opinion about frameworks as code sharing primitive and get back to your words. You literally claimed that while Wil made money "leaning heavily on some of the most well-designed frameworks in the industry", he said "frameworks are bullshit".
This isn't true: he said that people shouldn't use a specific way of sharing code in OS X, not that "frameworks are bullshit". He even said that "Apple's shared frameworks are very useful for sharing executable code and its associated resources among multiple applications". He also praises Cocoa, the framework, and many other frameworks created by Apple.
So, yes, you did misrepresent Wil's opinion, and you should take your words back.
"The absolute worst thing ever, completely beyond bad, lower than horrible, and more crappy than explosive diarrhoea"
So when I wrote "bullshit", my only crime was that I was being euphemistic. Guilty as charged. And as I wrote, he makes this farcical distinction between Apple and the rest of the world.
So, no, I did not misrepresent Wil's opinion, apart from softening it up. So you should take your words back.
Which, by the way, is also how Xcode is set up. Have you looked how large the actual binary is? On my system, it's 35K.
-rwxr-xr-x 1 root wheel 35K May 1 22:12 Xcode*
Holy compression, Batman! No, actually, they just moved all of the actual code out into frameworks. Just like the clang and llvm teams put all their code into libraries, which gives us tools like the static analyser and Xcode-integrated syntax tools.
So even if I don't have plans to share the code yet, I still just put it in a framework target that's in the same project as the app itself, which takes around 30 seconds, and afterwards is no extra effort.
And the idea that only Apple can create software that is worthy of reuse...well fanboys be fanboys, but it actually isn't true.