Most companies where I worked have a history of rebuilding their applications every 3 to 5 years, some even 2 years. This has extremely high costs, it has a major impact on how successful the application is, and therefore how successful the company is, besides being extremely frustrating for developers to work with a messy code base, and making them want to leave the company. A serious company, with a long-term vision, cannot afford any of it, not the financial loss, not the time loss, not the reputation loss, not the client loss, not the talent loss.

If we renamed things more often, then it probably wouldn’t be so hard to name them in the first place.

Got a bit sidetracked into refactoring the Element visitor code, so haven't actually started on the event handler stuff per se, but that'll come soon. Element stuff is starting to feel a bit more logical and easier to follow.

It is important to notice that if you are planning on making your application a PWA, you don’t have to rewrite all the logic.

But maybe this PR should still be merged until he finds time for that?

You are not sure which path to take between the big re-write or continuous improvements(using refactoring)