3 ms·
> Lastly, I was surprised to observe that the Rust/WebAssembly version of the engine as currently shipped in HTTPS Everywhere seems to be slower at both initial
by londons_explore 6y ago
> Lastly, I was surprised to observe that the Rust/WebAssembly version of the engine as currently shipped in HTTPS Everywhere seems to be slower at both initialization and operating than the previous JavaScript implementation. This seems to contradict the previous claims when this was first released.
I see this all too often... Some bit of code is slow, so a project is started to rewrite it more efficiently. Along the way, a bit of scope creep happens, and the final result is slower than the original. Since so much effort has been invested into it, it gets deployed anyway.
- BiteCode_dev 6y agoI see that in the Python and JS world sometimes. The fact is, most scripting languages are written using a compiled one, often C, under the hood. And those implementations have been optimized for decades. A lot of hot loops are such because of complex sorting, filtering, and so on, and those are quite hard to do right. Hence, it's possible to write a way slower implementation using C manually than using the automatic way in Python or JS, not to mention the later has a very good JIT. If you add the fact some code may use crazy fast libs (like numpy in Python), then you may end up in a situtation where you have to really know what you are doing to implement a faster version. However, somebody knowing what they are doing would measure and find the bottle neck first before talking of a rewrite, and suggest it only if it's worth it. Which it can be, of course. Mercurial, Dropbox and Youtube are all good stories about it. But the junior thats been tasked to improve the UX is probably not the best to advice you on the matter.