It's also one of the funniest developer-centric things I've ever read - no holds barred for these guys in their contempt of the code they're ripping to shreds. Win/win.
Noting, too: the original Reifman article makes the truly odd presumption that because Amazon's _current_ workforce is 75% male, that all new hires will necessarily follow this same 3-to-1 male-to-female gender ratio - something I very much doubt. A company growing as fast and expanding into new, diverse areas like Amazon is, is likely to see a greatly more gender-balanced workforce than it had in its early tech-dominated early days. Maybe the new hires will not be 1:1 male:female - but certainly not the 3:1 of the past.
(*) Said author of the original debunked article also has the same user name as the submitter here - such a coincidence! I also note his last Slashdot submission was the also-debunked "OMG! Skydiver catches meteor falling on camera!" thing that was proven false a few days later. The Force is not strong with this one, fellow Jedi...
I'm actually quite happy with my 12mbit down / 5mbit up DSL link - not just because the bandwidth is plenty for my needs, but because the latency is pretty good (a canonical "ping 126.96.36.199", which should always resolve to a nearby Google DNS server, is about 25ms) - and it's pretty consistent at any time of day or night. (Unlike a theoretically fatter cable pipes, how many of my neighbors are watching pr0n doesn't affect my own speed since the DSL line is single-user all the way back to the DSLAM...)
Latency is especially important to me because I still do a lot of character-based terminal sessions and getting that single byte echoed back fast is golden. Given the option, I'd probably take a halving of present latency over a doubling of present bandwidth. Though with Gig-level fiber, I assume I'd get both....
Hey, folks, I can keep this up all day.
Tell you what. Let's go ahead and have you *moderate and run* (not just play with as an end user) a Yahoo group with 27,000 members in your spare time (as I do and have for many years). You get a week to do it with those "ancient" tools and interface, and then another week to do with with the badly broken, slow, ill-conceived, feature-poor, absurdly buggy new interface. After that week - if you can even get through it - come back and tell me that "Neo" is working just fine, thank you very much.
We won't even get started on your false dichotomy - that because some features might have been desired (eg inline attachments, which my users would never want or need) that it was necessary to completely revamp the entire interface and throw out about half the existing functionality to provide them.
And, of course, iron is at the bottom of the binding energy curve - it can't be fissioned or fusioned to provide net energy output.
My physics education is too far in the distant past to discern if these two things are just a coincidence - or significant feature resulting from the inherent structure of the table.
Someday somebody has got to decide whether the typewriter is the machine, or the person who operates it.