this post was submitted on 01 Sep 2025
37 points (100.0% liked)

Programming

22579 readers
12 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
37
Which is more important to you in a language, feature richness or documentation quality? (self.programming)
submitted 1 week ago* (last edited 1 week ago) by Sunsofold to c/programming@programming.dev
18 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Shirasho 3 points 1 week ago

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.