I would look into queues and a background task (with a concurrency of around 8 to leave enough server resources for other features) for heavy tasks like video processing. You can also make an API that reports progress to an user.
All your arguments can be applied when comparing ts to js. You can just use the succinct and readable js. Why waste time dealing with this type is implicitly any?
I would look into queues and a background task (with a concurrency of around 8 to leave enough server resources for other features) for heavy tasks like video processing. You can also make an API that reports progress to an user.
queued > generating (10%).. > done etc.
Woah. That's quite interesting. I didn't know that.
Yea it's like when we write
Some(2). It's not a function call but a variant of theOptionenum.Do you mean RAII guards
https://rust-unofficial.github.io/patterns/patterns/behavioural/RAII.html
Or match guards?
https://doc.rust-lang.org/rust-by-example/flow_control/match/guard.html
😂 Ikr!
Yeah I don't mean just terse functional idioms. Any programming technique that blew your mind the first time you came across it would qualify.
All your arguments can be applied when comparing ts to js. You can just use the succinct and readable js. Why waste time dealing with
this type is implicitly any?Get things done with js and chill.