Haiku VS SwiftUI

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

As an iOS engineer, you've likely encountered SwiftUI and UIkit, two popular tools for building iOS user interfaces. SwiftUI is the new cool kid on the block, providing a clean way to build iOS screens, while UIkit is the older and more traditional way to build screens for iOS. SwiftUI uses a declarative style where you describe how the UI should look, similar to Jetpack Compose in Android. UIkit, on the other... - Source: dev.to / 3 months ago

Struct ContentView: View { @State private var text: String = " **SwiftUI** helps you build great-looking apps across all _Apple_ platforms with the power of Swift — and surprisingly little code. You can bring even better experiences to everyone, on any Apple device, using just one set of tools and APIs.[SwiftUI](https://developer.apple.com/xcode/swiftui/)" // declare variable as LocalizeStringKey instead ... - Source: dev.to / 8 months ago

It took me a bunch of iterations to figure out the value prop, but hmm...it's actually pretty good. I can see all the SwiftUI[0] inspiration in how to make compositions, instead of relying on CSS only. Recently there was Rux[1] which is JSX in Rails, but that is really only dealing with ergonomics oh having Components in a nice DSL. Then there is actual deployment story. I recently made a DRF + Next App, and I... - Source: Hacker News / about 1 year ago

SwiftUI is an entirely different way of writing macOS and iOS software. I would start by watching the WWDC videos like this one and reading Apple's documentation. Source: about 1 year ago

I know there’s a bit of technical jargon here, but this is straight from Apple and will explain it better than I can here: https://developer.apple.com/xcode/swiftui/. Source: about 1 year ago