Viewing profile — gsserge
gsserge
HN member- Joined
- Fri, Mar 10, 2017, 1:15 PM UTC
- HN karma
- 111
- Public activity
- 15 items
- HN profile
- View on Hacker News ↗
About gsserge
No profile information was provided.
Recent public activity
-
comment
Comment #30935472
> It was not nearly as obvious 15 years ago, as it is today, but all the signs were there. We (I include myself here) were just not listening closely enough to the countries that k…
-
comment
Comment #30935396
At the very least Germany could have said no to Nord Stream 1 & 2.
-
comment
Comment #27703076
Fiberplane | Rust Engineer, Frontend Engineer, Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane ( https://fiberplane.dev ), we're r…
-
comment
Comment #27035516
Fiberplane | Rust Engineer & Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane ( https://fiberplane.dev ), we're redefining the futu…
-
comment
Comment #26632357
visx is great! It hides a lot of D3 complexity and provides a very composable React API. The D3 API are still there if and when you need them.
-
comment
Comment #26539998
Here's the actual course's link with lecture materials and labs: http://nil.csail.mit.edu/6.824/2020/schedule.html
-
comment
Comment #26411591
Oh yeah, I can totally relate to the Send-Sync-Unpin massaging, plus 'static bound for me. It's so weird that individually each of them kinda makes sense, but often you need to com…
-
comment
Comment #26410488
Thanks for the suggestion. I didn't think of (1), although it's a pity that it's not as ergonomic as async fn. I kinda feel like there's this false dichotomy here: either hide and …
-
comment
Comment #26409023
I think Rust is also able to hide certain things. Without async things are fine: type Handler = fn(Request ) -> Result , Error>; let mut map: HashMap = HashMap::new(); map.insert("…
- comment
-
comment
Comment #26407524
I like to joke that the best way to encounter the ugliest parts of Rust is to implement an HTTP router. Hours and days of boxing and pinning, Futures transformations, no async fn i…
-
comment
Comment #26102372
> I recommend this blog post: https://nick.groenen.me/posts/rust-error-handling/ This blog post is good indeed. The discussion on /r/rust linked at the end of the post is also wort…
-
comment
Comment #26102226
One thing that is useful to keep in mind when considering boxed errors or error-like objects, e.g. anyhow::Error, is that they famously do not implement std::error::Error trait [1]…
-
comment
Comment #22667795
Is remote limited to the US only or Europe is also fine?
-
comment
Comment #20420127
https://interpreterbook.com/ is a great book to get started.