53 karma · joined August 24, 2022
The general philosophy of Guix is to have a single definition for how to build your software and use it for the entire dev to production pipeline.
[1]: https://guix.gnu.org/manual/1.5.0/en/html_node/Invoking-guix...
This is how every LLM API has worked for years; the API is a stateless token machine, and the prompts + turns are managed by the client application. If anything it's interesting how standard it is; no inside baseball, they just use the normal public API.
Y'all, please actually read the homepage before dunking on someone's project...
Do you have a source for this? I couldn't find anything about this, and I find it strange that Electron (which uses the open-source chromium engine but not Chrome) would automatically send tracking information to Google.
That's a fair complaint, and I'm definitely biased since I'm technically oriented. That said, discarding it is totally fine as long as people who want it at least get the option; and if even showing it is too confusing to users, it's a lot better to have a "developer" toggle in settings that enables all this stuff, rather than not having it at all.
Haiku's certainly not crazy accessible right now, but it has some ideas that I think other OSs should take note of.
You're right; I was mostly thinking about problems with Linux since thats my daily driver. It would have been better to say that Haiku gives developers the same UX affordances for interacting with their system as non-technical users.
When using Linux I'm frustrated by an overall lack of UX, but when using Windows/Mac it's developer specific UX that's ignored.
It's little things like errors automatically prompting you to open a graphical debugger or processes being grouped by application. There's sensible UX that doesn't expect me to be a wizard to understand what's going on or how to dig deeper.
Obviously it has rough edges (as, well, honestly all operating systems do), but the things that do work work really well.