Comment on It's a mass extinction event

• Wooki@lemmy.world ⁨1⁩ ⁨year⁩ ago

  .net is not secure, it’s so far from secure it’s a joke.

  source

  • areyouevenreal@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Do you not think Rust also has security flaws? At least Microsoft patch theirs.

    source

    • fuck_u_spez_in_particular@lemmy.world ⁨1⁩ ⁨year⁩ ago

      There are of course security flaws, we’re humans after all. Unless the compiler and the language can be proven mathematically correct at least.

      But as described above, in practice the security flaws are easier to isolate in Rust compared to C# IME. The current story of security flaws in Rust is quite good so far.

      source

      • areyouevenreal@lemm.ee ⁨1⁩ ⁨year⁩ ago

        The current story of security flaws in Rust is quite good so far.

        That means nothing without knowing who said it. I find it hard to believe it’s anymore secure the C# without security research saying so. It’s a very complex language from what I understand with a lot of moving parts. It’s also dependant on external frameworks in a way that C# just isn’t. If you have a problem with .net there is a company behind it who is responsible. Who is responsible for actix web or seaorm?

        source
• fuck_u_spez_in_particular@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Rust has exactly the same problems with depreciation as many Frameworks rely on experimental features which are subject to change.

  Rust has actually quite a good record with depreciation and backwards-compatibilty etc. They are changing the language in non-backwards compatible way over editions, but the changes are mostly very manageable.

  But to not end up being another C++ (syntax-wise it’s a disaster IMHO), a few non-backwards-compatible changes every few years are the way to go, when it’s manageable.

  source

  • areyouevenreal@lemm.ee ⁨1⁩ ⁨year⁩ ago

    What’s so confusing about C++ syntax exactly? To me it seems to make a lot of sense given the languages history. Rust syntax isn’t even that different imo

    source
• fuck_u_spez_in_particular@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Learning curve is steep in the beginning, I agree (I wouldn’t argue painful though, maybe if you have to unlearn bad practices, like interior mutability though etc.).

  But I think it pays off after some time. I’m now faster in Rust than in C# with similar experience, and the quality of the code is definitely higher as well (which can be credited to the strict kinda opinionated design of Rust IMO).

  It composes really well, better than most (non-functional) popular languages. I think this is probably the Sell for Rust, as it additionally works remarkably well over the entire stack (kernel -> frontend) (in each abstraction level might be better/easier to use languages to be fair though).

  source

  • areyouevenreal@lemm.ee ⁨1⁩ ⁨year⁩ ago

    What’s interior mutability and why do you think it’s bad?

    I might have another try at rust some time in the future. I think I tried it in a bad situation having to use it for a web microsevices project when I had limited knowledge of the language. If it had been another language I probably would have been able to pick it up in the time frame required. Using it did cost me in terms of grades, and it was a poor decision to use that language at that time.

    The main things I struggled with were all the borrow checking and asynchronous stuff, as well as the lifetimes concept. I still don’t understand how you are meant to specify object lifetimes. In C you assign and free things manually, in Java and Python it’s done mostly automatically, in C++ you choose manual or automatic when it’s assigned. In Rust it seems it’s automatic until the compiler can’t figure it out and then it becomes manual, which is frankly bizarre.

    source