To-Do-List Example:
SIzes Binaries (not compressed, put into a DMG-Image or Install-Program), just pure compiler Output:
For me (main system is GNU/Llinux) it is very comfortable to serve all major platforms (win, mac, linux).
For crying out loud!!! I was just curious!!! Excuse me for asking a simple question!!!
Youāre allowed to ask questions. Others are allowed to answer them. Some, like Garry, will just answer it; others will feel the need to assume things about your motivations. But I seriously doubt that any of itās personal, and even if it is, that would be their problem rather than yours.
My responses were just about discussing the points raised, not an attempt at a pile-on. I meant no offense.
No nothing is personal. I had to read to often about the best and ever basic compilers with so small footprint. I am not intrested in this cause this is not a modern approach for programming. Youwanna small cli? Use C or Rust. No rintime no nothing. A few kilobytes. You wanna get UI program? Use the right tools for it. Security is one of the points. We are cyber security save with our applications. All are laboratory approved cyber secure. Once a year. Sometimes a regulated market is a regulated market. Everybody shall do what he wants.
Perhaps @TomasJ nicee, good Job.
Yeah I know you had that in mind and that was your frustration. However I think @pjsmith isnāt looking for a microscopic exe, he is selling a DB server built with Xojo after all. He really was just curious. It is a low priority curiosity for me too, although it wasnāt an input into my decision to buy an Objo license, for the reasons you mentioned.
I can understand. The opinion behind is testing first. Rest comes later. I guess. I hope that this product will replace this entire Idea behind X..o and replace the product. Why? While it is more capable of writing software. It is a clean and really good structure. Makes it nice to use.
None taken. I had no issues with your respsone. Tnanks though!
Well it is not a drop in replacement. Some of that is because itās early days (smaller type system, some features still being built) but some of it is inherent ā the language is somewhat different, the approach to multi-platform GUI is different, the code neednāt be peppered with platform conditionals, there is no API 1.0 vs 2.0, etc.
This is necessary not only to avoid enshrining poor design just for the sake of compatibility, but also, because Iām sure Xojo would sue someone making an actual clone, to slow them down and drain their resources if nothing else. Trump sets the example here, lol.
So the word āreplacementā is doing a lot of heavy lifting here. I abandoned Xojo maybe 3 years ago after a brief flirtation. For my immediate needs, I went to WinForms since I didnāt need cross platform ā and via ThinFinity or WiseJ.NET I still could deploy those to the web if needed someday. If Objo were more mature and especially if it has a web target, I would maybe use it instead of WinForms in a perfect world but thereās no business case for rewriting or using 2 platforms. What I have does the job for the client.
So I would use Objo for future projects that I might have used Xojo for if it had lived up to its promise (for now, also assuming I donāt expect phone or web targets would be needed), but they would be greenfield projects. The only sense in which itās a Xojo āreplacementā is that they are targeting a similar audience ā people looking to basically develop for a virtual platform and abstract away literally all the details of deploying / running on the different targets. Sure they can leverage their knowledge of Xojoās generally similar basic dialect and develop in a similar IDE but they canāt open a Xojo project in Objo and just keep going, nor would that ever be possible down the road. The closest you could come would be a code converter producing an Objo solution from a Xojo solution and then follow up on a significant list of things needing developer attention and testing. Not unlike the transition from VB6 to VB.NET must have been (fortunately I never had to convert between those).
True, no question. But for me it was the other way around. I had to use it for one project and was never even liking it. Came from Java / JavaFX and Vaadin and wrote many Android Apps in Codenameone for different purposes but mostly business purposes. So I never had the need of XoJo as I even didnāt came from VB6 like many others. My first language was TurboPascal, later C and when Java came up I changed to Java while it runs on all platforms. As I have CN1 I can also write in Java for iOS and Android. So for me I have a toolchain which covers 90% of my needs. Sometimes I need also a few stuffs native. Thatās always done with C++ and QT so I can work cross platform with native UI components ot letās say more near to native than XoJo ever was.
I cut my teeth on early compiled BASICs (and some Z-80 assembler) in the 8 bit world and then took a lengthy detour into xBase dialects (mostly Foxbase / FoxPro) before the Microsoft / Fox āmergerā murdered that platform, then straight to .NET 1.0 and its successors. I was responsible for many years for a code base that had been started in VB.NET by someone else, but I never really did any work to speak of in VB6.
So I have a soft spot for Basic and the ethos surrounding it but have been pure C# for years now, professionally.
What attracted me to Xojo was the hype that it was mutli-platform including web from substantially a single codebase, and I never really enjoyed web development with its ad hoc shotgun wedding of various technologies. Somehow I have made a good living as a back end guy, and mostly avoided web development, although I had a substantial side gig maintaining a hoary old web app for the mortgage industry, and a couple of others like that over the years.
Xojo held promise for abstracting away platform differences and letting me focus on business logic and UI. It did not, of course, deliver. Objo seems like it might succeed (in part by simply not being buggy and having a nimble developer who is actually responsive to users; in part by having better architecture and making smarter choices in what to built upon, not suffering from ānot invented hereā syndrome, etc).
Given my age it is likely I will never use Objo in my consultancy, but I can imagine spending some enjoyable hours using it to build fun things in my retirement (if I ever get around to retirement).
Sounds like a man who knows what heās speaking about.The single codebase for all platforms was what attracted me in the java world. In the later 90th Java became also capable of web development and this development continued. In 2000 I was totally happy when Vaadin came up and in 2002 it became open sourced. For me that was so simple to work while I had immediately the chance to use my code for all platforms. In 2012 Codenameone came up for Android and iOS what attracted me from the same reason: sing my code on all platforms with a maximum of usability.
The best for me was: when you know Java Swing entering Vaadin isnāt that hard and also the structure of the Codenameone code concept is close to Java Swing. So it became my toolchain. While I have also electronic development I had always also the GUI Software with Java and the firmware written in C and today mostly Rust, What ever: this is my way of programming and serving applications for Windows, Linux, macOS, the Web and mobile (iOS and Android).
I can understand the attration of XoJo cause XoJo is less complex than building Java applications, no question. But for me the biggest argument for Java is still this extreme big ecosystem around Java. And for me stuffs are simple.
What was important for me (and at the end was not letting me understand this API1 and API2 Ideaas of XoJo) was and still is: reliability of Code. Even really old AWT applications written in 95 can still be compiled. yes, a few libs I have to change and a few new technologies I have to implement. But I habe a maintainable codebase in the age of 30 years which is still maintainable and foreseeable in ten years maintainable.
And yes, one thing is still annoying me: it is never native GUI. It really looks like it (FlatLaf for Java Swing for example and I can use file choosers, dialogs and other stuffs native so they come up native. But the rest isnāt. The other side for me is: I can write exactly one documentation and I do not have to write one for Windows, one for macOS and one for Linux.
So yes, this is my world and my toolchain I can use. Reliable and foreseeable for the next decade available.
Shortly after Objo Studio was announced I bought a license. Iām very impressed on how well build and easy to use Objo is. Itās already very useful on creating apps.
At the moment Iām trying to get the framework, that Joost Rongen (sadly, he passed away in 2024) and I have created in the past, working in Objo Studio. It is a lot of work and slowly but surely Iām getting there.
My main problem at the moment is that itās not possible to add files to the resources folder, like the CopyFiles in Xojo. I need to add a couple of readonly databases to the resources folder. Having the ability to copy files to the resources folder would be a big game changer for me.
Garry is doing a fantastic job with Objo Studio. Keep up the good work Garry! 
Iāve added a feature request for this: Feature #339 - Objo
Hi Garry,
I also mentioned this before on the Objo forum ( How copy files to resources folder of app. - Objo Studio Community ) and you already made a feature request for this Feature #278 - Add generic projectresources copied into app bundles.
Ah youāre correct. Itās a duplicate. Have merged into #278. Thanks.