logs-benchmark VS hello

I am a maintainer at SigNoz. Nice to see OpenObserve's belief that the future of Observability should be OpenSource. We chose clickhouse rather than building a database as it takes multi-year effort to move a db to maturity and clickhouse has been battle-tested at Yandex, Uber and Cloudflare. Clickhouse also provides native integration with s3 and other blob storages. Our users have been using disk as hot storage for a week and moving the data to s3 after that. Tiered storage is really cool in terms of query performance.

We have also seen logs data of our users at a compression ratio of 30x/40x. We have published a logs benchmark (https://github.com/SigNoz/logs-benchmark) where the data is very high-cardinal (causing a compression factor of only 2.5x). Would love to see how does OpenObserve perform in that dataset someday.

Wishing you best for the journey ahead.

Did you update the benchmark after you got feedback from this user at Hacker News or after you got the feedback that including Loki here is kinda pointless?

Nitrux, or the FreeBSD derivative "Hello/System"

HelloSystem is an interesting design that is intended to be just the kind of interface you're wanting. The author is critical of modern user interface design and advocates the Macintosh interface. It's interesting stuff to consider. Hellosystem is based on FreeBSD and is not ready for users (and may eventually be a FreeBSD desktop, not a Linux distro).

Are you suggesting they should have chosen Wayland? I think they have a good argument against it:

"Wayland: Under development since a long time, it offers no clear advantage over Xorg while it makes things more complicated (e.g, breaks screen recording) --> Use Xorg instead, or (maybe even better) no X server at all but pure framebuffer (like *ELEC does for media centers). Also see https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d... "

https://github.com/helloSystem/hello/wiki/Welcome-and-unwelc...

> Custom Actions

> It is now possible to arrange custom actions in cascading submenus. Just enter the same submenu name for a custom action in order to place it into the same menu. If you require multiple menu levels, you can achieve that by using '/' in the path of the 'Submenu' entry.*

In 2012 KDE AppMenu Runner was presented as a "plugin which allows to browse, search and select the menubar of the active application".[0]

In 2019 I requested to somehow implement a feature, similar to Blender's "Menu Search"/"Operator Search"[1], into Olive Video Editor.[2]

After it "Action Search" was implemented into Olive Video Editor ('/') shortcut, its code was reused for "Action Search" in Scribus ('Ctrl+/') and then converted into Qt5-plugin.[3,4]

Year later, this Qt5-plugin code reused in for implementing global "Action Search" in helloSystem FreeBSD distribution.[5]

Then "Search and Run a Command" ('/') was added into GIMP.[6]

Guess, GIMP's implementation may be used for other GTK-based apps too (especially Inkscape, which still has no such feature).

[0] https://www.omgubuntu.co.uk/2012/02/appmenu-runner-the-kde-h...

[1] https://github.com/olive-editor/olive/issues/265

[2] https://docs.blender.org/manual/en/latest/interface/controls...

[3] https://github.com/scribusproject/scribus/issues/109

[4] https://github.com/aoloe/scribus-plugin-actionSearch

[5] https://github.com/helloSystem/hello/issues/21

[6] https://gitlab.gnome.org/GNOME/gimp/-/issues/5601