One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Another post bashing one language to rise another.
π€π€?
The article is about the misconception that Kotlin is limited to Android.
It's not.
Kotlin is a great fit for me for doing backend programming on the JVM.
I'm not sure where you have read that I was bashing other programming languages.
I'm no fan of bashing other technologies that others find useful in their particular context.
Exactly the point. I came to read problems about Android being interchangeably used with Kotlin which is easy to understand because of JavaScript = Java problem from before :). But things like "I propose this rule of thumbs:
if Java is a good solution to a given problem,
then Kotlin is a great solution to the same problem"
are what this article has related to bashing. I did not want to rant about how someone is bashing something but more to open eyes of the writer. Things like the ones mentioned are actually this technology > other technology. That's what bugs me and I need to question it. I tried C# and Kotlin. C# was much better but I disliked the .NET Core in comparison to Micronaut & Spring. Kotlin was a pain and I had no actual benefits of it for my use cases. So I came here to see maybe something more than Kotlin > Java. And still not more than that I found. I guess you see the point now of why I feel this article had some bashing in it. I know it's not your intention but do try to understand of why someone might feel that way.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
I understand now why you reacted this way, you took my "rules of thumb" as an hint that I wanted to bash Java.
But really my intention was something else than bashing anything.
I do think that Kotlin is great for me (but happy that you have found something better for your needs). But the reason Kotlin is great is that it is standing on the shoulders of Giants
π€π€?
The article is about the misconception that Kotlin is limited to Android.
It's not.
Kotlin is a great fit for me for doing backend programming on the JVM.
I'm not sure where you have read that I was bashing other programming languages.
I'm no fan of bashing other technologies that others find useful in their particular context.
Exactly the point. I came to read problems about Android being interchangeably used with Kotlin which is easy to understand because of JavaScript = Java problem from before :). But things like "I propose this rule of thumbs:
if Java is a good solution to a given problem,
then Kotlin is a great solution to the same problem"
are what this article has related to bashing. I did not want to rant about how someone is bashing something but more to open eyes of the writer. Things like the ones mentioned are actually this technology > other technology. That's what bugs me and I need to question it. I tried C# and Kotlin. C# was much better but I disliked the .NET Core in comparison to Micronaut & Spring. Kotlin was a pain and I had no actual benefits of it for my use cases. So I came here to see maybe something more than Kotlin > Java. And still not more than that I found. I guess you see the point now of why I feel this article had some bashing in it. I know it's not your intention but do try to understand of why someone might feel that way.
I understand now why you reacted this way, you took my "rules of thumb" as an hint that I wanted to bash Java.
But really my intention was something else than bashing anything.
I do think that Kotlin is great for me (but happy that you have found something better for your needs). But the reason Kotlin is great is that it is standing on the shoulders of Giants
A Tribute to Java. Java-bashing is a popular past-time and⦠| by Roman Elizarov | Medium
Roman Elizarov γ» γ» 6 min read
Medium
Back to my article: I am a Kotlin backend developer and I receive almost every day a job offer to do Android... which I really do NOT want to do.
So I wanted to explain once for all that there is more to Kotlin than just Android.
The rule of thumb is to give recruiters a better idea of where Kotlin makes sense : mostly in the same areas where Java makes sense.