ComponentKit VS Haiku

What about ComponentKit? Just kidding, your tools looks great! Source: 10 months ago

In order to make our engineers' lives easier and gain consistency in our user experience, we needed a declarative abstraction on top of UIKit. We chose UIKit because after experimenting with SwiftUI, Texture, ComponentKit, and other alternatives, UIKit offers us the right combination of features, including:. Source: almost 2 years ago

If you go to osnews.com and do a search for QNX, you will find many articles that were written over the past 20 years that describe the features, and pros and cons of running QNX. I believe there was also an article that compared BeOS (reborn as Haiku OS, haiku-os.org) and QNX. Source: 10 months ago

I assume you know of https://haiku-os.org. Source: about 1 year ago

I am in a similar position. I'm not using the very latest C++ features, but maybe this will be of use to you anyway? I decided to get started writing a native app for Haiku (http://haiku-os.org/), which you have to write in C++. So I loaded it up in a VM and started plugging away. I have always avoided CMake, but it's so popular these days that I decided to give in and get comfortable with it. Haiku is really... - Source: Hacker News / over 1 year ago

{Yes - I know what I'm about to post is NOT "Linux" ...but if you're wanting to learn something new and/or have some nostalgia for the late-90s/early-00s, read on} I absolutely LOVED BeOS back in the day Though I understand why Apple chose to buy NeXT instead of Be in the 90s, I wish they'd bought both - NeXT to get Steve Jobs and NeXT's way of managing apps (where they're all self-contained... - Source: Hacker News / almost 2 years ago

I agree with this. I can also recommend trying out Haiku OS x86 version with UTM emulation (choose between 32-bit or 64-bit OS version), because it requires very little system resources. Haiku is working on an ARM port, but it’s not ready for real-world usage yet. Source: almost 2 years ago