Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try !politicaldiscussion
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I find this question very interesting. What does it mean to "know" a programming language. They map to certain paradigms for how to solve problems, in various degrees, with different tradeoffs there for surrounding tooling, libs, and what not.
A bunch of the most familiar ones are procedural with different sprinkles on top, and they pretty much do the same things when it comes to the "language" side. So, "knowing" one, or another, IMO, has little to do with the syntax, parsing and keywords, and is much more if you have suffered through cryptic compile errors, figured out good debugging tooling, etc.
Which is to say, if we compare these two list
I'd consider the first one much more impressive in terms of diversity in "knowing programming languages". And, I say that as someone belonging squarely in the latter.
Yeah this question seems weird. Isn't programming less about knowing and more about solving?