3 ms·
Your issue is with the developers, not the language. Stop working with bad devs. And honestly you should revise your own attitude as well, it's a poor worksman
by scrollaway 8y ago
Your issue is with the developers, not the language. Stop working with bad devs.
And honestly you should revise your own attitude as well, it's a poor worksman who blames his tools. What you keep complaining about in TS is the rigid backwards compatibility which, should it not be there, you'd probably be the first one to post angry comments about.
Your assertion that decent devs stay away from typescript is incorrect. If you think staying away from it makes you personally a decent dev, yikes.
- yakshaving_jgt 8y ago> it's a poor worksman who blames his tools This is such a ridiculous common myth, and I've been hearing it repeated my entire life. While not everything, tooling does matter an awful lot.
- scrollaway 8y agoAnd typescript is a fantastic tool. Yet, the commenter in question keeps blaming it for ills that have nothing to do with it.
- Cthulhu_ 8y agoIt does matter, but if you have a problem with a tool you need to make an informed statement about it. Instead of yelling "Go needs generics!", look up the original reasoning behind the lack of them first - because they DID think about it, long and hard. (as an example)
- oblio 8y ago> Instead of yelling "Go needs generics!", look up the original reasoning behind the lack of them first - because they DID think about it, long and hard. (as an example) A lot of the people complaining about Go lacking generics knew about this and were just saying that the Go designers' conclusion was wrong, based on existing evidence: the myriad languages supporting generics without major issues. If conservative languages such as Java and C# could get generics in 2005, surely Go could have gotten them as well, back in 2012.