Please Stop The Framework Carousel

Content I HAVE NO IDEA WHO JSON IS AND AT THIS POINT I'M AFRAID TO ASK

When your CS professor says "implement a sorting algorithm" but you've got an OpenAI API key and zero shame. This dev just created the world's most expensive sorting function by literally asking GPT-4 to be a sorting algorithm! Sure, it works—but imagine burning through API credits to sort [42, 3, 99, 7, 13] when a simple Array.sort() would do the trick. The true innovation here is maximizing both latency AND cost while solving a problem that was figured out decades ago. Congratulations, you've invented O(API) complexity—where the limiting factor is your credit card limit!

Content The Proud Parent The Linker REPENT TOMER - Half your manager, half your senior - Designed the codebase - Will always answer your question, but only after a 5 minute on the motivations of a now rebuilt module from years ago - "I remember when we had to do that process in the AWS console with just a trackpad, uphill both ways" - Tough during code review, but genuinely happy to see you ship new features to the system The Job Security Maximizer - Always sends you a link when you ask a question, sometimes without any other words - "Look at this" - Thinks you don't know standard documentation exists - Posts medium articles in the main channel, doesn't read them - Never reviews code - First stack overflow result The Big Chiller - "Ohh, that? Sorry I totally forgot all - Been around for years, knows the entire about the code I wrote a month ago" codebase - Tells you to ask someone else for the - Friends with the CTO simplest question - Shows you the exact line of code that - Has dozens of pages of private notes, causes your bug within 5 minutes READMEs all read "initial commit" - They last shipped a commit a couple - "Have you thought about adding an months ago, you think abstracter to this abstraction? With that - Always approves your PRs we can decouple the coupler from the universe" 10 i0

Content 34 Answers Sorted by: Highest score (default) 2 Next 4409 Locked. There are disputes about this answer's content being resolved at this time. It is not currently accepting new interactions. V 9 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 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 crrupt entities (like SGML entities, but more corrupt) a mere glimpse of the world of regex parsers for HTML will ins tantly 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 radianc destroying all enlightenment, HTML tags leaking from your eyes like 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 if it is beautiful the final snuffing of the lies of Man ALL IS LOST ALL IS LOST the pony he comes he comes be comes the icher permeates all MY FACE MY FACE chiged no NO NO000 NO stop the angles pre not reai ZALGO IS TONY THE PNY, HE COMES Have you tried using an XML parser instead?

The AUDACITY of JavaScript developers to create an entire UNIVERSE just to print numbers 0-15! Look at that top code—creating an array, filling it, mapping it, and THEN forEach-ing it?! HONEY, WHY?! Meanwhile, the humble for loop at the bottom is sitting there like "I've been doing this since 1995, darling." This is the programming equivalent of using a rocket launcher to kill a spider. I can't even! 💅

The function loops through ALL USERS to find one with matching credentials instead of using a proper query. The comment is the chef's kiss: "This only works because there are not many users." It's like saying "my car doesn't need brakes because I don't drive fast." Bonus security nightmare: they're storing password hashes but comparing them directly instead of hashing the input password first. This authentication is basically a time bomb wrapped in spaghetti code!