- Nov 4, 2021
Yes, it means more effort to program it, obviously. But no, one doesn't have to test every combination which would indeed rise exponentially. On top of that, having post numbers is a long-solved problem and something that used to be implemented, so really shouldn't be hard to make optional. I'm not saying to make everything optional either, but this is a major forum feature, one that just about every other forum software has and that does matter. Why would other forum software implement it if it wasn't useful and / or important? After all, it takes development time, effort and cost, just like you're saying.Making things optional is a surprising bane of development and something that a lot of people seem to assume is easy.
It’s honestly not. If you were to have a test system that could test every combination of options, a simple on/off switch doubles the test cases each time. 5 on/off switches = 32 possible combinations. 10 on/off switches = 1024 combinations. 20 on/off switches = 1048576 combinations.
And then if you don’t have tests for all the things people get upset when things are buggy.
It is not sustainable to make everything optional, and to a point nor should it be. I’d rather platforms make their choices and run with it, with plugins for things that people do or don’t want.
It’s kind of the same as the Microsoft Word problem. Everyone uses 2% of its functionality but everyones’ 2% is different.
I really dislike being forced into developer limitations, quite often for no good reason and I'm including everything in this, not just computers. One design niggle with my car for example: with the driver's side electric window, one can let the button go and the window keeps going up or down until it reaches the end of its travel. Great, just how I like it, but none of the other windows do. Instead, I have to hold that sodding button all the way. Why not make it at least a cost option on the passenger side front window? One that I operate quite often, not so much the rear windows. I find it really irksome that I can't have it at any price. One can again argue about design and production costs bla bla bla, but I still bet they could have offered it. It's crap like this, the post numbers and other similar niggles one sees in many things that bothers me.
Re the Word problem example. That's actually a great reason to stuff it with as many features as possible so that it caters for the needs of the widest selection of customers possible. Quality code will avoid many bugs and there's always patches at a later date when bugs are found, as happens anyway.
And in the end, there's this point: they have the right to remove a feature and piss off their customers and I have the right to walk away from their product when said missing feature is important to me. Everybody's happy, or unhappy depending on viewpoint.