I agree with you on portability. If that's a concern, and you're a web developer, I'd say TypeScript is a more obvious choice than Go, Ruby, etc.
Re: "tools are better, more modern, with broader library support" - I would need a lot of evidence to convince me this is the case, particularly for Ruby and Python.
I would need a lot of evidence to convince me this is the case, particularly for Ruby and Python.
Both Django (python) and Rails (ruby) are great, popular and well supported environments with very "broad library support". This is a bizarre statement.
So your defense of broader library support is that each of them have one framework to choose, where php has dozens of web frameworks, all of which have broad library support (often sharing libraries between them)
Comments
I agree with you on portability. If that's a concern, and you're a web developer, I'd say TypeScript is a more obvious choice than Go, Ruby, etc.
Re: "tools are better, more modern, with broader library support" - I would need a lot of evidence to convince me this is the case, particularly for Ruby and Python.
Both Django (python) and Rails (ruby) are great, popular and well supported environments with very "broad library support". This is a bizarre statement.
So your defense of broader library support is that each of them have one framework to choose, where php has dozens of web frameworks, all of which have broad library support (often sharing libraries between them)
Why is that evidence that they are _better_ than PHP's ecosystem? That's the claim I'm skeptical of.
I just found it weird that you singled out the two languages that are the basis for two of the most popular web development frameworks.