> 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 knew Russia the best: Estonia, Latvia,…
At the very least Germany could have said no to Nord Stream 1 & 2.
Fiberplane | Rust Engineer, Frontend Engineer, Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane (https://fiberplane.dev), we're redefining the future of collaboration for…
Fiberplane | Rust Engineer & Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane (https://fiberplane.dev), we're redefining the future of collaboration for infrastructure…
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.
Here's the actual course's link with lecture materials and labs: http://nil.csail.mit.edu/6.824/2020/schedule.html
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 combine then and all of a sudden the…
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 be like Java/Go or be as explicit as…
I think Rust is also able to hide certain things. Without async things are fine: type Handler = fn(Request<Body>) -> Result<Response<Body>, Error>; let mut map: HashMap<&str, Handler> = HashMap::new(); map.insert("/",…
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 in traits, closures not being real first…
> 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 worth reading. Another good and light…
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]. This could be a problem if you want…
Is remote limited to the US only or Europe is also fine?
https://interpreterbook.com/ is a great book to get started.
> 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 knew Russia the best: Estonia, Latvia,…
At the very least Germany could have said no to Nord Stream 1 & 2.
Fiberplane | Rust Engineer, Frontend Engineer, Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane (https://fiberplane.dev), we're redefining the future of collaboration for…
Fiberplane | Rust Engineer & Solution Engineer | Amsterdam, The Netherlands | ONSITE or REMOTE (CET +/- 3 hours) At Fiberplane (https://fiberplane.dev), we're redefining the future of collaboration for infrastructure…
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.
Here's the actual course's link with lecture materials and labs: http://nil.csail.mit.edu/6.824/2020/schedule.html
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 combine then and all of a sudden the…
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 be like Java/Go or be as explicit as…
I think Rust is also able to hide certain things. Without async things are fine: type Handler = fn(Request<Body>) -> Result<Response<Body>, Error>; let mut map: HashMap<&str, Handler> = HashMap::new(); map.insert("/",…
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 in traits, closures not being real first…
> 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 worth reading. Another good and light…
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]. This could be a problem if you want…
Is remote limited to the US only or Europe is also fine?
https://interpreterbook.com/ is a great book to get started.