[throwme_123]

Funny to see the main question in the forum is "How stable is it?" and does it crash less than other options.

Haiku is fantastic and seeing it still developed after 20 years is awesome.

But maybe it would benefit from some modern tech. Given the recent discussion on Swift for Ladybird, since huge parts of Haiku are written in C++ it might make sense to gradually introduce Swift to benefit from the language safety features.

[tmikaeld]

"Modern tech" often require significant corporate backing and/or significant amount of funds. I'm amazed that Haiku OS is still going considering it's surviving on donations.

[tialaramex]

> since huge parts of Haiku are written in C++

Sometimes pre-standard C++ and sometimes C++ 98. There's a lot of "C with classes" and stuff that C++ proponents will insist isn't now "really" C++ because that no longer suits their understanding of the language. As is common for that era it has its own custom string type, BString, and so on.

So Swift is about 20 years over their horizon, and modern Swift is even further.

[pjmlp]

Some things never change, regardless of the modern C++ discussions.

Apple, Google and Microsoft "modern C++" frameworks also use their own types, instead of the standard library.

See Android NDK, IO Kit / Driver Kit / Metal bindings, C++/WinRT and WIL.

[KerrAvon]

IOKit dates to circa 1999; it’s not “modern C++” by any reasonable definition.

[pjmlp]

Beyond discussing what Modern C++ actually means, Andrei Alexandrescu book, C++11, C++14, C++17, C++20, C++23, this only goes to show how "modern" is the C++ code from companies that should know better as WG21 members, and C++ compiler vendors.

Let alone those that aren't neither WG21 members, nor C++ compiler vendors.