Live data from Hacker News

Viewing profile — moldavi

moldavi

HN member
Joined
Sat, Aug 01, 2020, 12:09 AM UTC
HN karma
164
Public activity
77 items

About moldavi

No profile information was provided.

Recent public activity

  1. comment
    Comment #42276416

    Do Apple's chips (M1 etc) change this at all, since they share memory with the GPU?

  2. comment
    Comment #33751053

    You know nothing of what I'm programming. You don't know when, whether, or how my program accesses or deletes data. You don't know what domain I'm in, whether I'm on a team, or wha…

  3. comment
    Comment #33750707

    GP was confused about why the doubly linked list case was so important, so I enlightened, it's an example of an entire class of the borrow checker's problems. Your response isn't r…

  4. comment
    Comment #33750456

    It's not just doubly linked lists. They're just a basic example of borrow checking not being able to handle a lot of easy patterns that are perfectly safe in other languages.

  5. comment
    Comment #33750439

    I've experienced this as well. Any disagreement always comes down to "you just haven't used it enough". I let myself take that gaslighting for years before I decided to just not go…

  6. comment
    Comment #33750414

    Single ownership often introduces bugs of its own. In Java, I never need to create an Err if the thing my ID is "pointing" to isn't around anymore in whatever hash map the borrow c…

  7. comment
    Comment #33750408

    Pony is a great example of fearless concurrency without the borrow checker's difficulties.

  8. comment
    Comment #33750404

    That absolute claim is simply not true. That's like saying that people need to avoid shared mutability in every program, which simply doesn't make sense for a lot of programs, espe…

  9. comment
    Comment #33750378

    Easier than C or C++ for sure. But I definitely wouldn't say that Rust as easy as a GC'd language like Java or Go. They have strictly less constraints to deal with, they can let yo…

  10. comment
    Comment #33750346

    Can we please not do this? It's fine to give a different viewpoint, but it's surprisingly common that whenever someone says anything bad about Rust, a Rust user comes in to say tha…

  11. comment
    Comment #33750337

    I'm sometimes a bit confused when people say that Rust has less cognitive load. I assume that's compared to something like C or C++, right? I've used Rust and (imperative-style) Sc…

  12. comment
    Comment #33584379

    Rust will never be used as widely as GC'd languages like Java, Go, C#, etc. It's incredibly well-designed, but you can't design away the inherent complexity of writing safe, secure…

  13. comment
    Comment #33058345

    I've seen both sides of this, as a Rust user and as a Go user. Rust users are generally friendly to one another, and to people who are interested in Rust. Hoever, some Rust users a…

  14. comment
    Comment #32718937

    For a single player turn-based game, I'm not so sure the tradeoff is as obvious as everyone says, after coding one in C++ and another in Rust. It's turn based, so I don't need AAA …

  15. comment
    Comment #32242702

    Saying it's "idiomatic" isn't very actionable advice for people, the average programmer hears that and doesn't really know when to use Rc over other approaches. I also wouldn't say…

  16. comment
    Comment #32242615

    That's where the discipline comes in: one has to know when it's okay to use the simpler approach (indices into a Vec), and when it's better to use Arcs such as to prevent privacy p…

  17. comment
    Comment #32241018

    In Rust, people tend to go for the easiest solution that works within the borrow checker, and not workarounds like Rc or Arc. Otherwise, the performance hit means there's little re…

  18. comment
    Comment #32240865

    That's why I said one should have the discipline and practices in place to avoid this bug. I think we can do better than saying that indexes into Vecs are "non-idiomatic" in applic…

  19. comment
    Comment #32240733

    That's why I mentioned one needs to have discipline, to not use that particular solution. We agree it's not the best solution. And it's easy for us to say that now, after I've spel…

  20. comment
    Comment #32240161

    In fact, in the pursuit of eliminating memory-safety and security bugs, Rust can sometimes makes some privacy bugs more likely. For example, in GC'd/RC'd languages, if we have seve…

  21. comment
    Comment #29610074

    React and Polymer seemed like an okay balance of of OO and functional... are our current GUI architectures really that nasty?

  22. comment
    Comment #29610060

    The author could have recommended Scala, which has all of Rust's type system benefits, plus garbage collection (and of course, minus the low level control over performance). YMMV t…

  23. comment
    Comment #29610017

    I'm also curious about the architectural consequences of Rust. It seems to force us into a very procedural or functional style, and sometimes makes us use parallel collections for …

  24. comment
    Comment #29300370

    Something about Odin I like is that you can have multiple allocators, and use a bump allocator for just a specific call (and its subcalls), and afterward free it all at once, and g…

  25. comment
    Comment #28830830

    Doesn't GhostCell preclude deletion, and effectively grow forever?