Live data from Hacker News

Viewing profile — mtzet

mtzet

HN member
Joined
Fri, Nov 25, 2016, 10:28 AM UTC
HN karma
521
Public activity
104 items

About mtzet

No profile information was provided.

Recent public activity

  1. comment
    Comment #48970699

    The main point is to use zswap over swap plus zram. The sd card usecase definitely doesnt want swap to disk, compressed or otherwise, so zram or no swap are the options.

  2. comment
    Comment #44853856

    A normal desktop with non-soldered components is more repairable, cheaper and can also run on stock Linux? The only selling point is the form factor and a massive amount of GPU mem…

  3. comment
    Comment #42524962

    I don’t get this take. Is it so hard to understand that a computer operates on a giant array of bytes? I think the hard thing to understand is that C’s pointer syntax is backwards …

  4. comment
    Comment #41820267

    So let's focus on the case where I'm setting up a bunch of bare-metal hosts as servers. What's the value proposition of using FreeBSD over Debian/Ubuntu if we're not counting famil…

  5. comment
    Comment #39882484

    > special case where all memory can be easily handled in arenas That seems to be an unfair bar to set. If _most_ objects are easily allocated by an arena, then that still removes m…

  6. comment
    Comment #39579337

    Most software in the industry is slow because it's doing a lot of stuff that it shouldn't. Often times additional "optimization" layers adds caching, but makes getting to the root …

  7. comment
    Comment #37674622

    Processors doing out-of-order execution doesn't change the semantics of the code. That's very different from the example where gcc just throws away the assignment. The idea that he…

  8. comment
    Comment #36401241

    > I’m not a go developer. How does go document how a function can fail? There's no magic to it. Errors are values, so it's a part of the function signature that there's an error co…

  9. comment
    Comment #36401179

    I'm not arguying that go has modern tech, but rather that it has modern sensibilities. This means not trying to force 90s style OOP, preferring static linking for easier deployment…

  10. comment
    Comment #36400399

    I agree that go and rust have different areas, but that was less clear when they were getting started. Back then go was trying to figure out what it meant by 'systems programming l…

  11. comment
  12. comment
    Comment #36101734

    > as best as I understand it, because of the content of JeanHeyd's blog post on reflection in Rust. I'm having trouble finding it. Can anyone link this post?

  13. comment
    Comment #35804235

    Off the charts? Compared to completely at will maybe. You generally have to pay 3 months severance + 1 month per 3 years of employment for a maximum of 6 months severance after 9 y…

  14. comment
    Comment #35491204

    As someone who knows nothing at all about the success of PayPal, can you elaborate on why? I'm also curious about his role in the success of Tesla and SpaceX. I personally find tho…

  15. comment
    Comment #35008007

    I agree. Emacs out-of-the-box is terrible, but my Doom Emacs config is all 50 lines of code. For that I get: - IDE-like features via LSP - The best git porcelain out there: magit. …

  16. comment
    Comment #34867017

    On the other hand, I've found that a lot of the caching that happens organically from each component building up it's own state of the world can lead to poor performance of its own…

  17. comment
    Comment #34745137

    I agree about being pragmatic and doing what the business needs are at the moment! But that's also why I argue for having less process up front and creating it as needed. The maste…

  18. comment
    Comment #34739827

    Gitflow merges everything to a linear 'master' branch, from which releases are tagged. That means you can't create new 1.x releases after 2.0 has been tagged. In TBD you'd have mos…

  19. comment
    Comment #34737235

    To me the argument makes more sense in reverse: Gitflow solves a problem few teams actually have. Throwing away a working (simpler) process of having a single trunk when there's no…

  20. comment
    Comment #31189634

    > IOW, if I build a system with yocto for an embedded system, which is also a very useful candidate for a read-only system image installation, I cannot use this feature for this us…

  21. comment
    Comment #31189560

    > Systemd has this problem How does systemd have a problem? Systemd doesn't care about having a read-only rootfs at all, except that it supports it and now ships a little tool that…

  22. comment
    Comment #30243588

    Theoretically, Wayland has proper support for fractional scaling, and this just works. In practice however, this only works for wayland-native applications and all applications run…

  23. comment
    Comment #30071424

    Chesterton's Fence is a valid point, but I dislike how the article celebrates it. Doing the archeology required to figure out why things are the way they are is oftentimes much mor…

  24. comment
    Comment #29990827

    I can highly recommend the interview with Jason Gregory of Naughty Dog from Handmadecon 2016. He gives a lot of insight into the reality of working with the scheme-based format in …

  25. comment
    Comment #29862785

    The article expands upon this point in great detail. To wit: > Flutter's HttpServer that crashed on iOS if the user briefly switched to another app and then back to mine. The autho…