Viewing profile — namjh
namjh
HN member- Joined
- Wed, Dec 29, 2021, 4:41 AM UTC
- HN karma
- 51
- Public activity
- 24 items
- HN profile
- View on Hacker News ↗
About namjh
Recent public activity
- story
- story
- comment
-
comment
Comment #49153163
[dead]
-
comment
Comment #48081998
As a South Korean I'm lowkey surprised that most reactions posted here is describing the detention experience to be some kind of human rights abuse. Most Koreans debating on Intern…
-
comment
Comment #46158379
Yes we do have[^1] but unfortunately it looks like not checking the integrity, just reachability. [1]: https://downdetectorsdowndetectorsdowndetector.com/
-
comment
Comment #42599399
Amazed that Safari does not support WebGPU even with the latest release. Opened Chrome and it works. Very cool demo!
-
comment
Comment #42458193
> Consequently, this also means you cannot define two error variants from the same source type. Considering you are performing some I/O operations, you won't know whether an error …
-
comment
Comment #42060433
Anyone who needs to handle FFI in Rust, should read the FFI chapter in Rustonomicon: https://doc.rust-lang.org/nomicon/ffi.html Unsafe Rust is indeed very hard to write correctly. …
-
comment
Comment #41773764
There was an NFT section in the claim form so certainly they are aware of but I'm not sure it's still open
-
comment
Comment #41471680
Big kudos to Rust compiler devs about their sophisticated type system and its kind (and highly intelligent) help messages. A little concern is that AFAIK its complexity in type sys…
-
comment
Comment #41398879
That's because the code triggering compilation error is using reference. If you use Rc or Arc (which pays runtime cost) there should be no lifetime at all. Albeit I admit there som…
-
comment
Comment #41398735
IMHO the mentioned examples of complexity like multiple type variables and lifetimes with bounds are for who "really" wants compile-time contracts. These are mostly opt-in so highe…
-
comment
Comment #41352781
Do we have a better method of verifying compilation output than just re-executing the compiler with same source, than comparing the output? TEE attestation could be a thing(albeit …
-
comment
Comment #40941876
Albeit 1.6PB/day may be somewhat exaggerated, comparing Binance to Ethereum needs much more consideration including: - Ethereum's transaction throughput is normally 12~20tx/sec so …
-
comment
Comment #40923886
Interesting project and kind of tangential topic, will JIT compilers still be widely adopted given they are considered a critical attack vector when it misbehaves? I wonder if ther…
-
comment
Comment #40745404
Great work! I really enjoyed the interactivity. Actually I already was aware of the concept of zero-knowledge proof from the wonderful article by ZCash(which is a privacy-oriented …
-
comment
Comment #40745379
In reality, the entire map should be sent first to the verifier (with colors hid behind the post-it) so if it was a bogus randomly colored map, you may find two adjacent points hav…
-
comment
Comment #39084840
Am I the only one just seeing a blank page? Proxying via archive.is did not help. Edit: after some googling I found https://lists.freebsd.org/archives/freebsd-hackers/2024-Janu... …
-
comment
Comment #36784843
> The problem is that in the ecosystem we are building the prevailing assumption is that anything async must also be Send, which means we end up using Send primitives even in non-S…
-
comment
Comment #36783687
> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing wha…
-
comment
Comment #36719758
Might be related: https://arxiv.org/abs/2211.16421 It's a paper about directly learning via JPEG encodings which works well with visusal transformers' patch mechanism.
-
comment
Comment #36690030
When I was a newbie for Rust, I was encouraged to use CLion with the Rust plugin. What's the difference between CLion + Rust and IDEA + Rust?
-
comment
Comment #36665507
Wow, if I were you, I would never think of analyzing the rustc source code. Great job!