Vue version 2 moving to version 3

I don't intend to get into an argument over it as it serves no purpose. You have a different perspective on Vue - possibly because you use it a lot maybe? But it would be better to perhaps acknowledge that other people's perspective and experience may be different rather than "patently false".

The old library still works. The new one has mostly the same basic features. Nobody is forced to change. And they won't be for the foreseeable future. The new library requires less boilerplate code but fundamentally works the same way as before. Old code still works.

Not really, there are new options, the previous ways still work.

It is indeed but the old stuff still works just fine.

v5 to v6, the only real major change was the jump from node.js v12 to v14 in line with Node-RED itself. This doesn't need new code or changes to flows.

I really don't think you are reading many of my posts if that is what you think. So please don't make unwarranted accusations. Not helpful to anyone. The rapid move of the Vue project from v2 to v3 has annoyed many people, that is demonstrable and searchable fact. It has caused much confusion for people trying to use Vue with uibuilder, also demonstrable fact. I still like and use Vue, also fact. And uibuilder still has more examples - for both v2 and v3 than any other framework. So I absolutely see both the strengths and weaknesses of it as a tool. But the world moves on.

I will continue to explain to people who get caught out by the move why it has happened. I will also explain to people why I've moved away from frameworks and am trying to expand what uibuilder can provide without them. Vue happens to be a useful explanation point as is the evolution of Angular and some other advanced frameworks.

I am a great believer in open standards and open data and this shapes the development of uibuilder. But there is plenty of room for different tools to be added to Node-RED, providing different capabilities for different use-cases and different styles. I will also continue to advocate the best tool for a specific use-case whether that is one I've developed or one that someone else has - just as I have for over 10 years now.