"slow" is on the eye of the beholder :). Maybe a week is slow for some, maybe a year is slow for others.
I can say this though, adding features comes at a cost. Not the programmer-cost of the feature though, all the other costs;
A) documentation. If it isn't documented, it doesn't exist. Good docs takes time and effort (and skill).
B) UI clutter. Most features require at least some UI to be added to the program. Menu item, check box, whatever. So 100 features later you have 100 little UI things, and it's starting to feel cluttered.
C) utility versus long-term maintainence. Add one more report, which only a tiny number of customers asked for (and none of them will actually use) and you will be updating that report _forever_. 100 reports like this later, and there's a lot of overhead.
D) training. Existing users will see this new UI. They need to be trained on it. Who's doing that? When?
E) overkill - simple programs appeal to people with simple needs. If Wordpad will do, the Word is overkill. Sometimes adding features means you're now targeting a different market, at a different price point.
F) security. Sure we can add JavaScript support. Not sure that's a good idea though. Features need to be thought-through from a security perspective.
G) price versus return. Sure it costs money to add this (plus all the above) - who's paying for that?
I could go on (translations, compatibility, partner products etc) but you get the picture...
Comments
"slow" is on the eye of the beholder :). Maybe a week is slow for some, maybe a year is slow for others.
I can say this though, adding features comes at a cost. Not the programmer-cost of the feature though, all the other costs;
A) documentation. If it isn't documented, it doesn't exist. Good docs takes time and effort (and skill).
B) UI clutter. Most features require at least some UI to be added to the program. Menu item, check box, whatever. So 100 features later you have 100 little UI things, and it's starting to feel cluttered.
C) utility versus long-term maintainence. Add one more report, which only a tiny number of customers asked for (and none of them will actually use) and you will be updating that report _forever_. 100 reports like this later, and there's a lot of overhead.
D) training. Existing users will see this new UI. They need to be trained on it. Who's doing that? When?
E) overkill - simple programs appeal to people with simple needs. If Wordpad will do, the Word is overkill. Sometimes adding features means you're now targeting a different market, at a different price point.
F) security. Sure we can add JavaScript support. Not sure that's a good idea though. Features need to be thought-through from a security perspective.
G) price versus return. Sure it costs money to add this (plus all the above) - who's paying for that?
I could go on (translations, compatibility, partner products etc) but you get the picture...