To mention a big one, Go is mostly statically and strongly typed, in stark contrast to Javascript. Also it has significantly fewer misdesigns (such as the equality operator being weird). Are you claiming that such features don't matter for the effectivity of the platform?
I can appreciate that not everyone likes JavaScript - it's all a matter of personal preference I guess - but saying that Go is a better language because of the syntax is like saying bananas taste better because of their color.
They are two very different languages with each their strengths and weaknesses. Does JavaScript have a few design flaws? Absolutely! More so than many other languages? Quite possibly! Does it make me write worse software if I'm aware of those quirks? Most certainly not.
No need to bring up syntax. It's a superficial feature and has nothing to do with the actually important features I listed.
> Does it make me write worse software if I'm aware of those quirks? Most certainly not.
Is there some limit where good language features stop mattering? I guess we would obviously agree that creating web software with x86 assembler wouldn't be a good idea -- even if we could imagine a comparable library/framework situation.
No but the difference between static typing and dynamic typing actually does. Go compiler performs a lot of optimizations that no Javascript engine can.
If you are talking about the callback queue getting too full and causing delays you may have a point, but the objections that you have raised are quite petty.
Are you certain that that is true, or do you think it might just be that you're so used to the dynamic woes that you nearly ignore them?
That designing requires thinking, and thinking takes your attention away from whatever your goals are, whether you are used to it or not.
Strong type systems come with their own things that require extra thinking, but I think it is less than what is required to write robust dynamically typed code.
Many projects don't need truly robust code. Then, the dynamic language may still win.
Well, that's your bias. As I said in practice I don't see a problem. And also, as I said, there are static analysers, and you really HAVE to have strong type you can always use typescript.
But you seem to imply that you implement strong type checking into all(?) your functions yourself and think that is a better solution than having your platform do it for you automatically and systematically. Or is it about the freedom of not doing it?