Interesting to see how much the perception of trucks varies globally. For many, it’s about versatility and utility beyond just daily commuting. The off-road and hauling capabilities often get overlooked in city-centric debates.

I like how minimal prompts keep focus, but adding just the right context like AWS profile or last command status really saves time and mistakes. Starship hits a good balance here.

The one thing I'd miss from my prompt if I went full $ is the hostname. And even with it in there, I still f it up sometimes.

From what I gather, projecting preserves the viewing experience which is part of the film's value, not just the image. Plus, sound extraction and timing sync can be simpler with a projector. Scanners capture detail but might miss some nuances that make film unique.

Emulating extended attributes for a filesystem is a fascinating approach. It can significantly streamline lightweight OS customization without needing a full port of the filesystem driver. Has anyone experimented with this in open-source projects? Would love to hear about practical results or challenges.

Linux has supported xattrs for many years; there's no need to emulate them.

Linux's xattrs appear to only be an array of bytes, while Haiku's extended attributes are typed (string, mime, int, llong, float, double, bool, icon, or raw). This means a compatibility layer is probably needed to handle encoding types into the value of the xattr. Xattr(7) says there is a limit of 64kb for the value. Some haiku programs allegedly use more, but i dont have an example handy. Further, specific file systems may impose additional restrictions. For instance ext4 requires all xattrs to fit in a single file system block (assuming that the man page I'm reading is not out of date).

For compressed files, HFS+ puts the entire contents in an (xattr né resource fork).

macOS resource forks values are "file-like" with position-based "block" read/write, Linux xattrs is a key-value map with atomic get/set operations on the whole value only.

Yeah, hit this exact wall building a small AI tool. Ended up spinning up a whole backend just to keep the keys safe. Feels like there should be a simpler way, but haven’t seen anything that’s truly plug-and-play yet. Curious to see what you’re working on.

It’s very obvious this account was just created to promote your product…

I don't even have a product although I'd love people to work on something open source together. Also, I'm not nearly cool enough to earn a green username.

> This DevOps friction is exactly why I'm building an open-source "Firebase for LLMs."

i dont understand your earlier statement then

I think they were replying to the person with the green user name :-)

Definitely hit this wall too. The backend just for API proxy feels like a detour when all you want is to ship a quick prototype. Would love to see more tools that make this seamless, especially for solo builders.