Reflections around the refactoring point raised on the website preview

[salmonb]

The purpose of this discussion is to decide if we should keep, update or remove the refactoring point raided on the website preview.

This discussion is a continuation of this topic started in the first discussion #1

The last idea I proposed in that discussion was a twitter survey about Java refactoring vs JS refactoring, and if Java wins, then a second survey Java refactoring vs TypeScript refactoring. What do you think?

[salmonb]

This article also says that refactoring is better with TypeScript than JavaScript.

You can be confident about your refactoring and that the app will work the same way as it did before refactoring.

Which implicitly states that it's not the case with JavaScript. So you don't need to write tests to check your code is not broken (as Martin Fowler advises for JS refactoring). All these advantages hold for Java vs JS.

To confirm this I raised the idea of the twitter pools.
Is one of you happy to do it?
(I can't do it myself as I'm not active on twitter and have very few followers)