Unable to load image

:marscientist: Scientist thinks running a WASM Python interpreter in the bowser :marseyhacker: is a good idea; Science proves that the idea is bloated :marseyobesescale::marseyobesescale:

https://drtransmisia.github.io/mistletoe

Poll

write down there the time it takes to load the shit (after the second load, to allow it to build up the cache)

:#marscientist::#marscientist::#marscientist:

:#marseycapyhacker::#marseycapyhacker::#marseycapyhacker:

21
Jump in the discussion.

No email address required.

Thanks to @Aevann for upvoting every post on /h/slackernews manually and in good faith

:#marseycapychad2::#marseykneel:

Jump in the discussion.

No email address required.

2010 Intel i3 that has never been cleaned running in a very hot room with no ac (cpu fan is almost always on 100% during the summer)

Chromium on Windows 10 with VBS enabled

>I took 48433.19999998808ms to load the fricking Python runtime 'n related shit!

:#marseyburn:

Jump in the discussion.

No email address required.

:#marseydicklet:

Jump in the discussion.

No email address required.

>I took 9700ms to load the fricking Python runtime 'n related shit!

You think CPU time just grows on trees? I actually use my Intel Core 2 Duo to it's fullest potential by mining monero in the background

Jump in the discussion.

No email address required.

Don't worry it's not gonna be used on the site :marseyplaty:

Jump in the discussion.

No email address required.

I took 2212.7999999988824ms to load the fricking Python runtime 'n related shit!

second time:

I took 1018.7000000011176ms to load the fricking Python runtime 'n related shit!

Jump in the discussion.

No email address required.

2087ms, was ~3500ms the first time

Jump in the discussion.

No email address required.

I took 8822ms to load the fricking Python runtime 'n related shit!

I took 4347ms to load the fricking Python runtime 'n related shit!

please no

Jump in the discussion.

No email address required.

took 3488.399999976158ms to load the fricking Python runtime 'n related shit!

took 2004.6000000238419ms to load the fricking Python runtime 'n related shit!

core i7 2600k

Jump in the discussion.

No email address required.

I took 1700ms to load the fricking Python runtime 'n related shit!

:#marseypop2: :#marseypop2: :#marseypop2:

Jump in the discussion.

No email address required.

3secs. Faster than one of these js heavy news websites. Looks ready for primetime to me.

Jump in the discussion.

No email address required.

I took 1696.4000000059605ms to load the fricking Python runtime 'n related shit!

Jump in the discussion.

No email address required.

>I took 1274.300000011921ms to load the fricking Python runtime 'n related shit!

Jump in the discussion.

No email address required.

:#marseycupid:

Snapshots:

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.