• 4 Posts
  • 62 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle








  • they don’t want to do anything about federation or messenger intercompatibility.

    Their reasoning is that they only trust themself to keep the meta data safe and so need you.

    That’s not their reasoning. Their reasoning is that it’s much harder to evolve the protocol in a decentralized context than a centralized one. It’s not that they only trust themselves with your metadata, it’s that they can improve the protocol much faster in order to get rid of most metadata.

    They have been able to deploy a ton of protocol updates with regards to minimizing the amount of metadata anyone has access to (including them), while other decentralized alternatives have essentially been stuck in limbo for a while:

    • Secure Value recovery
    • Groups V2
    • Sealed sender
    • Usernames
    • Post quantum resistance

    On the other hand, Matrix, XMPP and email are very leaky with regards to metadata. I’m not going into email because that’s pretty documented, but here it is for matrix:

    • Message reactions are not encrypted
    • Group membership are not encrypted (which lead to attacks)
    • Profile pic and Name are public (visible by everyone even people with whom you don’t have any contact)










  • Zig is a very new and immature language. It won’t be kernel-ready for at l’East another 10 years.

    a better syntax

    That’s pretty suggestive. Rust syntax is pretty good. Postfix try is just better for example.

    Zig also uses special syntax for things like error and nullability instead of having them just be enums, making the language more complex and less flexible for no benefit.

    Syntax is also not everything. Rust has extremely good error messages. Going through Zig’s learning documentation, half the error messages are unreadable because I have to scroll to see the actual error and data because it’s on the same line as the absolute path as the file were the error comes from

    No hidden memory allocation

    That’s a library design question, not a language question. Rust for Linux uses its own data collections that don’t perform hidden memory allocations instead of the ones from the standard library.

    it’s more readable

    I don’t know, Rust is one of the most readablelangueage for me.

    Fast compile time

    Is it still the case once you have a very large project and make use of comptime?

    it’s simpler to learn

    Not true. Because it doesn’t have the guardrails that rust has, you must build a mental model of where the guardrails should be so you don’t make mistakes. Arguably this is something that C maintainers already know how to do, but it’s also not something they do flawlessly from just looking at the bugs that regularly need to be fixed.

    Being able to write code faster does not equate being able to write correct code faster.

    Really great interop with C

    Yes, because it’s basically C with some syntax sugar. Rust is a Generational change.