3 ms·

The ideals of Haiku are great but is anyone using it consistently? If they are what workflows benefit from Haiku's feature set? I understand the theoretical be

by memexy 6y ago

The ideals of Haiku are great but is anyone using it consistently? If they are what workflows benefit from Haiku's feature set? I understand the theoretical benefits. I'm curious if anyone is actually using Haiku features in some non-trivial way, e.g. > Database-like file system (BFS) with support for indexed metadata A filesystem with indexed metadata sounds great but who is actually using it and how? I tried to search for comments with the obvious phrases but all I found was this comment from 10 years ago: https://news.ycombinator.com/item?id=1335692 https://news.ycombinator.com/item?id=1335692.

jessermeyer 6y ago
> A filesystem with indexed metadata sounds great but who is actually using it and how? One of my first sour experiences with NTFS was the horror involved in learning how to find which files have changed since some given time in a directory. I expected a SQL-ish interface but...omg. omg. The reason for tracking changes in files was for hot loading art assets into a running program.
- memexy 6y ago
  Yup, filesystems in general should have a database/SQL interface. I'm currently using CouchDB and Apache Tika to index and search my files. It works but there is no way people who are not programmers would enjoy using such a system. It's extremely inelegant and requires constant context switching and I'd much rather be using an operating system that had all this functionality as part of the filesystem interface.
  - jessermeyer 6y ago
    A visual interface that sorts by type, file size, date time, name, etc, are just intuitive group_by SQL commands.
  - mycall 6y ago
    > Yup, filesystems in general should have a database/SQL interface That's basically what FILESTREAM is in SQL Server if you squint.
extro 6y ago
>The ideals of Haiku are great but is anyone using it consistently? If they are what workflows benefit from Haiku's feature set? I do, but maybe i am not the best everyday example with my ~20 years user experiences with BeOS and Haiku and do development/porting for Haiku. I use on a dedicated Haiku laptop and planing to switch to Haiku on my main system too, the only roadblock is the external-display support. After it gets enabled (i have intel based system) i will switch completely. >I'm curious if anyone is actually using Haiku features in some non-trivial way, e.g. All the files coming from packages have an own attribute which identifies the parent package, so it is extremely easy to find from which package the questioned file comes from. For example. I have to frequently search for existing recipes, i use bash to craft me a search query. I definetely could use `find` instead. I like that i have no email client, so if i need to search for a mail on a busy covered desktop i don't have to hunt for the mail-client icon on the taskbar i just click on the desktop where it visible between all the windows, Alt-F > type what i want > ENTER. I really like the virtual-desktop handling, S&T, etc., so long story short: i like so how it is.

by memexy 6y ago

jessermeyer 6y ago

> A filesystem with indexed metadata sounds great but who is actually using it and how? One of my first sour experiences with NTFS was the horror involved in learning how to find which files have changed since some given time in a directory. I expected a SQL-ish interface but...omg. omg. The reason for tracking changes in files was for hot loading art assets into a running program.

memexy 6y ago
Yup, filesystems in general should have a database/SQL interface. I'm currently using CouchDB and Apache Tika to index and search my files. It works but there is no way people who are not programmers would enjoy using such a system. It's extremely inelegant and requires constant context switching and I'd much rather be using an operating system that had all this functionality as part of the filesystem interface.
- jessermeyer 6y ago
  A visual interface that sorts by type, file size, date time, name, etc, are just intuitive group_by SQL commands.
- mycall 6y ago
  > Yup, filesystems in general should have a database/SQL interface That's basically what FILESTREAM is in SQL Server if you squint.

extro 6y ago

>The ideals of Haiku are great but is anyone using it consistently? If they are what workflows benefit from Haiku's feature set? I do, but maybe i am not the best everyday example with my ~20 years user experiences with BeOS and Haiku and do development/porting for Haiku. I use on a dedicated Haiku laptop and planing to switch to Haiku on my main system too, the only roadblock is the external-display support. After it gets enabled (i have intel based system) i will switch completely. >I'm curious if anyone is actually using Haiku features in some non-trivial way, e.g. All the files coming from packages have an own attribute which identifies the parent package, so it is extremely easy to find from which package the questioned file comes from. For example. I have to frequently search for existing recipes, i use bash to craft me a search query. I definetely could use `find` instead. I like that i have no email client, so if i need to search for a mail on a busy covered desktop i don't have to hunt for the mail-client icon on the taskbar i just click on the desktop where it visible between all the windows, Alt-F > type what i want > ENTER. I really like the virtual-desktop handling, S&T, etc., so long story short: i like so how it is.