Currently meeseeks_html5ever works asynchronously, calling the NIF then receiving a response, but since the minimum supported version of Erlang/OTP is now 20 we can start using dirty schedulers instead.
This should simplify the NIF's implementation since it can work synchronously and hopefully get rid of a little performance overhead.
mischov
commented
5 years ago
Currently
meeseeks_html5everworks asynchronously, calling the NIF then receiving a response, but since the minimum supported version of Erlang/OTP is now 20 we can start using dirty schedulers instead.This should simplify the NIF's implementation since it can work synchronously and hopefully get rid of a little performance overhead.