You may as well have said that Amazon is living on JVM mostly and look how rich and happy they are as company.
It would be a much stronger argument :)
Sometimes things happen not thanks to, but inspite of.
You may as well have said that Amazon is living on JVM mostly and look how rich and happy they are as company.
It would be a much stronger argument :)
Sometimes things happen not thanks to, but inspite of.
I am not working at Amazon. If anything, you can view my post history and see my disfavor of big tech.
If you have something more substantial to say, please do it, but a sarcastic/snark remark isn’t jt
I'm just saying that your arguments doesn't refute my point, nor supports it. Your success with java doesn't mean that java world is not full of legacy and suffering for many other teams.
It has nothing to do with my company, and so interesting your rebuttal to my comment was snark and about an entirely different company.
Here’s your original comment.
> “if you commit in 2022 to java/scala - you subscribe to heavy 20yo over-engineering legacy, whether you want it or not”
And now you said:
> “Your success with java doesn't mean that java world is not full of legacy and suffering for many other teams.”
You painted a broad brush stroke, and I shared personal evidence of a successful business running on JVM.
Now you’re painting another brush, indirectly saying this case is exception or somehow doesn’t matter.
If you have something meaningful to say, or any particular experience on what my organization should watch out for (some blind spot), call it out.
It feels like you’re not here to teach or inform, this is more about you being right. Everyone can have an opinion. They’re worthless unless you have something actually constructive to add.