Its
Its

Its

But
But

But

Its Too Late
Its Too Late

Its Too Late

I Hate That
I Hate That

I Hate That

falling asleep
 falling asleep

falling asleep

candy bowl
 candy bowl

candy bowl

weights
 weights

weights

joyce
 joyce

joyce

late
 late

late

longing
longing

longing

🔥 | Latest

Dumb, Target, and Tumblr: metatf: I know, the fact that they are on the water like that it’s dumb, but I noticed it too late :’|. Speedrawing.
Dumb, Target, and Tumblr: metatf:
I know, the fact that they are on the water like that it’s dumb, but I noticed it too late :’|.
Speedrawing.

metatf: I know, the fact that they are on the water like that it’s dumb, but I noticed it too late :’|. Speedrawing.

Beautiful, Community, and God: 21 Answers votes oldest newest You can't parse [X]HTML with regex. Because HTML can't be parsed by regex. Regex is not a tool that can be used to correctly parse HTML. As I have answered in HTML-and-regex questions here so many times before, the use of regex will not allow you to consume HTML. Regular expressions are a tool that is insufficiently sophisticated to understand the constructs employed by HTML. HTML is not a regular language and hence cannot be parsed by regular expressions. Regex queries are not equipped to break down HTML into its meaningful parts. so many times but it is not getting to me. Even enhanced irregular regular expressions as used by Perl are not up to the task of parsing HTML. You will never make me crack. HTML is a language of sufficient complexity that it cannot be parsed by regular expressions. Even Jon Skeet cannot parse HTML using regular expressions. Every time you attempt to parse HTML with regular expressions, the unholy child weeps the blood of virgins, and Russian hackers pwn your webapp. Parsing HTML with regex summons tainted souls into the realm of the living. HTML and regex go together like love, marriage, and ritual infanticide. The <center> cannot hold it is too late. The force of regex and HTML together in the same conceptual space will destroy your mind like so much watery putty. If you parse HTML with regex you are giving in to Them and their blasphemous ways which doom us all to inhuman toil for the One whose Name cannot be expressed in the Basic Multilingual Plane, he comes. HTML-plus-regexp will liquify the nerves of the sentient whilst you observe, your psyche withering in the onslaught of horror. Regex-based HTML parsers are the cancer that is killing StackOverflow it is too late it is too late we cannot be saved the trangession of a child ensures regex will consume all living tissue (except for HTML which it cannot, as previously prophesied) dear lord help us how can anyone survive this scourge using regex to parse HTML has doomed humanity to an eternity of dread torture and security holes using regex as a tool to process HTML establishes a breach between this world and the dread realm of čorrupt entities (like SGML entities, but more corrupt) a mere glimpse of the world of reg ex parsers for HTML will instantly transport a programmer's consciousness into a world of ceaseless screaming, he comes-the pestilent slithy regex-infection will devour your HTML parser, application and existence for all time like Vişual Basic only worse he comes he comes do not fight he comes, his uņholy radiance destroping all enlightenment, HTML tags leaking frọm your eyesiike liquid pain, the song of regular expression parsing-will extinguish the voices of mortal man from the sphere I can see it can you see t it is beautiful the f inal snuf fing of the lies of Man ALL ĮS LOSTALL IS LOST the pony he comes he comes hejcemes the ichor permeates al MY FACEFACEh god no NO NOOoo Ne stop the an ges aře not reâj ZALGO IS TON THË PONY, HECOMES 1811 Have you tried using an XML parser instead? link edit flag edited Nov 14 at 0:18 community wiki bobince regex and html
Beautiful, Community, and God: 21 Answers
 votes
 oldest
 newest
 You can't parse [X]HTML with regex. Because HTML can't be parsed by regex. Regex is not a tool that
 can be used to correctly parse HTML. As I have answered in HTML-and-regex questions here so many
 times before, the use of regex will not allow you to consume HTML. Regular expressions are a tool that is
 insufficiently sophisticated to understand the constructs employed by HTML. HTML is not a regular
 language and hence cannot be parsed by regular expressions. Regex queries are not equipped to break
 down HTML into its meaningful parts. so many times but it is not getting to me. Even enhanced irregular
 regular expressions as used by Perl are not up to the task of parsing HTML. You will never make me
 crack. HTML is a language of sufficient complexity that it cannot be parsed by regular expressions. Even
 Jon Skeet cannot parse HTML using regular expressions. Every time you attempt to parse HTML with
 regular expressions, the unholy child weeps the blood of virgins, and Russian hackers pwn your webapp.
 Parsing HTML with regex summons tainted souls into the realm of the living. HTML and regex go together
 like love, marriage, and ritual infanticide. The <center> cannot hold it is too late. The force of regex and
 HTML together in the same conceptual space will destroy your mind like so much watery putty. If you
 parse HTML with regex you are giving in to Them and their blasphemous ways which doom us all to
 inhuman toil for the One whose Name cannot be expressed in the Basic Multilingual Plane, he comes.
 HTML-plus-regexp will liquify the nerves of the sentient whilst you observe, your psyche withering in the
 onslaught of horror. Regex-based HTML parsers are the cancer that is killing StackOverflow it is too late
 it is too late we cannot be saved the trangession of a child ensures regex will consume all living tissue
 (except for HTML which it cannot, as previously prophesied) dear lord help us how can anyone survive
 this scourge using regex to parse HTML has doomed humanity to an eternity of dread torture and
 security holes using regex as a tool to process HTML establishes a breach between this world and the
 dread realm of čorrupt entities (like SGML entities, but more corrupt) a mere glimpse of the world of reg
 ex parsers for HTML will instantly transport a programmer's consciousness into a world of ceaseless
 screaming, he comes-the pestilent slithy regex-infection will devour your HTML parser, application and
 existence for all time like Vişual Basic only worse he comes he comes do not fight he comes, his uņholy
 radiance destroping all enlightenment, HTML tags leaking frọm your eyesiike liquid pain, the song of
 regular expression parsing-will extinguish the voices of mortal man from the sphere I can see it can you
 see t it is beautiful the f inal snuf fing of the lies of Man ALL ĮS LOSTALL IS LOST the pony he
 comes he comes hejcemes the ichor permeates al MY FACEFACEh god no NO NOOoo Ne
 stop the an ges aře not reâj ZALGO IS TON THË PONY, HECOMES
 1811
 Have you tried using an XML parser instead?
 link edit flag
 edited Nov 14 at 0:18
 community wiki
 bobince
regex and html

regex and html

Comfortable, Deer, and Hello: hello-kitty-senpai There is a specific and terrifying difference between "never were" monsters and "are not anymore" monsters The thing that was not a deer implies a creature which mimics a deer but imperfectly and the details which are wrong are what makes it terrifying The thing that was not a deer anymore" on the other hand implies a thing that USED to be a deer before it was somehow mutated, possessed, parasitically controlled or reanimated improperly and what makes THAT terrifying is the details that are still right and recognizable poking out of all the wrong and horrible malformations hello-kitty-senpai hey I totally forgot the 3rd type, which is "Is Not Anymore And Maybe Never Was" monsters "The thing which was no longer a deer and maybe never was" implies a creature that, at first glance, completely appears to be a deer, but over time degrades very slowly until you realize (probably too late) that it is not a deer anymore, and had you seen it in this state first, you wouldn't have recognized it as a deer at all, and there's a decent chance that it was never actually a deer to begin with but only a very good mimic, and what makes this one scary is the slow change from everything being right to everything being wrong, happening slowly enough that you don't even notice it until its too late, as welll as the fact that something now so clearly not a deer could have fooled you to begin with katekarl And the fourth type, which is, "I dunno, but it sure ain't a deer. Which implies complete confusion about what the creature could be, to the point that even a person as comfortable in this world as someone who would use the word ain't unironically is uncertain, which should horrify you to the deepest depths of your soul. goblinfruit Don't forget the fifth type, the that's a weird looking dog," implying that while the creature has an appearance that slips beyond our ken, that raises the tiny hairs at the back of our necks and limbs, that makes our lungs rattle and hearts constrict,... personality-wise, it is a good boy Source: hello-kitty-senpai 52,450 notes #anymore #never #were #notNever were, not anymore - #Anymore #notNever
Comfortable, Deer, and Hello: hello-kitty-senpai
 There is a specific and terrifying difference between "never were" monsters and
 "are not anymore" monsters
 The thing that was not a deer implies a creature which mimics a deer but
 imperfectly and the details which are wrong are what makes it terrifying
 The thing that was not a deer anymore" on the other hand implies a thing that
 USED to be a deer before it was somehow mutated, possessed, parasitically
 controlled or reanimated improperly and what makes THAT terrifying is the
 details that are still right and recognizable poking out of all the wrong and
 horrible malformations
 hello-kitty-senpai
 hey I totally
 forgot the 3rd type, which is "Is Not Anymore And
 Maybe Never Was" monsters
 "The thing which was no longer a deer and maybe never was" implies a creature
 that, at first glance, completely appears to be a deer, but over time degrades
 very slowly until you realize (probably too late) that it is not a deer anymore, and
 had you seen it in this state first, you wouldn't have recognized it as a deer at all,
 and there's a decent chance that it was never actually a deer to begin with but
 only a very good mimic, and what makes this one scary is the slow change from
 everything being right to everything being wrong, happening slowly enough that
 you don't even notice it until its too late, as welll as the fact that something now
 so clearly not a deer could have fooled you to begin with
 katekarl
 And the fourth type, which is, "I dunno, but it sure ain't a deer. Which implies
 complete confusion about what the creature could be, to the point that even a
 person as comfortable in this world as someone who would use the word ain't
 unironically is uncertain, which should horrify you to the deepest depths of your
 soul.
 goblinfruit
 Don't forget the fifth type, the that's a weird looking dog," implying that while the
 creature has an appearance that slips beyond our ken, that raises the tiny hairs
 at the back of our necks and limbs, that makes our lungs rattle and hearts
 constrict,... personality-wise, it is a good boy
 Source: hello-kitty-senpai
 52,450 notes
#anymore #never #were #notNever were, not anymore - #Anymore #notNever

#anymore #never #were #notNever were, not anymore - #Anymore #notNever