Live data from Hacker News

Viewing profile — qouteall

qouteall

HN member
Joined
Sun, Jun 04, 2023, 9:25 AM UTC
HN karma
372
Public activity
76 items

About qouteall

No profile information was provided.

Recent public activity

  1. comment
  2. story
  3. story
  4. comment
    Comment #47097714

    It's probably due to server side rendering and rehydration. The rehydration use server side component state to override DOM state.

  5. comment
    Comment #47097687

    With modern IDE and AI there is no need to save letters in identifier (unless too long). It should be "sizeInBytes" instead of "size". It should be "byteOffset" "elementOffset" ins…

  6. comment
    Comment #46954953

    Normally the database and message queue is decoupled from the backend service. This decoupling makes managing simpler and make cross-language things easier. But if the type system …

  7. story
  8. comment
    Comment #46553107

    WebAssembly standard design has considered binary size optimization. The format itself is quite compact. But porting native code to Wasm often brings many large existing libraries …

  9. comment
  10. comment
    Comment #46553080

    They originally used JS realm polyfill, which is not real JS realm. The polyfill has some security holes. Now they switched to Js interpreter in Wasm. https://www.figma.com/blog/an…

  11. comment
    Comment #46553050

    I've written about limitations of WebAssembly https://qouteall.fun/qouteall-blog/2025/WebAsembly%20Limitat... WebAssembly still doesn't provide a way to release memory back to brow…

  12. comment
    Comment #46400111

    One limitation of Rust macro is that it can only access code token, not actual type information. When macro sees a type `X` macro can never be sure whether it's `&str` as Rust allo…

  13. comment
    Comment #46341486

    The optimistic concurrency control that reads multiple shards cannot use simple CAS. It probably needs to do something like two-phase committing

  14. comment
    Comment #46341452

    Thanks for reply. So in my understanding: - The transactions that only touch one shard is simple - The transactions that read multiple shards but only write shard can use simple op…

  15. comment
    Comment #46341056

    In real-world business requirements it often need to read some data then touch other data based on previous read result. It violates the "every transaction can only be in one shard…

  16. comment
    Comment #46333485

    This video criticizes Rust using perfect solution fallacy. Critizing a useful thing just because it's imperfect. https://en.wikipedia.org/wiki/Nirvana_fallacy

  17. comment
    Comment #46324969

    We are in the down season.

  18. story
  19. comment
    Comment #46311408

    There are two kinds of slowness. One is trying hard while getting no visible result. Another is procrastination. The article refers to the first

  20. story
  21. comment
    Comment #46274752

    The better phrase is that "if it compiles, then many possible Heisenbugs vanish" https://qouteall.fun/qouteall-blog/2025/How%20to%20Avoid%20F...

  22. comment
    Comment #46274734

    I want to add Contagious Borrow Issue https://qouteall.fun/qouteall-blog/2025/How%20to%20Avoid%20F... Contagious borrow issue is a common problem for beginners.

  23. comment
  24. story
  25. comment
    Comment #46252719

    Lecture video https://www.youtube.com/watch?v=orDKvo8h71o