You got rid of 500 lines of test but you sacrificed flexibility. What if a new JavaScript developer ( who is not familiar with typescript ) joins your team? or your company should be exclusive for typescript developers?
Keeping JS or migrating to TS it's a decision that has pros and cons on both situations. It's up to you or to your company to decide what suits you the best and what to sacrifice.
TypeScript is a linter.
Typically, a linter does not enforce you to use a specific syntax neither the ability to transpile. TypeScript is a superset so technically it's a programming language itself.
If youβre not a Microsoft hater, then why mention it at all?
I mentioned it just to make it clear that my opinion is not biased by hatred toward Microsoft still you confused me with a Microsoft's hater.
Personally, I'm very comfortable with many of Microsoft products, I'm writing this from Win10 and I use VSCode occasionally but this does not mean I'll automatically praise any product Microsoft launch.
Though, I'm super happy with the recent contributions Microsoft has made for the open-source community.
What if a new JavaScript developer ( who is not familiar with typescript ) joins your team?
I would be really excited to pair-program with them until they feel comfortable with TypeScript. I'd be really excited to mentor them and to show the value of clearly communicating yourself in code. It's one of the reasons why I'm so passionate about this series I'm writing on TypeScript's emotional/conversational value: dev.to/cubiclebuddha/communicating...
or your company should be exclusive for typescript developers?
I would never dictate the technology for an entire company. The best companies are polyglot and supportive of each team's needs. Now as far as the teams that I lead, I make sure that my teams can develop new features very quickly without having to spend a lot of time fixing old bugs that crop up. So my team members have really gotten used to TypeScript and some have learned to love it.
This is the issue that made me enter the conversation in the first place. Why would you decide that they should use TypeScript. It's okay if that's what your team is comfortable with but this will narrow down your options in term of hiring new talented JavaScript developers ( who are not necessarily interested in TypeScript ).
I would never dictate the technology for an entire company.
Of course, I meant is it okay for your company to use both JavaScript and TypeScript for its projects ?
I meant flexibility in term of expanding the team or sharing the code as not all JS developers required to know TS.
Despite that, I'm really interested to know more about TS and what flexibility it gave you ?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You got rid of 500 lines of test but you sacrificed flexibility. What if a new JavaScript developer ( who is not familiar with typescript ) joins your team? or your company should be exclusive for typescript developers?
Keeping JS or migrating to TS it's a decision that has pros and cons on both situations. It's up to you or to your company to decide what suits you the best and what to sacrifice.
Typically, a linter does not enforce you to use a specific syntax neither the ability to transpile. TypeScript is a superset so technically it's a programming language itself.
I mentioned it just to make it clear that my opinion is not biased by hatred toward Microsoft still you confused me with a Microsoft's hater.
Personally, I'm very comfortable with many of Microsoft products, I'm writing this from Win10 and I use VSCode occasionally but this does not mean I'll automatically praise any product Microsoft launch.
Though, I'm super happy with the recent contributions Microsoft has made for the open-source community.
I would be really excited to pair-program with them until they feel comfortable with TypeScript. I'd be really excited to mentor them and to show the value of clearly communicating yourself in code. It's one of the reasons why I'm so passionate about this series I'm writing on TypeScript's emotional/conversational value: dev.to/cubiclebuddha/communicating...
I would never dictate the technology for an entire company. The best companies are polyglot and supportive of each team's needs. Now as far as the teams that I lead, I make sure that my teams can develop new features very quickly without having to spend a lot of time fixing old bugs that crop up. So my team members have really gotten used to TypeScript and some have learned to love it.
This is the issue that made me enter the conversation in the first place. Why would you decide that they should use TypeScript. It's okay if that's what your team is comfortable with but this will narrow down your options in term of hiring new talented JavaScript developers ( who are not necessarily interested in TypeScript ).
Of course, I meant is it okay for your company to use both JavaScript and TypeScript for its projects ?
Yes, a company should be free to have teams that use whatever language that makes them the most productive.
I really can't see how using TS sacrifice flexibility... On the contrary I've gained a lot more...
I meant flexibility in term of expanding the team or sharing the code as not all JS developers required to know TS.
Despite that, I'm really interested to know more about TS and what flexibility it gave you ?