Well, and how these reasoning justifies the need of ActiveX (the solely reason of IE8 installation) in order to fill in a web form?
Since you don't need 40 people and a couple of $700/hr partners to build a web form, they broadened the scope of the process to pick low hanging fruit or synergize paradigms.
That may make no sense to you, but I'm sure it sounded good at the 16th hole (and 4th cocktail) at the country club when the $700/hr partner was pitching it.
To (hopefully) install a shim that lets them install software that lets their help desk help their customer more effectively. If I were trying to support millions of 'ordinary users' and had them calling me every time anything didn't work the way they expected, I'd want something on their desktop that let me help them (a gotomypc type of agent, for example).
I'm not sure if anyone can justify the need for ActiveX in this case.
ATT's homepage for DSL customers is Yahoo, and it is heavily Flash dependent. The same logic that serves as part of the justification for Apple's iOS strategy underlies ATT's decision making - reducing options to reduce support costs and enhance user experience. It is better if Grandpa's introduction to the internet has everything working when he lands on your homepage for the first time.
Again, ATT knows their market segment.
I think that's overly generous. Aaron Patterson spoke at RailsConf. He said he works for AT&T, and to submit an expense report, he scans paper receipts to a PDF, emails that somewhere, which converts the PDF to a fax, which faxes it somewhere else to be converted back into a PDF.
That is clearly a stupid process. It's not there because AT&T has analyzed the business logic; it's there because a large, old business can accumulate layers of bureaucratic process more easily than a small, young one. There are more committees and more inertia. And maybe if you make billions, wasting thousands of dollars worth of employees' time doesn't make you sit up and take notice.
I'd guess this web form is a similar problem. If you have a 5-person company, everyone in the company hears customer feedback and maybe talks to customers personally. I doubt the CEO of AT&T even knows this form exists.
The fact that they are leveraging legacy business processes rather than reengineering them for the sake of aesthetics (keep in mind thtat even with reengineering Aaron would still be scanning his receipt and the person in accounting would still be dealing with a PDF and it doesn't cost them anything to use idle bandwidth because they own the pipe).
Don't misunderstand me, ATT doesn't get any of my money because of my past dissatisfaction with them. My point is that it is a mistake to misinterpret their webpage in the way the article does.
[edit] In fact the process of converting PDF's into faxes and back into PDF's makes a lot of sense from a document management standing because it will convert Aarons 2400 dpi 32bit scan of a Chili's receipt to the 100 dpi 1 bit image which is sufficient to do the job. Thereby reducing long term storage costs, standardizing the stored format, and almost certainly integrating with the initial portions of the office automation system which no doubt were designed to convert faxes from the field into digital documents for use by accounting staff.
Well, that's one way of interpreting it. Another way is to say that AT&T is a monopoly provider and therefore has no incentive to cut costs. The fact that the setup process is baroque doesn't cost AT&T anything - its not like customers have a plethora of alternatives for their broadband access. So, what AT&T optimizes for is cost of development, and I can assure you it was cheaper to develop this "solution" using half-trained consultants than it would have been to develop a well-designed setup page using experienced software engineers.