Quote:
Originally Posted by kjk
Yes, more hypotheticals, I get it, I get it. Do you really think the NYTimes gives a shit about people who have javascript turned off and thus "miss" the warning? We can make up stories about this all night to defend certain behaviors-let's not. I get it.
As I noted before, it is obvious to *me*..in *my* opinion, that the NY Times coders in fact did understand the limitations and workarounds, and proceeded with what they thought was the best balance they could find, given the realities of the web. And some people will drive around the barriers, intentionally or not. And some will actually pay the toll, not knowing how to go around the barriers. And some people will pay, because they understand the whole subscription idea, and find value in it. Even if they don't see the barriers at all.
(FWIW, I think the cost barrier is too high, at least for an iPad user who doesn't currently subscribe to the paper edition. But I'm not turning off Javascript. )
|
Y'know, maybe that explains the height of the cost barrier. Those who don't go around it will pay Bigger Bucks. And if you think about it, there are a lot of potential Big Bucks purchasers. The library. The corporate employer. The rich. There might be others. Enough for the NYT to make back its costs, & then some.
Maybe it's not a bug. Maybe it's a feature.