Programmer based in Munich, Germany, interested in Rust, programming, science, etc. He/him
GitHub: https://github.com/Aloso – Mastodon: https://hachyderm.io/@aloso
And are you sure the license is the sole reason for that? With a sample size of 2, this correlation might very well be coincidence. I’m not intimately familiar of the history of Linux or BSD, so I might be off base, but I don’t think a permissive license like MIT prevents a project from being widely adopted and becoming successful.
I can’t find it on LemmyRS, is it possible that LemmyRS is not federating with kbin.social?
i also saw that there’s about 200+ open tickets of variable importance
Note that it is normal that the number of open issues grows faster than issues are resolved. For example, rust-lang/rust has 8,963 open issues and 39,803 closed issues. microsoft/TypeScript has 6,001 open issues and 31,397 closed issues. A large number of open issues isn’t necessarily concerning, unless high-priority issues (vulnerabilities and critical bugs) stay open for a long time.
I’d like for the r/rust community to completely migrate to lemmy, and for the r/rust moderators to become moderators of the chosen lemmy instance.
I don’t care which instance it will be, although I do like the idea of the Rust community being fully self-sufficient and self-governed by hosting our own instance (but still being interoperable with others). The main downside seems to be that people who are active in multiple communities will need multiple accounts, and creating an account requires
And if you use a mobile app as well as the web app, you need to login twice after the account was approved.
On another note: The lemmyrs.org instance currently has several “communities”, which are more like categories. They might be a substitute for Reddit flairs, which should allow people to filter what they see on their Reddit homepage. However, Lemmy doesn’t support flairs, and on r/rust they weren’t actually used that much. Most people didn’t set a flair when posting something, which kind of defeated the purpose. I think we should come up with a proper solution for this at some point.
There are executors for more specific use cases.
bastion
is a “Highly-available Distributed Fault-tolerant Runtime”, inspired by Erlang, and including an async executor.embassy
includes an async executor specifically for embedded systems.fuchsia-async
is an executor for use in the Fuchsia OS.wasm-bindgen-futures
converts Rust Future
s to JavaScript Promise
s and schedules them to run to completion. It could also be seen as a (very basic) executor.
You need to tell the user that this is an error, otherwise they don’t know if it succeeded or not.
The last line is incomprehensible, just use a full sentence.