Objo Studio's niche is the ability to target MacOS, Windows and Linux from a single code base, with other targets (including web) on the roadmap. It's built on top of .NET and Avalonia, with its own custom VM running compiled bytecode. Performance is very good, and also on the roadmap is interop with .NET languages and C, so performance critical bits can be handled. I also expect a vibrant ecosystem of add-on libraries and tools will develop -- the tires are already being kicked by vendors.
I can only describe the feel of this product as lovingly built by a real craftsman and competent architect who is incredibly responsive to both bug reports and feature suggestions. That is paramount to me. In fact that responsiveness and pride of workmanship in today's world of products diluted and enshittified by soulless corporations, is actually inspiring. It has already earned a core of enthusiastic developers.
And the price is right: free until you want to compile distributable executables (or use the premium Profiler).
The language will be comfortable to anyone who has developed in C# or VB.NET (or Xojo, a commercial product formerly known as RealBasic, which Objo (the language) is broadly compatible with, while not being enslaved to Xojo's sometimes idiosyncratic architecture).
Nothing important is lacking in the language: async / await, closures, reflection (which Objo refers to as introspection), generics, etc. The main weakness from my point of view is the small type system (64 bit integer, floating point and decimal types; strings, DateTime, boolean -- although there is no problem building classes, modules, enumerations, etc. of arbitrary complexity). I particularly miss a dedicated char type, although there's a comprehensive API for converting strings to and from code points in the form of integer arrays. There is also a MemoryBlock type, which is essentially a fixed size byte array, with robust support for reading and writing binary data between MemoryBlocks, disk files and more.
While some might be tempted to see Objo as a beginner's language, it is in no way limiting in that regard. In fact a self-described beginning programmer requested a fairly advanced feature recently (conditional compilation) and the vendor response was typical: "implemented for the next release". As for pros -- I requested a profilng tool and that was "in the next release" as well.
The debugger is excellent and includes the ability to trigger breakpoints based on expressions, as well as remote debugging.
Beginners and long time professionals like myself will all be quickly spoiled by this product. I have been slinging C# code for 20 years and other languages for two decades before that, and I do not feel deprived by Objo the language.
There are of course things I don't love. Objo Studio has an opinionated approach to building class definitions and filling them out with code. Everything is form-based; you don't write a class definition in a file organized as you wish, you use Studio's UI (forms, tree controls, etc) to navigate around your project. However, it is well constructed and stable, so it grows on you, and the solution / project formats are open, documented, and Git-friendly. I expect 3rd parties to make more traditional drafting of code a reality down the line, for those who want it on occasion.
I find the solution / project metaphor in Objo Studio to be ... different. It is in a sense the inverse of Visual Studio or Ryder: a solution contains your library code, off of which hang your projects, which are the apps you're building. Since you quickly accumulate general purpose components that you would use in all your apps, you end up with one solution and many projects under it. As it currently stands, I can't think of a use case for multiple solutions as you would have to resort to copy-paste to get your support libraries in all of them. I expect however that this will change when interop and 3rd party support arrives, such that you can buy a library and import it into any Solution -- and build your own importable libs in the same way. So I regard this as an "early days" issue and not a practical long term problem.
So far, I have been focusing on language and performance matters, but folks who are already building complex GUI apps have no complaints here, even when porting complex existing apps from other platforms.
In summary: if you are looking for a cross platform development tool that lets you focus on implementing your GUI and business logic while capably managing the platform differences -- or if you just want a pleasant environment to work on your idea for a great product -- I can confidently commend Objo Studio to you.