Earlier quoted context omitted.
The building is packed all week. I don't think that keynote-only attendees are a significant factor here. If the two were separated, then maybe it would have sold out in 80 seconds this year instead of 70 seconds. Big deal. The imbalance between the number of people willing to pay $1600 for the conference and the number of tickets available is so enormous by this point that there's simply no way to make it fair. It d…
So one interesting thing is that the "two disparate events, one conference" problem goes a little deeper. There seem to be four "things" you get out of WWDC: 1. Meeting with people (can be achieved without a ticket and just going to SF that week) 2. The sessions (many of which are recorded and thus largely don't require a ticket, but some are not I think?) 3. The keynote (not actually important for developers) 4. 1-o…
I agree that #2 isn't all that important (although there are probably some people who learn better in that sort of environment) and #3 is basically just a free show that you get with your ticket and could easily be made completely separate.
I like the idea of a week that's just focused on direct contact with engineers, but I fear that it would end up in very inefficient uses of their time due to being flooded with people asking basics because they couldn't be bothered to watch the intro sessions. In general, I fear what would happen without enough structure. But perhaps it could be made to work, and it certainly seems worth considering.
The obvious first step seems like a bigger venue, though. Apple keeps saying they can't... but other companies pull it off, so I have to wonder why Apple can't.