I know people who would claim clojure for productivity and expressiveness because they have to type fewer characters. Hellish option for real world engineering however.
You could argue shell or Javascript for productivity because if you give someone a new computer and tell them to write hello world, you’ll get it done fastest in one of those. If you ignore that silly hypothetical and give them a setup device then python or javascript are good for low time to productivity for any random developer a hiring manager might bring in. If you consider productivity from a long-term velocity rather than onboard speed perspective then code-base familiarity and tech debt are the big factors more than language itself. Languages that play well with older languages but eliminate headaches (like Kotlin for a Java based stack) are going to be the best options for productivity in a real world sense. If you just care about typing the fewest characters then perl or APL.
Design is going to be totally subjective. Go is popular. Functional zealots love Haskell or lisp for minimalism. Someone else mentioned Scala which I’d tend towards myself. Even Coffeescript (Rip) had a certain profane elegance.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
I know people who would claim clojure for productivity and expressiveness because they have to type fewer characters. Hellish option for real world engineering however.
You could argue shell or Javascript for productivity because if you give someone a new computer and tell them to write hello world, you’ll get it done fastest in one of those. If you ignore that silly hypothetical and give them a setup device then python or javascript are good for low time to productivity for any random developer a hiring manager might bring in. If you consider productivity from a long-term velocity rather than onboard speed perspective then code-base familiarity and tech debt are the big factors more than language itself. Languages that play well with older languages but eliminate headaches (like Kotlin for a Java based stack) are going to be the best options for productivity in a real world sense. If you just care about typing the fewest characters then perl or APL.
Design is going to be totally subjective. Go is popular. Functional zealots love Haskell or lisp for minimalism. Someone else mentioned Scala which I’d tend towards myself. Even Coffeescript (Rip) had a certain profane elegance.