4 ms·

I enjoy the BeAPI. In my opinion, the Interface Kit (GUI) has just the right balance between having enough features to be useful and not getting in your way. T

I enjoy the BeAPI. In my opinion, the Interface Kit (GUI) has just the right balance between having enough features to be useful and not getting in your way. The BMediaKit realistically has 2 purposes, decoding/encoding and streaming and ideally should be split up into 2 kits. The Haiku based packaging system is really great for developers, since installing headers/libs requires zero effort, it just works. Tracker (file navigation) is fantastic, finding header files takes less than a second. Deskbar needs to apply 20 years of modernisation and adopt features from other OS's. The browser situation is terrible, though. System administration is really well thought out, however, it needs user accounts and encrypted volumes. Regarding other development environments, I've done professional Qt development, and I'm displeased with the ownership and kitchen sink model. Ownership and auto layout make dynamic widget hiding a real pain, especially since you cannot remove a widget (ownership issues). Layouts with dynamic widgets are another pain point.

AnIdiotOnTheNet 5y ago
> it needs user accounts Why? It's a desktop OS. The use case has a median user count of 1.
- deleted 5y ago
  [deleted]
- rdpintqogeogsaa 5y ago
  A family PC has more than one user. I'm sure that the same people don't want to, say, share their browsing history and log-ins or have the same taste in wallpapers.
  - selfhoster11 5y ago
    You could do an n-way multi-boot, with an instance of the OS for each person. It's definitely small enough to support that.
  - AnIdiotOnTheNet 5y ago
    > A family PC has more than one user. Do these really still exist[0]? As far as I can tell, they only ever existed during the window between when internet access became ubiquitous and when smartphones became ubiquitous and laptops got really cheap. Besides which, I think there are better ways to accomplish that goal without user accounts. User accounts exist to protect the system and users from other users in a shared system or network, which doesn't really apply in a Desktop use case. Instead I would say what you want is switchable user profiles, plus encryption to actually protect your documents if that's important to you, because it is trivial to bypass filesystem permissions for local users anyway. [0] I'm sure somebody is doing it, but I have to imagine that within the vanishingly small Desktop PC market this use case is itself vanishingly small.

AnIdiotOnTheNet 5y ago

> it needs user accounts Why? It's a desktop OS. The use case has a median user count of 1.

deleted 5y ago
[deleted]
rdpintqogeogsaa 5y ago
A family PC has more than one user. I'm sure that the same people don't want to, say, share their browsing history and log-ins or have the same taste in wallpapers.
- selfhoster11 5y ago
  You could do an n-way multi-boot, with an instance of the OS for each person. It's definitely small enough to support that.
- AnIdiotOnTheNet 5y ago
  > A family PC has more than one user. Do these really still exist[0]? As far as I can tell, they only ever existed during the window between when internet access became ubiquitous and when smartphones became ubiquitous and laptops got really cheap. Besides which, I think there are better ways to accomplish that goal without user accounts. User accounts exist to protect the system and users from other users in a shared system or network, which doesn't really apply in a Desktop use case. Instead I would say what you want is switchable user profiles, plus encryption to actually protect your documents if that's important to you, because it is trivial to bypass filesystem permissions for local users anyway. [0] I'm sure somebody is doing it, but I have to imagine that within the vanishingly small Desktop PC market this use case is itself vanishingly small.