It is a very long debate and honestly there is no ultimate good answer that can reveal the truth,
simply because it is different for everyone and other differences of interaction with people and languages etc.
So I just gonna write a little tidbits of personal opinion and point at few examples.
For each developers you gonna see a curve with high and low,
based on age and maturity, center of interests and experience, number of projects under his/her belt,
position and/or job title (junior, senior, lead, etc.), amount of people working
on those projects (solo, small indie teams 4-8 , medium teams 10-30 , big teams 50+),
type of projects, type of companies, and a lot of other closely or loosely connected parameters.
Maybe something like that
or something like this
Very rarely you will see two developers having the exact very same experience.
But eventually, with time, the more a developer keep at it, thoses experiences
should teach him/her that the more he/she develop stuff the less he/she knows about stuff.
That's the very nature of programming, you can not know it all, not in your lifetime,
not even over 10 lifetime, it just never stops as there is always something new to learn.
So yeah you can play the blame game: it's not my fault it is the programming language fault
because X or Y, it is the vendor fault because other stuff, it is the team fault because this or that,
it's the computer and/or server fault because it's too slow to compile that or to run this,
or any other kind of scape goat.
Some developers at some stage in their programing life will find themselves very confident
and super smart on how they solve problem.
Look at Donald Knuth's lifework about The Art of Computer Programming,
everyone agree that it is brilliant work but nobody really read it, and Knuth will probably not have enough time to finish everything.
Personally I don't care how anyone think how smart they are about programming
there is always someone standing on a higher mountain than you and that will be able to point out how stupid your code is, how inefficient your algorithms are, how inexperienced and dumb your solutions are, etc.
But that does not really matters, I mostly say this for the programmers (often guys) who just like to "compare the size of their dick".
Some will even be quite arrogant about it, that's the syndrome of "I'm doing that shit for few years now, and I think I know everything", but eventually then they hit a wall, something so big that even their preferred framework or programming language can not solve for them, something like a bug that keep resisting them and make them realise that finally, maybe ..., just maybe ..., they don't know everything.
Once you acquire a certain maturity, you will just accept that there is nothing perfect.
I don't quite know how to put this, but
our entire field is bad at what we do,
and if you rely on us, everyone will die.
It's funny because it's true
There is nothing that works, everything is broken, it is how it is.
You can blame nothing, there is no escape or excuses, there are just little pros and cons.
Maybe something work better for you in your particular situation, maybe you had bad experiences in the past with something else, maybe you just "gave up" and want to copy what others are doing because it seems to work for them.
There is no good answer.
Whatever programming language, platform or ecosystem you are choosing for yourself,
there is always gonna be someone else to criticise it at great length.
See this little story about functional programmers being arrogant.
Programming language bashing is part of our larger community of developers, you use N then someone using X will bash N, or all those stories about "why I moved from Y to X", "how we rewrite our app in N and got a much better app than with X", "from A to B and then back to A because B is shit", etc.
See also All your Programming language sucks and Your Programming language sucks.
So when I answered someone missed the point, let me be clearer
maybe for you, not for me, not for my specific apps, not for my specific situation
in my case AIR is pretty damn fast, but that's just me
who cares? not me
I mean that's where you missed the point
the whole post is about how AIR is a damn good tech to publish cross-platform on desktop and mobile
I could not care less about publishing on the web
so whatever the web is nearly as fast because of WASM or whatever
OK, good for you, useless for me
Simply put, you're telling me my language sucks
and I'm telling you: no, your language sucks
and we are both right, or both wrong
We are certainly not developers that are sharing the same experience,
and we are certainly not building the same kind of applications