This all makes sense, but it doesn't really apply to D12, because this site is frankly not built as a business. It is "just" a group of volunteers who want a nice place and community to play Risk
It is for that reason that we're not really in the mindset of making sure we have all the features from "the competition". I think each Risk community has its own feel and its own ideas about what should be part of the site and what shouldn't, so I think it shouldn't be seen as a problem that D12 lacks some features other sites might have: that just represents a difference in underlying principles, and it's what gives multiple Risk sites the right to exist.
We'll never please everyone here at D12, and if some people find exactly what they seek in another website, then power to them.
So yeah, I understand where you come from. I've been through the whole thing you have described, though before all the technical analysis happens, a product analysis happens too on whether adopting this feature and moving the product in this direction is desirable in the first place. It is too simple to say that this is a "must have" feature, and because we don't have the resources to do proper market research, we have to rely on community discussions like these, and programmers have to make judgement calls on what they work on, keeping in mind both all the technical aspects, as well as the product aspects.
I am not so much concerned that this will really fry the servers or be months of work to implement, but I still dislike it when people pretend to know how easy it is to implement, and use it as an argument against the programmers of this site: "why doesn't this exist yet??? it's so easy to implement!!!" I hope this post, in combination with some of my other posts above, clarify that (1) it remains a non-trivial problem to find a good solution for, even if the technical challenges are easy to solve and (2) this site is not run as a business, but as a group of passionate volunteers who do what they can in their free time, and the best way to get features you want is to have respectful conversations with the programmers about the features you would like to see, with the expectation that there's a good chance they simply can't.
This all makes sense, but it doesn't really apply to D12, because this site is frankly not built as a business. It is "just" a group of volunteers who want a nice place and community to play Risk :) It is for that reason that we're not really in the mindset of making sure we have all the features from "the competition". I think each Risk community has its own feel and its own ideas about what should be part of the site and what shouldn't, so I think it shouldn't be seen as a problem that D12 lacks some features other sites might have: that just represents a difference in underlying principles, and it's what gives multiple Risk sites the right to exist.
We'll never please everyone here at D12, and if some people find exactly what they seek in another website, then power to them.
So yeah, I understand where you come from. I've been through the whole thing you have described, though before all the technical analysis happens, a product analysis happens too on whether adopting this feature and moving the product in this direction is desirable in the first place. It is too simple to say that this is a "must have" feature, and because we don't have the resources to do proper market research, we have to rely on community discussions like these, and programmers have to make judgement calls on what they work on, keeping in mind both all the technical aspects, as well as the product aspects.
I am not so much concerned that this will really fry the servers or be months of work to implement, but I still dislike it when people pretend to know how easy it is to implement, and use it as an argument against the programmers of this site: "why doesn't this exist yet??? it's so easy to implement!!!" I hope this post, in combination with some of my other posts above, clarify that (1) it remains a non-trivial problem to find a good solution for, even if the technical challenges are easy to solve and (2) this site is not run as a business, but as a group of passionate volunteers who do what they can in their free time, and the best way to get features you want is to have respectful conversations with the programmers about the features you would like to see, with the expectation that there's a good chance they simply can't.
“This is how humans are: We question all our beliefs, except for the ones that we really believe in, and those we never think to question.”
- Speaker for the Dead, O.S. Card