Even as someone who has largely developed command line and OS services with GUIs being mostly a utilitarian necessity for internal admin apps, I find Objo incredibly pleasant and useful. Mainly because the language doesn't meaningfully limit you, nor get in your way; in fact, in some ways it's better -- for example, it makes async/await patterns easier to reason about than, say, C#, and is better at mixing sync and async code. It has an excellent profiler and debugger.

It's opinionated in that you basically can only edit code within Studio, but in exchange for that you get your code consistently and clearly organized along with your design notes and docs. It has basic GitHub support included.

Performance is very respectable, even impressive at times. Certainly adequate to its intended use cases. And a rich ABI is planned for calling C and .NET libraries, for the times you need the extra oomph.

I think Garry's architectural instincts are very good, and it's reflected in the product.

Perhaps the most pleasant part of testing this product has been Garry's incredible responsiveness and transparency; it's refreshing after years of dealing with large corporate-sponsored product development. I like the trend where more and more products of this type are being produced by smaller, leaner teams with a vision and passion for what they are doing.

undefined