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

Programming

23617 readers
68 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
39
Which is more important to you in a language, feature richness or documentation quality? (lemmings.world)
submitted 2 months ago* (last edited 2 months ago) by Sunsofold@lemmings.world 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
[–] MonkderVierte@lemmy.zip 1 points 2 months ago* (last edited 2 months ago)

Bad documentation was one of two reasons for me to steer clear of Iced and looking at Slint instead. The other being that the feature set didn't match but not as in less features but a different focus.

Edit: GUI frameworks, but the same goes for languages. Or even moreso, since at least half of a language is the concept/philosophy.