I would love for you to disagree, but for that to happen, you have to address the points of my arguments, which none of you have. The things you in particular

I would love for you to disagree, but for that to happen, you have to address the points of my arguments, which none of you have. The things you in particular mention goes towards my point, not against it. We are probably mostly in agreement when it comes to those. I know that: - it is easy to make a tiny framework - you can do that with both Java and JavaScript - that the translation layers really don't add much effectively - that you can program both languages without any library even I know all this. If you think that you have to tell me this or that I am wrong because of this, then you have missed the train. You can substitute Java and JavaScript there for ARM assembler. Do you get that? But if you as the proverbial CTO were to suggest going with assembler, people would (drum roll) use my arguments against you. Assembler needs a lot of Something Else to go on top of it and with it to make it generally useful. This is not to say that there's anything wrong with it in and of itself. But if you want to address cross-cutting concerns in a project, you are shit out of luck. You would invent a... drum roll... high level programming language to go with it. You would also likely want to have some sort of state management to go with that. And error handling, configuration management, various abstractions such that those become ergonomic to use. Please tell me you get the point now, because so far... you really haven't. I understand your points, but they are not directed at my point and we do not necessarily disagree about anything.