IntelliJ IDEA and PyCharm Running on Haiku(discuss.haiku-os.org) |
IntelliJ IDEA and PyCharm Running on Haiku(discuss.haiku-os.org) |
The beauty of each desktop centric OS is the whole platform, the set of SDK languages, the respective frameworks for exposing the OS and hardware features that make the desktop experience unique, and IDE developer experience.
If it is to run desktop agnostic apps, then anything can do.
I ended up reading the Wikipedia page on BeOS for some nostalgia and it mentioned Haiku. Glad to see BeOS still around in some form — definitely was ahead of its time!
It blew my mind. Things we take for granted now like multiple QuickTimes running at the same time, all the massive concurrency... Live searches of the filesystem via journaling... All way before its time (or at least, way before it appeared in mainstream OS'es).
What I wonder is, is Haiku more efficient than other available OS'es at Intel (or other, like ARM) CPU utilization?
Great stuff. We need an open-source operating system 100% focused on the desktop.
It seems like a very performant and simple OS (which is a welcome alternative compared to macOS) but these are pretty glaring problems for a user starting out. For a project that's been around for over a decade, that's a little bit of a red flag.
Also dunno why WebPositive wouldn't do anything for you. It's still a little buggy, but it usually works well enough for my purposes...
We need something that even senior citizens can use to replace Windows XP on a system they can't afford to upgrade. Just the basic word processing Internet surfing and email.
ReactOS is progressing as well.
OSFree the OS/2 rewrite seems slower but using the M4 kernel with DOS and OS/2 personalities.
[0] https://depot.haiku-os.org/#!/pkg/python3/haikuports/3/6/7/-...
I didn't know about Haiku up to 2013 I guess where I had a bug report for my download manager https://github.com/Alir3z4/yoDownet
It's a really interesting OS
Linux is getting good at drivers and "just works", but it still isn't there. I fear how hard it will be to get haiku running
It Just Works and contrary to certain other IDEs it uses Mavens pom file directly instead of translating it to some other (even hehe) less ideal format.
(Recently though Visual Studio Code has been a so big part of my developer life because of Dot Net Core, and Netbeans was so late and unclear about their 9.0 release that I tested just using VS Code for Java as well. It worked reasonably well. But now that Netbeans 10 is released I'd probably go right back if/when I go back to Java.)
My personal experience from large scale transition from Windows 7 to Linux Mint at work indicates that people ABSOLUTELY can use Linux - the UI is (unlike Win10) stable and things do not move around, settings don't change themselves on upgrades. And, importantly, updates can be set to be silent and automatic.
I am probably one of the biggest naysayers of Linux as a desktop platform, so keep that in mind when I ask: What's wrong with Linux for this use case?
If all you need is an internet kiosk, Linux is fine. In fact, I'd go so far as to say that's been the Linux Desktop's targeted use case for about a decade now because their cultural attitude is that anyone who isn't a C greybeard needs to be bottle fed.
My other grandmother has been on Chome OS for almost as long. Which has been another great option. I do wish that Google had better support for installing/running full Chrome OS on more generic hardware. I find it's just about the best option all around for the novice computer user.
The way I see it, it is nostalgia. Which has its value. For ReactOS, it also provides backwards compatibility and essentially is a FOSS and free as in beer Windows implementation. However, there are also progressive OSes such as Nix, Tails, Qubes to name 3, or microkernel-based OSes. These are where the innovation lies.
They have something that boots, but I am not sure if it can run OS/2, DOS, Windows code yet.
I wanted to donate $5 but their donate button is broken.
I’m more than happy if the former two are done and dusted and my experience with BeOS and since on the former two has been pretty good. If something is pretty but not functional, people won’t use it. If something is functional but not pretty, it’ll get used nevertheless.
People might say it’s a false dichotomy but GNOME 3 and early Windows 8 are substantial examples of the opposite.
Windows 95 wasn’t pretty in any traditional aesthetic sense but by god was it ever functional and cohesive and successful despite basic bitmap faux-3D. Nobody cared.
But I do think you're right in that if BeOS had survived, it would not look like that in 2019. It's probably time for Haiku to start evolving the UI/UX to keep current as the spiritual successor of BeOS.
The style is part of its appeal.
I think if they could get patches upstream for chrome and node, which would allow electron, that could open the doors for a significant increase in usable end user applications. The article's demonstration on progress for Java applications is very impressive on its' own.
Aside: being able to use user tweaked UI/UX would be nice in general, but would probably be a break from the BeOS origins. I used to run a shell replacement on Win2k and XP era, but I liked win7 so much I stopped using it (don't even recall the name right now).
In the end, there's no cause for rudeness here. While I don't think I'd be able to use Haiku currently, it's nice to see progress here. I'd also be interested to see a window manager for linux that followed the Be/Haiku aesthetics as I think a lot of people would appreciate it. Personally I really like the dock/taskbar in Win7 and 10, though I prefer the Win7 start menu. I run mac, windows and linux regularly (mac and windows daily, linux at least once a week on elementary).
If Haiku was a Linux Window Manager, I would use it in a heartbeat.
It's a bit of a stretch, but you could argue the comment goes against this guideline:
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
Nit picking comment aside, I wonder if the fact that it is single-user was one of the reasons Apple did not go with it.
At any rate, we'd love to at least have your patchset in HaikuPorts, even if it's not quite ready for prime-time yet.
However if mmap is more significantly broken then Haiku needs work - Wine does need the ability to map things into the address space at the requested locations and actually get it.
mmap on a fixed address should work just fine, unless the address is outside the normal range or in an already mapped region, which seems to be a problem on 32-bit systems. I think there are some emulators we have ports of which already use MAP_FIXED quite a bit.
Would like to try my hand at building something like that myself, but X on top of being phased out is a strange beast to learn and there’s practically no material on writing something for Wayland.
I've been working on and off implementing some Platinum stuff in Pharo's upcoming new graphics layer (called Bloc) and these have come out OK. That's where I'd really like to use it -- my whole desktop can be like Hypercard
You should look up the work of Sir_Cmpwn (aka Drew DeVault), specifically the wlroots project and his excellent writeup: https://drewdevault.com/2018/07/29/Wayland-shells.html
Unix had it different with there being no core experience in the first place -- X11 being a glorified terminal multiplexer plus xeyes. Whether it was the commercial Unices with OpenLook/NeWS vs Motif/CDE or later Linux with Qt vs Gtk. Not that there wasn't a chance -- at one time Motif won over the commercial sector and if it would've been available with the same license as Xlib/Xt, GTK would've never been developed.
But that seems to be a thing of the past. These days the web forced us to give up all platform-specific UI expectations -- heck, any expectations of having a proper UI in the first place. And thus applications are all over the place, Electron being just one particularly heinous culprit. Material UI on the desktop. Plenty of applications starting up web-based interfaces in the browser.
On the one hand, as you say, this doesn't make the particular desktop matter anymore, it's more a vehicle of getting your wifi driver to work properly and load the browser. So one could use Linux or even Haiku without any big losses. On the other hand, if everything's pastel-colored oatmeal, there's no big benefit from a neat, unified, C++ desktop experience that BeOS was aiming for.
If you want a vision of the future, imagine HTML stomping on your face -- forever.
I don't need such vision, it is how it would look like if all OSes happen to jungle browser instances, ChromeOS style, while a big chunk of applications runs on someone else's computer, abstracted via language runtimes.
The return to mainframe's timesharing days and very sad outcome for desktop computers, with the minimum experience common to all vendors.
Graphical APIs not able to take advantage of hardware, hardware support that takes years to have minimal APIs, drawing UIs pilling divs customized with CSS and JS to mimic visual behaviours.
The reason apps all went cross platform is that desktop operating systems stopped innovating. Which is the desktop platform with the most new native apps, where developers take pride in making non-cross platform experiences? MacOS for sure. Which desktop OS has been consistently the most innovative over the past 20 years? MacOS!
Haiku running IntelliJ is technically interesting, but ultimately as a user I don't understand why I'd want to use Haiku. BeOS may have been innovative 20 years ago but it's a dead OS that hasn't changed in decades. May as well run IntelliJ on any other platform, then.
I think the desktop can be great again, but it will take a new generation of developers with new ideas about where to take operating system technology. I also tend to think that whoever tackles that problem will probably tackle it by writing a cross-platform app runtime that slowly expands to become more and more of an operating system until the actual OS is indeed, just relegated to providing some drivers and bootstrap code. But the actual UX will be defined entirely by that environment. Sort of like how Pharo gives you a full blown desktop environment when you start it (but I'm not arguing for Smalltalk)..
I agree. In my opinion though, Haiku's insistence on becoming just another platform to run your UNIX software stack on means it will probably never succeed at that goal.
Anyway, I think you miss the point of Haiku if you think it'll never get anywhere because of how much UNIX software runs on it. It's not here just to "be different from everyone else." The POSIX API makes a lot of sense; anyone going against it has to have a particularly good reason to do so. Even Apple doesn't, for the most part.
So Mac OS X inherited one userbase that appreciated platform-specific software. Haiku doesn't really have anything to inherit like that so until people start making Haiku-specific software, that could be an issue for seeing great Haiku software rather than just ports.
For a while, the OS X app space was rather "pure". A minimalistic aesthethic, plenty of small opnionated productivity applications. Apple itself didn't wreck or disrupt it too much (looking at you, MS Office).
Then mobile happened.