Not exactly sure what your point is here - Will simply explained that there is a known bug related to compression and ajax.
It - I believe has been resolved in 5.6.2beta - or alternatively - turning of compression for the time being in 5.6.1 at the hosting level
also resolves the issue.

No one is holding a gun to your head - if you find a better solution to you needs - move to it.

Alternatively, if you have a better solution to aspects of DNN
 - get involved - join a core team or a module team - contribute your code and ideas
 - thats why the tools developed by Joe and Will and Brandon were originally there
 - they got involved and contributed.

If you WANT a different login process - CODE ONE - honestly it would take you less than a couple of hours if you have any programming skills. 
Thats the whole point of dnn - its an open framework - it has authentication providers you could code against.   And if you believe so passionately about your new and improved login process - after you have completed it - offer it to the CORE.  Alternatively - if it is something that only requires a change in the core login module - submit the code changes as recommendations to gemini.  Mind though if it were to BREAK 500,000 dnn sites functionality then it may not be accepted through the validation process ... so you mileage may vary.

Same thing goes for Amazon S3 capabilities - you want them in the core - how about you look at getting involved and contributing instead of expecting others to do the heavy lifting. Those that have released commercial options have done so because they saw a need - if you are willing to give your time for free to see something contributed to the core - more power to you - but if not well . . .

Just my 2 cents.

Westa