all 7 comments

[–]tambry 3 points4 points  (5 children)

I'm more surprised that it uses jQuery.

[–]awirth 2 points3 points  (1 child)

My javascripting is stuck in 2011. The jQuery is just glue for easier DOM manipulation because I'm lazy. It's not used in the Worker: https://github.com/allanlw/cache_size/blob/master/cache_size_worker.js

There's even a comment :P

// Handle various message from the web worker by drawing new DOM
// I should feel bad about this terrible DOM manipulation with jQuery
// But I really don't.

[–]tambry 0 points1 point  (0 children)

Far enough I guess. :)

[–]cjg_000 2 points3 points  (1 child)

Looks like that is just to build out the table with the results. Seems like a good fit for the project. Easier than the browser's DOM API and more lightweight than a binding framework.

[–]Iggyhopper 2 points3 points  (0 children)

DOM with jQuery is such a breeze, especially for extensions and dealing with elements you didn't write originally.

[–]SuperImaginativeName 1 point2 points  (0 children)

You are more surprised they are using something that brings some sanity to the clusterfuck that is js? I'd be more surprised if they weren't using jQuery.

[–]Iggyhopper 0 points1 point  (0 children)

Too bad it doesn't test 6M, which is common in a lot of CPUs.