This post was marked non-constructive, probably because of the tone of the opening line, but the criticisms here are valid.
The author of this post has minimal training, graduating high school in 2018 with no college listed. They were a "technology specialist" (sys admin) for about 10 months in 2019, and their current "job" listing is a Discord community volunteer. They have a grand total of 7 LinkedIn connections. I have more connections to recruiters for companies I ended up not working for, and I really don't spend much time grooming my LinkedIn profile (it's just kind of expected in tech).
This is not to put Hanna down, only to speak to their experience level. They clearly seem very smart, able to learn quickly, and to have a passion for development. I wish them well in this pursuit!
But the point is that at this point in one's experience, their opinions on languages should be very measured and reserved. One can certainly talk about pros and cons they've encountered or details they like and dislike, but be careful about making broad claims about things like performance. And making general claims about the "feel" of a syntax rather than objective analysis is very revealing about one's lack of experience and depth of knowledge about syntax and language design. While I certainly have criticisms of the syntax of languages, or at least design decisions that were made (e.g. the C++ syntax for lambdas is very magicky), just saying one syntax "feels" weird just means a lack of exposure to it. It would be much more meaningful to critique the readability of one over the other, and I can give scores of ways Python is more readable than C++, even when both are written with a good code style -- and these are my 2 most-used languages!
Experienced developers can also list lots of ways that JavaScript has problematic syntax and design, too. It's really popular more for historical support reasons than because it's a "good" language. In fact, there is a big movement in tech to try to make it optional on the browser side, too, with WebAssembly. Much of the work around JS is focused on avoiding writing actual JS. Nobody with experience would recommend JS as a first language due to its quirks, except for some web devs who eat, sleep, and really only know JS.
I'm a full stack software engineer, linux system administrator, tech support specialist, and LGBT+ rights activist. I love old technology and collect old computers. Come say hi!
Thank you for being respectful! You make very valid points, but please do keep in mind my post(s) are purely my opinion, in a lot of cases! Could probably specify that more.
And you should absolutely keep writing about them, whether it's on here or even just in discussions with other devs. It makes you think about language design and style, and often sparks an interest into why something was done that way (hint: it was usually a compromise, probably for backward compatibility). Any time spent thinking deeply about programming will just make you a better developer. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This post was marked non-constructive, probably because of the tone of the opening line, but the criticisms here are valid.
The author of this post has minimal training, graduating high school in 2018 with no college listed. They were a "technology specialist" (sys admin) for about 10 months in 2019, and their current "job" listing is a Discord community volunteer. They have a grand total of 7 LinkedIn connections. I have more connections to recruiters for companies I ended up not working for, and I really don't spend much time grooming my LinkedIn profile (it's just kind of expected in tech).
This is not to put Hanna down, only to speak to their experience level. They clearly seem very smart, able to learn quickly, and to have a passion for development. I wish them well in this pursuit!
But the point is that at this point in one's experience, their opinions on languages should be very measured and reserved. One can certainly talk about pros and cons they've encountered or details they like and dislike, but be careful about making broad claims about things like performance. And making general claims about the "feel" of a syntax rather than objective analysis is very revealing about one's lack of experience and depth of knowledge about syntax and language design. While I certainly have criticisms of the syntax of languages, or at least design decisions that were made (e.g. the C++ syntax for lambdas is very magicky), just saying one syntax "feels" weird just means a lack of exposure to it. It would be much more meaningful to critique the readability of one over the other, and I can give scores of ways Python is more readable than C++, even when both are written with a good code style -- and these are my 2 most-used languages!
Experienced developers can also list lots of ways that JavaScript has problematic syntax and design, too. It's really popular more for historical support reasons than because it's a "good" language. In fact, there is a big movement in tech to try to make it optional on the browser side, too, with WebAssembly. Much of the work around JS is focused on avoiding writing actual JS. Nobody with experience would recommend JS as a first language due to its quirks, except for some web devs who eat, sleep, and really only know JS.
Thank you for being respectful! You make very valid points, but please do keep in mind my post(s) are purely my opinion, in a lot of cases! Could probably specify that more.
And you should absolutely keep writing about them, whether it's on here or even just in discussions with other devs. It makes you think about language design and style, and often sparks an interest into why something was done that way (hint: it was usually a compromise, probably for backward compatibility). Any time spent thinking deeply about programming will just make you a better developer. :)