Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
2
Comments
273
Joined
3 yr. ago

  • There is indeed a caveat in the introduction to the Reference that there may be statements in it that are specific to rustc. However, the authors strive to keep statements about the implementation separate from statements about the language.

    The main reason there's not yet an "official" spec is that creating one takes enormous time and money, which are always limited resources. (Note that both C and C++ had no formal standard for over a decade after their initial release.) The Reference is "good enough" to make a formal spec not strictly necessary, and the existence of Ferrocene makes it even less necessary, since anyone who absolutely needs a spec can use Ferrocene.

  • You can say the Rust implementation is wrong if it doesn't conform to the Reference. That is not the same as "you personally disagree with the behavior."

    Rust's guarantees about the behavior of safe code are far stronger than anything C or C++ provides, with or without a formal spec.

  • Creation is easy, assuming the many-worlds interpretation of quantum mechanics!

  • Delete prior iterations of the loop in the same timeline? I'm not sure there's anything in quantum mechanics to permit that...

  • In the universe where the list is sorted, it doesn't actually matter how long the destruction takes!

  • Reminds me of quantum-bogosort: randomize the list; check if it is sorted. If it is, you're done; otherwise, destroy this universe.

  • Or Stockholm Syndrome

  • You're not wrong, but not everything needs to scale to 200+ servers (...arguably almost nothing does), and I've actually seen middle managers assume that a product needs that kind of scale when in fact the product was fundamentally not targeting a large enough market for that.

    Similarly, not everything needs certifications, but of course if you do need them there's absolutely no getting around it.

  • In case you're still interested in this type of resource, here's another one I just learned about: https://google.github.io/comprehensive-rust/

    It's by the Android team at Google, and while it doesn't require knowledge of C++, it seems to be intended to bring devs up to speed on the concepts required for using Rust in Android and Chromium.

  • Does crates.io have a backup plan?

    Jump
  • Wow, I definitely should have google that myself before asking, but thank you for explaining and calling out that data point.

    I honestly think that shows that it was in fact a bad idea to assign TLDs to countries. Having a country code acronym with a popular tech meaning is essentially just luck of the draw, so they've basically just arbitrarily given a few small countries a valuable resource to sell. I guess that benefits those countries, but I doubt "quasi-random fundraising for small countries" was ever the intent.

  • Does crates.io have a backup plan?

    Jump
  • But do they actually have autonomy, give that random companies can use .io and .ai? Or did the British Indian Ocean Territory and Anguilla approve all such uses of those domains?

  • Does crates.io have a backup plan?

    Jump
  • Does crates.io have a backup plan?

    Jump
  • Obviously this isn't specific to Rust, but frankly it's bizarre to me that ICANN chose to tie top-level domains to country codes in the first place. Languages might have made sense, but a major feature of the internet is that it's less beholden to political boundaries than most of the physical world is.

  • Yep, learned it recently from a list of things that are, surprisingly, named after real people. Deb and Ian eventually got married but are now divorced.

  • It's so out of date that Deb and Ian are no longer together

    (...this is actually true, not just a joke)

  • But "drop-in replacement"? That's a strong and specific claim.

    I do actually think that WebAssembly will enable something - maybe Rust, but more likely something simpler - to eventually dethrone JS in the browser. I also do think it seems beneficial to have your client and backend in the same language.

  • ... the issue I have is people lying and saying Rust is a drop in replacement for js

    I am genuinely curious whether you've actually seen this claim before, or if you badly misunderstood or are simply exaggerating a claim about Rust being a good language for web servers, or if you simply made this up as a straw-man. I can't imagine anyone who knows what they're talking about using those words I that order.

  • To be clear, you're saying you trust git metadata to be preserved even when forge/issue-tracking/etc metadata is not?

    I suppose that's probably the case more often than not. I think it's still preferable to trust the forge you use than to spend any significant amount of time or effort trying to ensure that the team has strong enough commit-message discipline to compensate for the risk of losing data in an issue-tracker or forge.

  • "trust them" meaning trust github and gitlab?