Main

processing priority

3

site type

4 (micro-blogging service: Tumblr, Twitter etc. (millions of short posts instead of longer articles))

review version

11

html import

20 (imported)

Events

first seen date

2024-08-13 00:08:31

expired found date

-

created at

2024-08-13 00:08:31

updated at

2025-04-21 22:33:09

Domain name statistics

length

29

crc

51234

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

11900311 (tumblr.com)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

0

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

88419

mp size raw text

23356

mp inner links count

15

mp inner links status

9 (spam / low value domains)

Open Graph

title

javascript.reverse()

description

Tom Schuster @evilpies evilpies AT gmail DOT com

image

site name

Tumblr

author

updated

2026-01-31 10:38:56

raw text

javascript.reverse() Home Mobile RSS javascript.reverse() Text The pitfalls of self-hosting JavaScript Recently the SpiderMonkey team has been looking into improving ECMAScript 6 and real world performance as part of the QuantumFlow project. While working on this we realized that self-hosting functions can have significant downsides, especially with bad type information. Apparently even the v8 team is moving away from self-hosting to writing more functions in hand written macro assembler code. Here is a list of things I can remember from the top of my head: Self-hosted functions that always call out to C++ (native) functions that can not be inlined in IonMonkey are probably a bad idea. Self-hosted functions often have very bad type-information, because they are called from a lot of different frameworks and user code etc. This means we need to absolutely be able to inline that function. (e.g. bug 1364854 about Object.assign or bug 1366372 about Array.from) If a...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

230

index version

2025123101

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

18015

text words

3862

text unique words

1159

text lines

338

text sentences

218

text paragraphs

61

text words per sentence

17

text matched phrases

3

text matched dictionaries

7

RSS

rss status

32 (unknown)

rss found date

2024-08-22 06:11:40

rss size orig

45208

rss items

14

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

30 (processing completed, results pushed to table crawler_sitemaps.ext_domain_sitemap_lists)

sitemap review version

2

sitemap urls count

15

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2024-08-15 10:13:40

sitemap process date

2024-08-15 10:13:42

sitemap first import date

-

sitemap last import date

-