OOP existed before Javascript. The OOP Languages, all strongly typed, existed before the SOLID principle and had their roots in languages like C. C has been around over 60 years. The stability of these languages make for excellent choices.
Design patterns were over hyped, with just 2 concepts needed 1. Single responsibility pattern and 2. Favor composition over inheritance. Both are equally applicable to Javascript.
Most Javascript folks do not understand OOP and have little appetite for it. Most OOP find Javascript to be inferior and open source libraries are megalithic messes.
But none of that matters because we personally should choose to take the position that pays the most.
That's why I know 4 of the top 6 languages. It's also why I am comfortable with Functional and OOP styles.
I know many languages (from a list with the 10 most in-demand langs of 2022 I just found, I know 8) and worked with OOP and FP (and logical programming, and everything in between). Also you seem to think I'm coming from a Javascript background, which is not really true. And I saw many of the mistakes from the misunderstood OOP paradigms. Even Alan Kay wasn't too thrilled about the object-oriented implementation in C++ (and thus also Java, C# and every other following OOP language) - btw, C was not considered object-oriented.
Those two concepts you mentioned (Single responsibility and composition) are fundamental in the functional paradigm. It has been the very fundament of function purity and immutability.
"But none of that matters because we personally should choose to take the position that pays the most."
I strongly disagree. If you are doing this job for the pay, well, okay, I won't judge. But I for one am not in for the money - it just happens to be very lucrative - but I think no company would want to pay me enough for me to even consider working with Java ever again. And I don't have to.
Another topic you're touching on is this 'lang A is better than lang B' BS. Sorry, to say it, but many Java developer always looked down on PHP devs. But far too many times I saw how PHP solutions were running circles around Java developers when it came to get a project done. The same goes for Javascript or anything else that does not deemed worthy by others. It doesn't matter: The only thing that matters is if something gets done. Period.
To wrap it up. Yeah, I don't like OOP (as implemented in most OOP language anways), and not because I do not know it, but because it makes things unnecessary hard in my opinion. It never made sense to me. FP on the other hand clicked immediately. It made sense from the start. But that's just me.
First please don't apply my comments personally. I never mentioned your name, rather I mentioned only facts from my perspective.
As for you, if you prefer to work for 50% of what could be earned that's totally your choice.
With today's high inflation and real estate costs, I find it much more comfortable to be easily able to provide for my family by having a higher paying job.
I also never said or alluded to C being object oriented.
As far as OOP being hard, you may have missed what I said, we only need SRP and Compsition. Both are simple concepts.
As far as 'better languages', it's just a truth which some folks are too blind to see.
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.
OOP existed before Javascript. The OOP Languages, all strongly typed, existed before the SOLID principle and had their roots in languages like C. C has been around over 60 years. The stability of these languages make for excellent choices.
Design patterns were over hyped, with just 2 concepts needed 1. Single responsibility pattern and 2. Favor composition over inheritance. Both are equally applicable to Javascript.
Most Javascript folks do not understand OOP and have little appetite for it. Most OOP find Javascript to be inferior and open source libraries are megalithic messes.
But none of that matters because we personally should choose to take the position that pays the most.
That's why I know 4 of the top 6 languages. It's also why I am comfortable with Functional and OOP styles.
I know many languages (from a list with the 10 most in-demand langs of 2022 I just found, I know 8) and worked with OOP and FP (and logical programming, and everything in between). Also you seem to think I'm coming from a Javascript background, which is not really true. And I saw many of the mistakes from the misunderstood OOP paradigms. Even Alan Kay wasn't too thrilled about the object-oriented implementation in C++ (and thus also Java, C# and every other following OOP language) - btw, C was not considered object-oriented.
Those two concepts you mentioned (Single responsibility and composition) are fundamental in the functional paradigm. It has been the very fundament of function purity and immutability.
"But none of that matters because we personally should choose to take the position that pays the most."
I strongly disagree. If you are doing this job for the pay, well, okay, I won't judge. But I for one am not in for the money - it just happens to be very lucrative - but I think no company would want to pay me enough for me to even consider working with Java ever again. And I don't have to.
Another topic you're touching on is this 'lang A is better than lang B' BS. Sorry, to say it, but many Java developer always looked down on PHP devs. But far too many times I saw how PHP solutions were running circles around Java developers when it came to get a project done. The same goes for Javascript or anything else that does not deemed worthy by others. It doesn't matter: The only thing that matters is if something gets done. Period.
To wrap it up. Yeah, I don't like OOP (as implemented in most OOP language anways), and not because I do not know it, but because it makes things unnecessary hard in my opinion. It never made sense to me. FP on the other hand clicked immediately. It made sense from the start. But that's just me.
First please don't apply my comments personally. I never mentioned your name, rather I mentioned only facts from my perspective.
As for you, if you prefer to work for 50% of what could be earned that's totally your choice.
With today's high inflation and real estate costs, I find it much more comfortable to be easily able to provide for my family by having a higher paying job.
I also never said or alluded to C being object oriented.
As far as OOP being hard, you may have missed what I said, we only need SRP and Compsition. Both are simple concepts.
As far as 'better languages', it's just a truth which some folks are too blind to see.