If this is considered self-promotion and it is decided to be flagged I will be OK with it. However, I think there are some ideas in this post about what we expect from programming languages and the general developer culture.
The discussion of what makes good and bad languages has been going on for centuries, and regularly brings up good and interesting points that some might not have heard before.
Your post is very broad and mixes different criteria: Popularity, aesthetics, usability, speed etc. You argue that people like different languages; some people irrationally like some and dislike others; not all programmers apply the same evaluation criteria.
The problem is - all of these are old arguments, and calls for open-mindedness are nothing new. I'd find it much more interesting if you talked about a technical, concrete example how one can benefit from open-mindedness. E.g.: Decouple your modules so you can use different languages side-by-side; write the same code in two languages so you can battle-test your implementations etc.
Obviously this discussion is not new. I tried to point out (with no success I guess) the fact that most developers adopt languages in a religious way, and criticize others ignoring the most basic reasons behind these languages.
Since you're a computer scientist - do you have an example for reasons behind languages that are misunderstood or unknown? I'd love to read a post about that.
Yes I know. And I have requested these changes for a while with no success. Google scholar algorithm does not distinguish me and that scientist, that is why it mixes everything. Thanks for mention it.
Perhaps it would help to have an ORCID for yourself - you could also link to that from your page. Many publishers and universities are beginning to automatically ingest ORCID data, so it's a good investment.
Most of the jobs at the SW industry are traditional office jobs, specially in consultancy companies. There is a task that has to be done. That's all. Nobody wants to be responsible for the problems that may appear after applying a "novel" methodology. And that is perfectly normal. At the end of the day most people want to have their job done and go home.
As a personal recommendation, if you are in a job where you observe many overcomplicated practices, stale methodologies, and a lack of innovation the best thing you can do is to look for another position. You may be surprised but there are more people like you around there.
Feeling this loneliness in your own projects is very common. They are somehow a long distance race. If you like it, you will find motivation sooner or later. Obviously, the lack of a paycheck for your own project may discourage you. However, nobody says it would be easy. Take into account that only because is a personal project, it does not mean that you will not find the difficulties of a real project. Lack of motivation is one of them.
Something that I find encouraging in my personal projects is to stop for a while, take breath, and realize of how much I have accomplished so far. It is probable that a little voice in your head will say "there is still a lot to be done". And maybe it is true. However, I think that satisfaction must be found in the daily task, not in the final outcome :)
