I started doing the free version of the course a few days ago - the lessons are excellent but what is even better are the homework tasks which allows me to run my tests locally!
It's sometimes easy to just listen and understand, but be unable to write the code myself - having this coding homework task has really helped me solidify this new knowledge.
Can you share what hardware resources are expected for the assignments? Are the students just doing this on their personal computers or are they given cluster access?
Just curious what your thought are regarding this (https://zaplib.com/docs/blog_post_mortem.html) if you have seen it. Does implementing a physics engine in Rust and complied in wasm provide you guys with quite a big performance boost? Asking because I've considered doing so for my team, but have reservations about the performance increase.
We’re not implementing in Rust but taking an existing piece of middleware (Bullet) and using it. Performance wise it’d be an apples to oranges comparison but our general understanding from benchmarks, our own personal experiments and blogs like the one you posted there is not to expect miracles but more consistency and less footguns (e.g. megamorphic behaviour).
I would say there is hope when SIMD is supported across major browsers if your workload will make use of it. Just waiting on Safari. And there might well be more performance to eek out of the JIT compilation.
I have the EXACT same problem. Constantly refreshing and refreshing insta, reddit, hackernews, etc etc. Shameless plug, I built this to try to curb my addiction -> https://github.com/neriymus/Fetcher, maybe it'll help someone else.
I started working on porting an internal viz tool in the company I work at from JS to Rust/wasm 2 weeks ago. Thanks for writing this post mortem up, has made me think twice whether its worth the work.
I looked at the possibilities of porting parts of my 2D canvas library's code base over to Wasm (using either AssemblyScript or Rust) last winter. My thinking was that maybe some of the more intense calculation stuff - animating text along a path, particle calculations, complex filters, etc - could be delivered faster if they happened in Wasm.
I didn't take the idea forward because it would've been a heck of a lot of (unpaid) work requiring some fundamental rethinking of the library's architecture, together with learning Rust/AssemblyScript alongside Wasm best practices, etc.
But the main thing that held me back were the bad memories I had of all the work I did when I learned about web workers and attempted something similar a few years ago. That work added a lot of complexity to maintaining/using the library, but in the end failed to deliver the speed increases I was hoping for. The best work I did in 2020 was removing the web workers and their associated complexity from the code base and instead concentrating my efforts on finding speed gains in Javascript.
I love the idea of Wasm, and have had some success in getting code that exports to Wasm - for instance, MediaPipe's Selfie Segmentation ML model - to play nicely with the library[1]. But if I ever want a really fast, Wasm-enabled 2D canvas library I think the best approach would be to build the entire thing in Rust and just have a lightweight JS API to handle the DOM and user interactions.
I was addicted to refreshing websites - twitter, reddit, etc etc. So I wrote an extension to essentially pull new posts for me every 10 minutes - its actually saved so much of my time.
Good QAs are so important. There are so many bugs that would have never been found by us. In the past 3 weeks, both our QAs have been off, and the inbox list of problems have grounded to almost zero! Not because we are writing more-than-usual-amazing code, but because no one managed to find them.
I'm trying to solve my addiction of refreshing tabs constantly to get updates from my social media profiles, by building something that does it for me instead
Think rss, but for my personal feeds.
Still mvp, lotsa bugs, but if anyone has similar problems -> https://fetcher.page
It's sometimes easy to just listen and understand, but be unable to write the code myself - having this coding homework task has really helped me solidify this new knowledge.
10/10 would recommend
reply