Building and rebuilding a work environment is a kind of yak shaving, and after a certain point I have to say Enough and get on with actual work.
But, yes, if someone is doing anything at the systems level for the first time, the blog posts are culturally geared toward Linux and anything else would be a kind of friction.
Now the question is "What to work on?" and
"Should I just be learning or should I be contributing to an existing project?"
Here's fifteen hours of live coding TCP in Rust youtube.com/watch?v=bzja9fQWzdA from Jon Gjengset (who is clearly a lot more confident in a top down interface based approach than I am).
I suppose a good first networking project would be to rebuild netcat in rust.
I'm also looking at github.com/uutils/coreutils which is remaking BusyBox in rust. There's lots of interaction with the file system there.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Building and rebuilding a work environment is a kind of yak shaving, and after a certain point I have to say Enough and get on with actual work.
But, yes, if someone is doing anything at the systems level for the first time, the blog posts are culturally geared toward Linux and anything else would be a kind of friction.
Now the question is "What to work on?" and
"Should I just be learning or should I be contributing to an existing project?"
Here's fifteen hours of live coding TCP in Rust youtube.com/watch?v=bzja9fQWzdA from Jon Gjengset (who is clearly a lot more confident in a top down interface based approach than I am).
I suppose a good first networking project would be to rebuild netcat in rust.
I'm also looking at github.com/uutils/coreutils which is remaking BusyBox in rust. There's lots of interaction with the file system there.