nice, I didn't know Semaphores at all but they seem useful for the future. Can maybe someone explains to me what a possible reason is to limit this MP3-Import example? I think I didn't get the point. Is it better for writing the files on the hard disc (on import on the server side)? or only to keep the order of files (song 01, song 02, song 03, ...) so that the loading indicator doesn't jump?
Just use rx over promise, the async/await/promise is a convenient but bad standard, the part you can't cancel/multi-value/teardown properly makes rx essential handling slightly complex structures. Also define a method call iife call, it is far easier to manage and refactor over extra quote pairs.
Here's the slide deck for the talk + links!
speakerdeck.com/nybblr/async-patterns-to-scale-your-multicore-javascript-dot-dot-dot-elegantly
Amazing talk. Really will implement some ideas from this on my pet projects.
really helpful and impressive. thanks for sharing
nice, I didn't know Semaphores at all but they seem useful for the future. Can maybe someone explains to me what a possible reason is to limit this MP3-Import example? I think I didn't get the point. Is it better for writing the files on the hard disc (on import on the server side)? or only to keep the order of files (song 01, song 02, song 03, ...) so that the loading indicator doesn't jump?
paaddy_ The idea is to not crash the browser if the concurrent file sizes are too large. ie The user attempts to upload 100 files all at once.
would you mind sharing the slide?
Thanks for this nice talk!
Very nice talk, thanks a lot.
4:25 Every time I try to say parallelism.
really nice one
Just use rx over promise, the async/await/promise is a convenient but bad standard, the part you can't cancel/multi-value/teardown properly makes rx essential handling slightly complex structures.
Also define a method call iife call, it is far easier to manage and refactor over extra quote pairs.