I would say all of those reasons are poor ones for not learning something further - I dislike the syntax of some of the languages I use for instance - but my liking of the syntax has nothing to do with how well that language can solve my problem. Learning curves being too steep can definitely make it difficult to try something out, or really get to know it well in order to judge it properly, but in that case I would say - break it down into simple parts so it can be evaluated in a digestible format over time. Simply enjoying the toolkit you are most familiar with is something I see many developers suffer from, but again, at the end of the day this is not why we chose language/framework/lib a over b (hopefully) - we chose these things because they help us do are jobs faster/better and improve the end product. Also - not that this was the point of your post, but I wanted to say that while we all know using a tool just because of its hype is not great reasoning alone, neither is refusing to learn a tool because of its hype. Right tool for the right job<3
Maybe it's not clear in the post that those are examples of possible reasons, not the only existing ones.
Furthermore, when I mean refusing, I obviously don't mean ignoring a technology that is a best fit for a job because you dislike the syntax.
The idea of the post was to discuss which technologies had a peak of in popularity and yet you chose to not deeply explore it, not necessarily in a professional scope, but for personal projects.
I would say all of those reasons are poor ones for not learning something further - I dislike the syntax of some of the languages I use for instance - but my liking of the syntax has nothing to do with how well that language can solve my problem. Learning curves being too steep can definitely make it difficult to try something out, or really get to know it well in order to judge it properly, but in that case I would say - break it down into simple parts so it can be evaluated in a digestible format over time. Simply enjoying the toolkit you are most familiar with is something I see many developers suffer from, but again, at the end of the day this is not why we chose language/framework/lib a over b (hopefully) - we chose these things because they help us do are jobs faster/better and improve the end product. Also - not that this was the point of your post, but I wanted to say that while we all know using a tool just because of its hype is not great reasoning alone, neither is refusing to learn a tool because of its hype. Right tool for the right job<3
Maybe it's not clear in the post that those are examples of possible reasons, not the only existing ones.
Furthermore, when I mean refusing, I obviously don't mean ignoring a technology that is a best fit for a job because you dislike the syntax.
The idea of the post was to discuss which technologies had a peak of in popularity and yet you chose to not deeply explore it, not necessarily in a professional scope, but for personal projects.
No, it's clear - still feel the same way about those examples.
I know what you meant by refusing, hence my comment - "Also - not that this was the point of your post".
I have not had this happen to me - because I can't think of a reason why I would not explore a new technology deeply. Regardless of scope.
Sorry if I offended you, not my intent. If you have a suggestion of how I could explore this more deeply, as you say I am not - let me know.
When I said deeply explore it, I meant the technologies not the post.
Your comment was a valuable addition to the discussion. Sorry about my tone, last few days been rough