It feels like anything is mowed down on the internet. I’ve been a dev for a long time too, and I never feel sure when I chose a stack for a new toy project (in my day job I rarely get to chose, so that’s a non issue there)
Honestly, I would advise to not pick a language based on popularity, hate, or whichever of those qualify as internet fame these days.
I would approach the question with what you want to get out of your toy project. Do you want to get something done? Then pick a language that is close to what you are already familiar with. Do you mainly want to learn something? Go with a language with concepts you are unfamiliar with, eg. pick a functional language if you mostly do OOP stuff or pick a low level language when you mostly do high level web stuff.
My advice, generally speaking, is: When you do something in your spare time, don’t spend it on things you already do at work. The way to improve in software development is to see problems from many different angles and to rethink the solutions you already know.
Whenever I tested something that sounds great yet it is slow to get adoption I end learning a reason why it it’s not growing. It’s good to learn what the reason is before you spend a lot of time on it
No amount of reading will replace experience.
At some point you will come to the place where you’ll be the one who know why something that sounds good won’t be and why it won’t get adopted, but if you only base your decision on the opinions of others, you’ll never really learn anything.
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
Honestly, I would advise to not pick a language based on popularity, hate, or whichever of those qualify as internet fame these days.
I would approach the question with what you want to get out of your toy project. Do you want to get something done? Then pick a language that is close to what you are already familiar with. Do you mainly want to learn something? Go with a language with concepts you are unfamiliar with, eg. pick a functional language if you mostly do OOP stuff or pick a low level language when you mostly do high level web stuff.
My advice, generally speaking, is: When you do something in your spare time, don’t spend it on things you already do at work. The way to improve in software development is to see problems from many different angles and to rethink the solutions you already know.
Whenever I tested something that sounds great yet it is slow to get adoption I end learning a reason why it it’s not growing. It’s good to learn what the reason is before you spend a lot of time on it
No amount of reading will replace experience. At some point you will come to the place where you’ll be the one who know why something that sounds good won’t be and why it won’t get adopted, but if you only base your decision on the opinions of others, you’ll never really learn anything.