New To Programming, What Language Should I Learn With These Specs?

Content SaAMONT AUINAS OGODCGOGOOOCONOOCKCAONNONUAUAUDO SARANIONED JUUM LIOS, CNO DORAUN TOIS HOIHM

The duality of C++ developers confessing their sins. When the attractive dev with the C logo head admits to memory leaks, it's "awww, you're sweet" territory. But when the sweaty guy in a sweater vest does it? Straight to HR jail. Let's be honest, memory management is like dating - it's all about who's doing the allocating, not what's being allocated. The garbage collector can't save you from workplace discrimination.

Content import math import math as maths

Content 4414 8 Locked. There are disputes about this answer's content being resolved at this time. It is not currently accepting new interactions. 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. 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 a a tool to process HTML establishes a breach between this world and the dread realm of corrupt 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 stithy 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 radiance destroving all enlightenment, HTML tags leaking from your eyeslike 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 it 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 higed no NO NOOOO NO stop the an ales ZALGO IS TONY THE FNY, HE ICON 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. share edit follow flag edited Jun 20 at 9:12 community wiki 7 revs, 5 users 36 bobince

Content Always has been Wait, it's all just a website? N

The bell curve of debugging intelligence. At the bottom left and right, the simple souls with their "just reset it bro" approach—blissfully unaware but sometimes right. Meanwhile, the 34% crowd in the middle is sweating through Root Cause Analysis like it's their religion. They're writing 12-page documents about why the server hiccupped at 2:17 PM last Tuesday. Truth is, both the village idiot and the enlightened sage arrive at the same conclusion: turning it off and on again fixes 90% of problems. The difference? One spent 8 hours documenting the electron flow through the CPU first.