koto VS crates.io

Putting the finishing touches on a procedural macro to bind Rust code to koto we want to use in synth. Also a blog post about it is on the way.

I'm currently trying to improve the vtable dispatch in koto (because I want to use it in synth).

I've been working on Koto which is intended for this kind of use case. I've been thinking about extending Rust applications with scripting, and I have games in mind but more generally I'm interested in rapid iteration in creative applications. It's still very early so I haven't shared it more widely but I'd be curious to hear what you think.

https://github.com/koto-lang/koto

As for 240x240 SPI LCD display support, I'm not sure. You might be able to find something on This curated list or on https://crates.io/

The two closest crates to this on crates.io are rustmex and mex-sys.

You're right that publish=false is a good hint, although I could imagine someone not wanting to publish to crates.io but still wanting to publish to a prerelease or something on Github.

I'm hoping this will help crate maintainers keep an eye on the size of the packages they're pushing to crates.io, so we can have fast and light builds as much as possible!

crates.io is append-only (they took the opportunity to learn from NPM and co here;-). I see little problems going forward, especially considering the regular crater runs (build _all_ existing rust code to test new compiler releases or the tooling for regressions). With all the code getting built regularly, devs will notice old crates breaking and will fix the tooling before it goes out to the wider public.

I wouldn't necessarily call it dragging in technical debt but that's probably a difference in philosophy: to me it's a standardized solution and it's great that we can just pull it in from crates.io. I don't have a problem with a project having maybe hundreds of dependencies because of the strong guarantees that crates provide. I definitely prefer it to C++ projects that include the same hand-rolled functionality in multiple incompatible ways.

Lifetimes before there was NLLs. So much headache that just *poof* went away. Also String vs. &str - still hate that one. Once I started playing around with Types I started missing Generics very quickly. Also, while crates.io is *great* (I made the mistake of trying to learn node.js once), I do sometimes miss a large standard library. For certain things there's one obvious standard libraries (e.g. Serde), it can get a bit confusing for things where a novice would expect something standard: async - which is odd b.c. safe async programming is one of the hallmarks of Rust.

You can find third-party crates on crates.io or on lib.rs. lib.rs is an alternate frontend to crates.io (the listed crates are the same). IMO, lib.rs has a nicer UI and does a better job of ranking search results.

GitHub scans commits with regex at first. Then it sends the matched strings to crates.io's verify endpoint and the endpoint will check it is really an API token so that false positive should not be caused.

There is the following open issue: https://github.com/rust-lang/crates.io/issues/326