What goes wrong with JavaScript and what can we do about it
When it comes to the client side, indeed, there are some examples of sloppiness even among experienced designers and architects. It's 2016 people, isn't it time to change that?
Having that kind of attitude it is no surprise that a change in the client side of the project affects something else, which affects something else, which affects something else, and so on. Someone on the internet even described web development in general as series of hacks, but does it have to be so?
And if it breaks, that will also break something else, which will break something else, which will again, break something else, and so on and so on... and you find yourself among JavaScript haters. And you wonder how did that happen?
Rigidity, fragility, immobility, lack of maintainability and stability, what are the root causes? And good lord, consequences? Is there anything we can we do about it? I mean, is there anything we can do about except change sloppy clientside attitude? Are there any good practices, or maybe patterns even, that could help us reduce these problems? We will see...
Duration: 25 min
This talk is sponsored by ReversingLabs.
For last five years Vedran has been saying that he has ten years experience in development. Well, that makes it fifteen then. He has been involved into everything from building data warehouses for banking industry, over services for telecommunication industry to hardcore heavy fronted clientside projects. Currently is proudly working as senior developer for reversinglabs.com
