why do redditors get mad when you parse html with regex?

Wrong tool for the job.

Because they think you're always supposed to write generic code that can be reused anywhere, instead of just doing the specific thing you want to do

I've seen this exact same pepe image on /adv/, /o/, and on /g/ twice now. and that's just in a span of two weeks.

>>105846470
repeat after me:
- this is not the image i have seen before

>>105846439
What's the correct tool, anon?

>>105846510
a 20mb html parsing library

I still don't understand why you're not supposed to make up your own tags
a) i can't keep track of all the shit they introduced since "semantic html"
b) browsers have different defaults and styles for official tags so you're fighting an uphill battle
c) style and content are supposed to be separate, behavior should be too

>>105846510
a giant if-else statement

>>105846561
I've never heard this advice before, but I imagine the reasoning is that if the tag is ever used in the future, it will retroactively alter the behavior of your website

>>105846462
many such cases

>>105846510
Any actual HTML parsing library. It doesn't need to be a full featured one that would weigh several megabytes as the other anon suggested.

The problem with using regular expressions for HTML is that HTML is not a regular language, it's context-free. Regular expressions cannot, for instance, tell where closing tags are meant to apply to, nor if close tags are evenly matched. Your ability to parse within a given HTML document is quite limited with regular expressions.

>>105846510
beautifulsoup

>>105846510
something that takes more processing power because... because you just le have to, okay?????

>>105846611
>bro trust me, you HAVE to import an entire html parsing library to locate the text within <span class="nigger"></span> and nothing else
>you cannot just regex match that exact text because... well you just can't, okay?

>>105846425 (OP)
Because the same HTML formatted differently will fail to get selected
I’ve started to format some of my basic no-build-step sites with Prettier and I’m thinking I could get away with it for common elements that need search-and-replace because the form of the HTML is locked in

>>105846715
if a website changed something that causes your regex to break, then that is good because it means you can go and verify that the information is still correct. your parsing library continuing to work would not alert you to go and make sure it's actually getting the right data. who knows, maybe the website developer wanted to switch attribute values without changing the names

>>105846425 (OP)
because regex is retarded and if I ever have to work on a codebase thats reliant on regex I will kill myself and the person who wrote it

redditors are the ones using regex though

>>105846510
a web browser, it will parse html into a beautiful web page as a feast for your eyes

>>105846425 (OP)
You can do some HTML queries with regex.

>>105846643
There're various powershell packages that include html parsers so no python needed

>>105846611
the kind of subexpression that I'm looking for is context-free THOUGH

It's a dangerous way to do it, easy to introduce unexpected bugs. Since HTML is a tree structure you should be traversing it as such not randomly grabbing strings.

>>105846510
AI, of course

>2025
>websites literally transmit raw html rather than compiling it into some kind of bytecode language
YOU CAN'T MAKE THIS SHIT UP

>>105847766
>Source: my butthole (peer reviewed)

>>105848797
It can be compressed with gzip doe

>>105849090
Bytecode isn't a compression scheme, newfren.