The frontend community shifted from simple websites with jQuery to complex Single Page Applications with Angular, React and so on. With this community getting bigger and "older" there's another kind of problems that we need to solve: how to manage Legacy frontend codebases. But when can we call a frontend codebase “legacy” and how can we manage it in a safe way? During the talk, we are going to see how we applied the StranglerApplication pattern to change an AngularJS 1.2 Application into a shiny new codebase that our team really loves.


Comments are closed.

Matteo Ronchi at 11:40 on 10 May 2018

Great talk presenting a topic outside tipical js arguments. I really enjoyed it.

Nice talk, well structured between theory and code.
I did not have a 5, because It’s a shame you did not explain why you think framework less solution is a better solution for the future (the question you had at the end), I’m not convinced so I would love to hear your advice on this :)

Leo gullotta at 14:16 on 10 May 2018

good but the actual technical content wasn't much

Interesting, but not exactly novel. Could be useful to know what happens if code isn't changed for a long time (and thus never strangled)

Stefano at 21:56 on 10 May 2018

Good talk, better ideas to how incorporate old legacy application into new one. But maybe the frameworkless reasons could be better explained, perhaps with a comparison of performance.

Luca Fabbri at 18:32 on 11 May 2018

Brilliant talk, one of the best in the whole conference schedule.
I liked the story behind and the reason why the team chosed the "Vanilla way", I found amazing the way they broken the legacy software from inside, one peace at time.
Francesco warned us all about the future of building software that we don't want to became legacy. Wow.