I don’t get it.
To summarize:
-
Many customers express their distress after abandoning the web framework and a strong investment in it. Sometimes it is possible to try to migrate to a version 2, but often the cost is too high to switch to a new framework with a very different client side. Sometimes we have developed every day for 10 years on this version to build an advanced app. Imagine that the IDE is developed with the first web framework.
-
After all this concern expressed on the forum by your customers, you publish a blog post to reassure us. In this article, you state that if there are issues that break our applications, such as OS or web browser updates, you will do everything you can to fix the problem.
-
Greg tells us that in the real world, in practice, you probably won’t be able to fix the problem, for the technical reasons he states. At the same time we understand that Geoff’s previous statement was not accompanied by any technical precautions behind it. Apparently, no machines, disk images, or anything else, have been secured to ensure / facilitate possible technical updates. Of course, it is not possible to ensure an LTSC for every old version of Xojo. But here it was still a very important break.
-
Now you say that it was really just a matter of providing answers to questions. But, apparently, if OS or web browser updates break our applications, or for example if security protocols used in the framework become obsolete, it will actually be very difficult to make a technical update to this version of Xojo.
Keep in mind that the blog post you made was not isolated. It was in response to many distressing messages from your customers on the forum. Not messages worrying about not having answers to questions anymore. But messages worrying about the sustainability of our applications. Your blog post has calmed the crowd indeed. And all our reactions that followed in the same threads, in which you and Greg participated, among others, clearly showed that we were reassured about your ability to update this version of Xojo if needed. It’s really surprising that in reading all of these messages, no one in your company has said internally something like “hey, we have a problem here. Customers think we’ll be able to do updates to this version of Xojo if there’s a problem. And, in fact, it will probably be very difficult. It would be a fair thing to warn our customers, even if it’s difficult.”
In short, we’ve gone from a “If something goes wrong, it’s likely that Xojo will come up with a technical solution. Maybe they won’t make it and it will be too difficult, there’s always a risk, but they should be able to do it” to “If a problem happens, Xojo will try to find a solution, a little bit, but they probably won’t make it.”.