4 ms·
Nah you're probably just wrong. Generally speaking it's the older more experienced developers who demand typescript in my experience. Writing raw javascript is
by Tesl 5y ago
Nah you're probably just wrong. Generally speaking it's the older more experienced developers who demand typescript in my experience.
Writing raw javascript is genuinely painful, I literally don't understand how people can even do it. Like, how do you even refactor code safely?
- dimgl 5y ago> Like, how do you even refactor code safely? I've never had issues doing huge refactors in JS. But thanks for telling me I'm just wrong.
- FpUser 5y ago>" I literally don't understand how people can even do it." While I definitely appreciate types and normally work with the languages like C++ sometimes I do some front end JS libs and frankly do not have any mental troubles using plain JS. As for whether it is "safe" - all that matters to me if it works to specs and the customers are happy. Since I am programming since like forever I guess I've got enough discipline, common sense, knowledge and experience to produce decent code.
- ryohkyo 5y agoI think that’s where unit tests come in. In Typescript, I have seen “any” type everywhere that doesn’t make things any clearer.
- holler 5y ago> Like, how do you even refactor code safely? for me I make sure to write thorough unit tests along with clear, concise code
- steve_adams_86 5y agoI think you can combine that with static types and come out further ahead. To each their own though. I wrote code without any kind of autocomplete or tooling for a very long time because I felt like it. Sometimes when you don’t have something helping you all the time, it keeps you sharper.