Live data from Hacker News

Viewing profile — gorset

gorset

HN member
Joined
Sat, Jan 15, 2011, 11:54 AM UTC
HN karma
282
Public activity
80 items

About gorset

Programming, scalability and reliability. http://erik.gorset.no/

Recent public activity

  1. comment
    Comment #46741848

    One of the advantages of of protobuf I never see anyone highlight is how neat and well-designed the wireformat is, in terms of backward/forward compatibility and lowlevel stuff you…

  2. comment
    Comment #46185890

    This brings back memories debugging an azul zing bug where an effectively final optimization ended up doing the wrong thing with zstd-jni. It was painful enough that I couldn’t con…

  3. comment
    Comment #45613973

    I agree. It’s the enshittification of the internet. Luckily we still have infrastructure providers with more sensible offerings. We don’t have to use aws, gcp, etc.

  4. comment
    Comment #45492579

    I've used bazel for about 10 years, all in small orgs. Right now, single digit team. I don't think there exists a better solution for a project mixing Java and C/C++ than Bazel. Th…

  5. comment
    Comment #45311234

    That’s the default in the monorepos I’ve worked on. When a third party dep is broken or needs a workaround, just include a patch in the build (or fork). Then those patches can be u…

  6. comment
    Comment #45100928

    I enjoyed both talks a lot. I really appreciate the work done to evolve Java. They seem to be able to both fix earlier mistakes (and there were many!) and new ones from happening. …

  7. comment
    Comment #45099606

    I think the «best practices» found in Java enterprise has meant that a lot of people think all Java has to look like that. High performance Java is awesome and can be competitive w…

  8. comment
    Comment #45067783

    Mechanisms for getting the linux kernel out of the way is pretty decent these days, and CPUs with a lot of cores are common. That means you can isolate a bunch of cores and pin thr…

  9. comment
    Comment #44985631

    Isolating a core and then pinning a single thread is the way to go to get both low latency and high throughput, sacrificing efficiency. This works fine on Linux, and common approac…

  10. comment
    Comment #44680100

    In a previous project we used fixedint32/64 instead of varint values in the schema for messages where performance was critical. That left only varint used for tags. For encoding we…

  11. comment
    Comment #42567107

    Nice work! I love the care and discussion around low level optimizations, as such things are often ignored. There are a lot of interesting variants of rank/select and other succinc…

  12. comment
    Comment #42565837

    The number of unique int32 values is not that great, and a full bitset would only be 512MB. Hard to bit a dense bitset in performance. As a general purpose data structure, I would …

  13. comment
    Comment #42547943

    Selective testing is great also for smaller projects to help keep velocity high for merging and working with branches with many commits. I implemented selective testing using bazel…

  14. comment
    Comment #42539237

    I'm a big fan of this solution! It's always been annoying to perform all the ceremony involved in deploying a system with a bunch of files, with config, scripts and system written …

  15. comment
    Comment #42535088

    I always found the existing bazel integrations annoying. My solution has been to generate .classpath based on a set of bazel queries. Not what's officially recommended, but it has …

  16. comment
    Comment #42533914

    There's a lot of ceremony to run jdtls! I find it easier to just install language servers using brew. Then the command can be simplified to cmd = { 'jdtls', '-data', home_dir .. '/…

  17. comment
    Comment #41688652

    They could also have gone the commercial route and gotten Zing with their pauseless GC. It’s been around forever and they even cover Cassandra in their marketing. https://www.azul.…

  18. comment
    Comment #41656800

    Patch series comes from the linux kernel workflow, which git was developed to support. https://kernelnewbies.org/PatchSeries In this workflow you review every commit and not just t…

  19. comment
    Comment #41654878

    The use case is when you look at a branch as a series of patches. Reviewing a clean set of commits is much easier than a branch full of mistakes and wrong paths taken. Useful when …

  20. comment
    Comment #39322248

    I struggle to use lmdb when using resource isolation (like docker, nomad exec driver). The hidden complexities really become apparent when you build largish systems using shared in…

  21. comment
    Comment #39235733

    I was asking around in my network after experience with self hosting S3 like solutions. One serious user of SeaweedFS recommended looking into min.io instead. Another serious user …

  22. comment
    Comment #38598299

    There are some workarounds. In my company we have a script that generated IDE files automatically. It uses `bazel query` and `bazel build` to find all external and non native depen…

  23. comment
    Comment #38139100

    I have fond memories of my grandfather serving RC Cola to me in a small town in Norway 30 years ago. Imported to the town by a small independent shop focusing on cheaper alternativ…

  24. comment
    Comment #37180448

    The lack of “interface” was one of the main reasons I never ended up using scheme to build production systems. I loved playing with scheme in my university days 20 years ago, and l…

  25. comment
    Comment #27306424

    We use gitlab and review a commit at a time and do CI runs on each commit in the MR branch. Just plain git with the fixup/interactive rebase dance. Gitlab is not optimized for this…