Address Me

Content 4411 Locked. There are disputes about this answer's content being resolved at this time. It is not currently accepting new interactions. V You can't parse XHTML 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. Rege 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. Regx-based HTML parsers are the cancer that is killing StackOverflow it is too late it is too late we cannot be saved the transgression 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 8rrupt entities (like SGML entities, but more corrupt) a mere glimpse of the world of regex 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 Visual Basic only worse he comes he comes do not fight he comes, his unholy radianc destroying all enlightenment, HTML tags leaking from your eyes like liquid pain, the song of rgular expression parsing-will extinquish the voices of mortal man from the sphere I can see it can you see. if it is beautiful the final snuffing of the lies of Man ALL IS LOST ALL IS LOST the pony he comes he comes he comes the ichor permeates all MY FACE MY FACE h god no NO NOOOO NO stop the an"des are not reaT zALGO IS TONY THE PONY HE COMES Have you tried using an XML parser instead? Moderator's Note This post is locked to prevent inappropriate edits to its content. The post looks exactly as it is supposed to look - there are no problems with its content. Please do not flag it for our attention. ProdrammerH

DARLING, the BETRAYAL! Backend passing a note with HTTP status codes instead of a proper error object! The absolute AUDACITY! 🙄 Frontend's face says it all - "You expect me to work with THIS?!" Backend just casually tossing over raw status codes (200 for success, 500 for server error) when everyone knows frontend deserves a PROPERLY FORMATTED JSON error with actual useful information! The DRAMA of cross-team communication! It's like getting a breakup text that just says "relationship = null" - GIVE ME DETAILS, PEOPLE!

Content 0 "g" 0 Li So, if 0 "O" 1 00 and 0 IF then surely "g" G true JS true JS That makes sense to me. false

Content Ben Halpern bendhalpern Sometimes when I'm writing Javascript I want to throw up my hands and say "this is bullshit!" but I can never remember what "this" refers to

When JavaScript makes you want to set your computer on fire, just remember Java devs are stuck writing 15 lines of code to print "Hello World" in some corporate basement. Suddenly your undefined is not null errors don't seem so bad. Nothing calms the JavaScript rage like realizing you could be writing enterprise Java instead. Perspective is a beautiful thing.

Content Programming in high school and college: I can write a function to check if a number is a palindrome, a "Dog" class that overrides methods of the "Animal" class, and a dictionary that receives the real name of a superhero as key and returns their secret identity. I suppose that I have enough practice to start the next unicorn that will disrupt a major tech industry. imghip FIVE YEARS LATER, SEARCHING FOR WORK: K "What are all of these arcane symbols? How do I unit test? Who is JSON, and why is the letter 'A' missing in his name?" Imgflig