I see PropTypes increasingly replaced by static type checking, be it Flow or TypeScript. The advantage is that you don't have the overhead and warnings on live and still have the full type checking (and even more versatile one) in development.
What's your opinion on static vs. dynamic type checking?
Software dev at Netflix | DC techie | Conference speaker | egghead Instructor | TC39 Educators Committee | Girls Who Code Facilitator | Board game geek | @laurieontech on twitter
I'm a big fan of static type checking! But writing something in Typescript isn't as simple as writing JS and adding types; at least not if you want to follow best practices. So dynamic type checking is a nice middle ground. Giving you some of those features without changing what you know.
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.
A fun way to look at PropTypes :) Nicely written.
I see PropTypes increasingly replaced by static type checking, be it Flow or TypeScript. The advantage is that you don't have the overhead and warnings on live and still have the full type checking (and even more versatile one) in development.
What's your opinion on static vs. dynamic type checking?
I'm a big fan of static type checking! But writing something in Typescript isn't as simple as writing JS and adding types; at least not if you want to follow best practices. So dynamic type checking is a nice middle ground. Giving you some of those features without changing what you know.