I get it is not related, but, what are some of the things people do with Haiku? You can browse the web, what else? What other languages are supported, is there Haiku Ruby?
Porting Swift to Haiku
31–40 of 53 posts
Re: Porting Swift to Haiku
#32I get it is not related, but, what are some of the things people do with Haiku? You can browse the web, what else? What other languages are supported, is there Haiku Ruby?
> You can browse the web, what else?
There's a decent office suite, Vim, IRC client, etc
> What other languages are supported, is there Haiku Ruby?
The usual complement of scripting languages (Ruby, Python, Perl, Lua), any JVM language, Go, partially working ports of Haskell and Mercury, Rust (no Cargo port yet), probably some others.
Re: Porting Swift to Haiku
#33The Haiku OS Could use a modern language Port Swift to Haiku
To be fair, it does have Rust (but no Cargo port yet).
And Go, if that counts as a “modern” language.
Re: Porting Swift to Haiku
#34I just feel like this project has lost track of priorities, or doesn't want to be a credible alternative OS anymore. As a long time fan of the project - who cares about Swift? Where's the next release?
>> I just feel like this project has lost track of priorities
I've been following the development of Haiku (OpenBeOS) on and off since BeOS got discontinued -- for something like 16 years now.
While the effort and progress of the Haiku team is commendable, 16 years is a long time to produce an OS, so one might argue that they never had a good grasp of their priorities in the first place.
In the 16 years since OpenBeOS was announced, the world has changed drastically.
I remember running BeOS on a Pentium II, and it was amazing... at the time. It did some stuff that Windows and MacOS couldn't easily do performance-wise, because of its time slicing.
I remember simultaneously playing back four or five videos on BeOS at the same time without any hiccups, and you could barely do that with two videos on Windows on the same hardware. Because modern processors are so powerful, even on phones, most of the benefits I wanted out of OpenBeOS (Haiku) around 2000 no longer have value today.
I still follow Haiku's progress because of some BeOS sentimentality, but to me, it's now a novelty more than anything.
Re: Porting Swift to Haiku
#35This is gonna ba dank.
Also first time seeing Haiku mentioned here.
Re: Porting Swift to Haiku
#36I am really sad this isn't about writing swift as a haiku.
Metapoem.
Re: Porting Swift to Haiku
#37I don't think swift is enough mature language for this..
Yes, because Haiku is used in business critical applications...
TuneTracker, the radio broadcasting system from the BeOS days, uses Haiku now: http://tunetrackersystems.com/ -- so that's one "business critical" application, at least.
Re: Porting Swift to Haiku
#38I wonder what the plan is for getting swift interop with C++, given that all the Be/Haiku APIs are C++ (IIRC) and swift has no ability to call into C++ code directly.
Haiku is POSIX compatible, so at the very least there are the standard C APIs. It is true you need to call into C++ for things like GUIs though (unless you use a port of a C GUI library).
Re: Porting Swift to Haiku
#39I just feel like this project has lost track of priorities, or doesn't want to be a credible alternative OS anymore. As a long time fan of the project - who cares about Swift? Where's the next release?
>> I just feel like this project has lost track of priorities I've been following the development of Haiku (OpenBeOS) on and off since BeOS got discontinued -- for something like 16 years now. While the effort and progress of the Haiku team is commendable, 16 years is a long time to produce an OS, so one might argue that they never had a good grasp of their priorities in the first place. In the 16 years since OpenBeO…
It's kind of off-topic for this thread, but I think there are quite a number of arguments to be made for Haiku's continuing relevancy (although I'm clearly biased :). You're right of course about performance being much less of a big deal these days (Haiku still far outshines even Linux in efficiency, though not in raw speed, mostly due to our lack of GPU acceleration).
Instead, the relevancy now mostly has to do with the unity -- or rather the lack thereof -- amongst NIX operating systems. While Linux dominates the server market, the "year of the Linux desktop" that everyone's been hoping will arrive for at least a decade now hasn't arrived. Sure, there are new challengers now and again but most of the problems and criticisms of Linux aren't about the look and feel, but usually fall on a more fundamental level: "Stuff breaks and then it's impossible to fix." -- "My audio drivers don't work and this tutorial to troubleshoot it is incomprehensible to me." -- "I took some updates and now Kdenlive doesn't export audio anymore."
Haiku is very different in this respect because its underlying architecture is the one thing Linux/BSDs are not and never will be: unified. The entire system, kernel to HTTP client to file manager, is developed by one team on one infrastructure inside one git repository. Which means as a result, you always know whose fault it is when something breaks (ours), and that when we fix it, it'll appear in the "nightly" update channel by the next day. It also means that there's no long series of configuration changes to try when something doesn't work; almost universally, stuff either works or it doesn't. Really -- there's only one exception to this I can think of (relating to a bug in our port of FreeBSD's Intel WiFi drivers.)
Linux has been trying for a more unified system both up front (e.g. elementaryOS) and in back (systemd...), but the more I use it, the less I want to use it and the more I want to use Haiku.
Re: Porting Swift to Haiku
#40I am really sad this isn't about writing swift as a haiku.
That will be in Swift 5!