Because the business case isn't there, in terms of the cost/benefit. It's a lot of work (maybe not initially, but maintaining that functionality on an ongoing basis slows development), to support a tiny number of users, who you can't make any money advertising to (if you're ad-supported) and who are probably not the kind of users who buy much (if you sell directly).
The sad bit about this attitude is that some of us consider web design/development to be a craft, rather than purely an exercise in profit-maximisation. We should be creating the very best work that we can, not just aiming for what's good enough, then stopping. That's just an opinion; I realise it's unpopular with some.
Overengineering is the biggest problem with the craft today. True craftsmanship is about giving the customer something appropriate to their needs, not making a magnum opus every time.
Comments
Because the business case isn't there, in terms of the cost/benefit. It's a lot of work (maybe not initially, but maintaining that functionality on an ongoing basis slows development), to support a tiny number of users, who you can't make any money advertising to (if you're ad-supported) and who are probably not the kind of users who buy much (if you sell directly).
The sad bit about this attitude is that some of us consider web design/development to be a craft, rather than purely an exercise in profit-maximisation. We should be creating the very best work that we can, not just aiming for what's good enough, then stopping. That's just an opinion; I realise it's unpopular with some.
It is not unpopular. It is unrealistic.
Overengineering is the biggest problem with the craft today. True craftsmanship is about giving the customer something appropriate to their needs, not making a magnum opus every time.