Yes. This is another Windows thread (TIAWT).
First off, our product is 100% Windows based and my Xojo experience on the Mac is limited to other projects that I work on, but the product that we sell and based our business off is Windows, so with that in mind.
The purpose of this thread, without question, is to bring to light that there needs to be more work on the Windows support.
I’m at the point now of having to decide to continue with Xojo or (God forbid) move to C# / .NET / WPF. And its becoming a harder sell to stick to Xojo.
So I’ll elaborate.
I realize that if we’re a 100% Windows shop, that we’re probably in the minority here.
And some would argue that we probably should use the native too set on the platform we’re generating revenue from – but we chose Xojo because of the fact that we wanted to avoid the distribution issues, cost and complexity of the Microsoft tools – which if people have been using them understand exactly what I’m talking about. Xojo provided (5 years ago), a very comparable development tool to VB 6.0, if not a better product that allowed you to build very much the same types of applications that you could with VB.
But here we are almost in 2014, and times have changed.
I look at the current apps for Windows and its clear that the apps we’re doing with Xojo (on Windows) are far from being “professional” looking, they run
slow – they flicker (yeah, yeah) and they have a far more “older” feel to them than their Mac counter parts which went through years of Cocoa development
to get them up to the point where they are following along with the path that Apple has set forth.
Windows in my opinion is now behind the curve, and its falling further behind with each new release of Windows. So much so now that its becoming a bit embarrassing trying to develop an app that “looks” like it should run on the current Windows 7 and 8 platforms.
When XP was the standard, you could get away with producing apps on Windows – they fit into that look and feel. Today? Not the case.
Xojo is lacking in performance on Windows
The Window’s side UI performs poorly, with lots of flicker (which is well documented here) and a very slow painting of objects on the screen compared to the native apps created in Visual Studio using XAML (I.e. DirectX).
Database performance is weak. If I do a SQL query in Xojo using OleObjects with ADO, its 50 and sometimes 70 times slower in my testing with the same query using C# and OleDb objects. That’s unacceptable.
Not having 64 bit executables also hinders performance for applications As most Windows business application deployment is now 64 bit, Xojo has to reside in a 32 bit “box”.
Xojo on Windows lacks extendability
Not being able to call a .NET DLL is hindering the ability for Xojo to be expanded to solve many of the issues or extend functionality – older “C” style DLL’s are no longer the norm on Windows and this is presenting problems with being able to create applications that are for recent versions of Windows.
Xojo apps lack the standard Windows controls and look and feel
Looking at apps on Windows 7 and 8… its not hard to see how Xojo apps stand out like a sore thumb. Further, not supporting the basic objects on Windows is becoming an issue. Why should I need to buy a grid control to “mimic” a component on Windows thats standard for Visual Studio applications. In fact, on Windows, Xojo should follow ALL the available Windows controls that are available to WPF / C# developers – and this includes allowing for the use of XAML.
The Xojo IDE looks like a Mac application
The Xojo IDE just doesn’t look or behave like a Windows application on Windows. I’m not saying “make Xojo look like Visual Studio”, but what I am saying is that the GUI has no resemblance of a Windows development tool and looks like Xcode on Windows.
Embrace MS API’s and technologies
Just like Xojo has embraced Cocoa, there should be an effort to do the same on Windows.
Not supporting simple things like ADO OleDb within the language and have it perform on par with its Window counterpart is really disappointing. When we have an ODBC plug-in, but given that most data access now is through OleDb objects, to see Xojo requires the use of OleObject – which is complied into the language and very slow – is really hindering Xojo.
I could go on here, I’ve listed some things… and I’m sure there’s things I’m forgetting!
I realize there’s only so much you can do. I fully support the efforts on the Mac and iOS as well, and even think the WE technology is interesting. But I think we get all that stuff at the expensive of Windows. Windows is really falling behind and this is going to be a problem for me as I decide to upgrade and move forward with Xojo.
I’d really love to hear that there’s at least a single developer dedicated to improving Windows. Someone dedicated to solely making the Windows side of the product better – that would give me some confidence.