home.social

#orogene — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #orogene, aggregated by home.social.

  1. so this is happening.

    All my #Rust #RustLang repos are moved over. Now I just need to figure out CI, republish to crates.io, and archive the github side (and document a tombstone in their readmes).

    I have a bunch of other repos I'll either archive or delete as well.

    #KDL and #orogene will remain github-side for now because they're a bit more dependent on github services, but I would like to at least move orogene over eventually. KDL might be stuck, though, unfortunately, but I might move only kdl-rs.

    #bevy #miette

  2. so this is happening.

    All my #Rust #RustLang repos are moved over. Now I just need to figure out CI, republish to crates.io, and archive the github side (and document a tombstone in their readmes).

    I have a bunch of other repos I'll either archive or delete as well.

    #KDL and #orogene will remain github-side for now because they're a bit more dependent on github services, but I would like to at least move orogene over eventually. KDL might be stuck, though, unfortunately, but I might move only kdl-rs.

    #bevy #miette

  3. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!