Live data from Hacker News

Viewing profile — __jem

__jem

HN member
Joined
Fri, Oct 09, 2020, 3:31 AM UTC
HN karma
853
Public activity
193 items

About __jem

No profile information was provided.

Recent public activity

  1. comment
    Comment #38821569

    Right, because endless US involvement in ground wars in the middle east has always been firmly on the side of "concrete facts."

  2. comment
    Comment #38811829

    Isn't the point of a dev environment precisely that the intern can drop tables? Idk, I've never had a shared database not turn to mush over a long enough period, and think investin…

  3. comment
    Comment #38425463

    That's why OsString exists.

  4. comment
    Comment #38310381

    You know, minus sexually abusing his sister.

  5. comment
    Comment #38208096

    > the return type of MyWidgetFactory() probably isn't. Isn't the return type of a widget factory method obviously Widget? This doesn't seem like a great example. Of course the meth…

  6. comment
    Comment #38091187

    I've worked with some databases that are 20+ years old and have outlived multiple application iterations. There's always going to be cruft in this kind of situation, it just comes …

  7. comment
    Comment #38091143

    Reclaiming the physical storage of an unused column is often a costly and sometimes impossible operation, which is why many legacy applications end up with the equivalent of my_col…

  8. comment
    Comment #38022525

    What is the fact that many foundational ecosystem crate contain unsafe code supposed to prove? That's the entire point of the language. That someone writes a really good regex crat…

  9. comment
    Comment #37965134

    yes, it's harmless in this position but it provides no additional benefits to the select 1 idiom and is suggestive of poor query discipline. it's far easier to say just don't ever …

  10. comment
    Comment #37964832

    you're getting downvoted because it's not really a preference, it's pretty widely known to be bad practice and unhygienic in production queries. select * would get your pr rejected…

  11. comment
    Comment #37638077

    I'm not sure this is really an issue with transactionality as a single request can obviously be split up into multiple transactions, but rather that even if you correctly flag the …

  12. comment
    Comment #37630437

    Rust is memory managed, it just doesn't have a garbage collector.

  13. comment
    Comment #37616480

    Friction with modern devops practices is a big one.

  14. comment
    Comment #37366951

    Passing around functions that have already been partially applied means that downstream users can't incorrectly call or accidentally modify the arguments which have already been ap…

  15. comment
    Comment #37190974

    I'm not sure if he's made an official statement about his versioning policy, but if you look at https://crates.io/users/dtolnay?sort=downloads , you can see that most of his crates…

  16. comment
    Comment #37190637

    Correct, serde does not follow semver.

  17. comment
    Comment #37190448

    Well, there is an exit path for those who want to compile from source. If you mean build from source for Cargo users, I believe there's issues with how feature flags interact with …

  18. comment
    Comment #37190315

    > I found the discussion to be mostly very civilized and focused on finding solutions for those affected. I really disagree with this characterization of the discussion. While ther…

  19. comment
  20. comment
    Comment #37190219

    People have complained about the build time of proc macros for ages in the community. This might be a misguided hack, but the response to this is bordering on a witch hunt, particu…

  21. comment
    Comment #37090353

    Only some of the providers are based on Terraform. I think it would be incorrect to say it's "powered by Terraform."

  22. comment
    Comment #37090267

    > However, tailscale focuses on access different devices to each other, while Narrowlink focuses on access to the services trough on the agent as a proxy. You can easily do the sam…

  23. comment
    Comment #37001722

    Could not disagree more strongly that Datomic is well maintained. I'd view it as a significant liability in any organization using it without very good reason. My experience operat…

  24. comment
    Comment #36974334

    Well, in the real world, the premise is false, but not because writing memory safe code is in fact easy, but because in aggregate in large code bases it's impossible.

  25. comment
    Comment #36974267

    Okay, but using unsafe for FFI is entirely different than the claim that you can only achieve performance optimizations through "dereferencing pointers without anything extra runni…