4 ms·
I assumed you guys wouldn't do this, but thought this could lead to a larger adoption in this space. Alternatively I thought maybe you needed to have some clos
by panick21_ 5y ago
I assumed you guys wouldn't do this, but thought this could lead to a larger adoption in this space.
Alternatively I thought maybe you needed to have some closed source component from a vendor and could only include it like that.
- TD-Linux 5y agoI definitely didn't mean it as a feature request - blobs aren't actually that common in embedded (esp32 and some motor driver libraries are the most common exceptions), so I don't think it's important for adoption. In fact, not supporting it enables future ergonomics improvements and code sharing between tasks, so I appreciate that it's not a driving factor in the design.
- floatboth 5y ago> esp32 and […] are the most common exceptions Well, nearly anything having to do with wireless is typically blobs :/ Even Nordic has blobby SoftDevices, though you don't have to use them since Apache NimBLE exists (and rubble in Rust though that's only usable for advertising-only for now).
- steveklabnik 5y agoYeah, I hear you on the adoption thing for sure, though to be honest, right now we are laser focused on shipping Oxide's product, and so if nobody else but us uses Hubris, that is 100% okay. As our CONTRIBUTING.md mentions, we aren't yet at the stage where we're trying to grow this as an independent thing. It's true that vendors are likely to be an area where we have to deal with some things being closed source, though we're not simply accepting that as a given. This is one reason we're writing so much of our own software, and also, poking at the bits that must remain closed: https://oxide.computer/blog/lpc55 https://oxide.computer/blog/lpc55