After seeing this post I just thought it would be an interesting discussion. Obvious limits apply of ‘you have to have at least some documentation,’ so I’m not talking about something where there is none, and the feature set minimum would be less a question of whether you could complete X arbitrary project and more ‘does the feature set make it easy to do everything?’ You could essentially write everything in assembly, but would you want to?
On an arbitrary 1-10 scale, (1 being ‘I’ll build the features from nothing as long as the docs are good’ and 10 being ‘Who needs documentation? I’ll happily read through the undocumented code until I find the ones that make magic happen.’) where do your preferences lie?
Oh, and integers only. You can be nuanced in your ideas but no 5.5s allowed.
Depends on the intuitiveness of the UX. When it comes to API, as both a developer and an end user I would rather have it fully documented than have to spend hours digging through forums to figure out if something is even supported.
With that said, as much as I hate it, features lead to sales. When someone is shopping for a product they look at what it can do and whether it meets their needs. They don’t care how well documented something is. If it can’t do what they need they will look elsewhere.