Message from JavaScript discussions

January 2018

— As a great example (I think it's great since webdevs constantly argue over these) is application patterns like MVC... I started just like you not knowing what was best, so I tried MVC and hated it, then moved on to MVP, then MVVM, then Flux. It took me all those tries to figure out what pattern best suited me

Message permanent page

— 

Yeah i think that's the best way to go not knowing which one is best will make me explore them and learn more

— And true it applies to every language its just

— Sometimes become too overwhelming

— I've been there, oh man

— It took me 30 tries to even get MVC right, and hundreds of tries to get Flux right

— You just kind of get muddled in the complexity sometimes

— Yeah i can totally relate to that

— The other way of type restricting and checking is a slowdown of dev, imo. i belive checks are neccessary when you know that the data came from user input

Message permanent page

— It's not meant for user input only

— It's far lower level than UX

— Type safety is the prevention of type errors through the use of standard types