this is the first time I write, cause we usually have a company account without personal informations. However, this time I write because it may be interesting for you guys to.
We are a Hamburg based IT company/ software startup with about 20 developers. A part of our internal tools are build in Xojo, cause a former consultant of us used it to fulfill our contracts. We were never super happy with it. First of all, because no one wanted to go back to the VB days which are gone and what we think is okay. I know, an unpopular opinion here.
While we don’t start new projects in Xojo, we always kept the software which was developed in Xojo maintained. And also, some of us began to like it somehow.
Now we are negotiating with bigger investors to collect a 5M+ funding. We now had three technical due diligence (tdd) and that is story I wanted to tell you.
One tdd-contractor didn’t know Xojo at all, which is not a good sign, since they are extremely experienced and they do hundrets tdds each year all over the globe. They never had a touchpoint with Xojo. The outcome was, that they like the approach, but they made also some research, talked to Xojo-Users here on the forum (I read the chats).
→ In the end they told the potential investor to implement a second CTO here since it looked like we tend to make bad IT decisions. They said, that the licence, the release modell, the small team of Xojo, the closed source, the bugs and the tiny community is a huge risk and we should redevelop all systems which are currently in Xojo asap.
The second Investor made the tdd by them self. As they saw that we have internal tools built in Xojo here, they couldn’t hide a smile (honestly). They told us, that they have a list of technologies, which they don’t want to have in their company-portfilio. Xojo was on that list next to Perl, Elm, AppGuyver, Ninox, B4J and such, Smalltalk, Livecode and Filemaker. Reason was the same: Licencing, lack of support, lack of open source and community and dependence from one small company.
This was the only one, which didn’t told us to instantly rewrite the system, but to plan it’s rewrite within the next 3-5 years.
In every three reports of their technical due diligence, the Xojo system was listed as “technical dept”.
Not because of the language it self or the technology behind. Some of them were even impressed, that Xojo can perform so well in some cases. The reasons were always, that Xojo is to small to be the backbone of companies with the plan to grow to 50+ employees, that the community is to small, that the dependancy is way to high and that the open bugs (I think they get that from the forum here), were to risky.
What do we do now?
We rewrite a working piece of software, because we fear, that it could break our business some day. But not only out of this reason, also because we find no developers using it or even want to use it. And when I search through the forum here, this wouldn’t be the fist case, doesn’t it?
No bad feelings here, Xojo is alright, some of like it very well, but I leave that here, as I think it is interesting for some?