People can have various reasons for such look. It can be a symbol of non-conformity.
Official Rust spaces have a code of conduct that is inclusive and forbids discrimination, and this may attract people who otherwise wouldn’t feel comfortable to participate.
I don't think there are any OSS/FLOSS licenses that have non-commercial clauses, so CC NC is the best you can get among popular licenses.
When you use dependencies, your project (its users) must comply with all of the licenses together. IANAL, but I think CC and MIT (and other similarly permissive) licenses are compatible — you'll need to include text of the permissive licenses to comply, and that's not against CC.
If you take contributions, be clear what license they give you.
I’d love static analysis that finds which functions may panic, which are guaranteed not to. On a related note, it’d be nice to be able to hoist panics out of loops and coalesce multiple consecutive assertions into one (llvm can’t do it, because partially done work is a side effect).
To generate the LLVM code correctly you need to run build.rs if there is any, and run proc macros which are natively compiled compiler plugins, currently running without any sandbox.
The final code isn’t run, but the build process of Cargo crates can involve running of arbitrary code.
The compilation process can be sandboxed as a whole, but if it runs arbitrary code, a malicious crate could take over the build process and falsify the LLVM output.
Yes, it's Blink without the bits that Google doesn't share (I wanted to be precise that nobody can compile actual Chrome from public sources, they can build Chromium which is almost but not quite the same)
@-me if you have tips to share.
Vivaldi uses the same engine as Chromium, and the company has been founded by ex Opera developers.
Plus you can make certain sites always automatically open in their designated container, even if you followed a link. You can keep sites know for spying away from your logged in identity. You can have your banking and other important sites in another container for extra defense in depth.
I'm all for it, but I don't see how I could do that with lib.rs in particular. The site already takes a swing at the anarcho-capitalist-flavored plutocracy.
The context here is that it was after I had a heated megathread in the bugtracker where multiple people were defending cryptocurrencies on their merits as money, decentralization tool, or an ideal to aspire to.
Burntsushi's objection was different form these, in a subtle way, and I needed more explanation to understand the difference. His phrasing with "sneering" — to me — was not clear (I understood it as "don't sneer at cryptocurrencies, because they don't deserve to be sneered at" rather than "cryptocurrencies are bullshit, but you can't say it so directly and rudely").
Additionally, I did not want to invite another bugtracker megathread about cryptocurrencies, which is why I tested his patience asking for a statement, rather than merely linking to the bugtracker like he asked. I see it as an ask, perhaps negotiation. I don't think that exchange deserves to be summed up as "crap".
Anyway, I'm probably testing your patience too, so have a nice day!
(you're replying to the guy who runs lib.rs and responded to burntshushi in that thread)
The initial request was just a question about removal, without getting into why, so it had no stance to misrepresent. The text I proposed was prefaced with "how about: …?", and based on reasons I've been given previously by other people. That was a question whether that's the right representation, not a statement. I made a wrong assumption, the text wasn't right, so we found a different one that satisfied him.
I maintain a long-term Rust + Node.js project, and the Node side is the painful one.
Node makes backwards-incompatible changes, and doesn’t have anything like the editions to keep old packages working. I can end up with some dependencies working only up to Node vX, and some other deps needing at least Node v(X+1).