15

Why do websites have to make their html so fucking hard and complicated to read with something like beautifulsoup. Like I just want to scrape your data. Fuck your embedded iframes and div lists. Why must you do this I JUST WANT YOUR DATA

Comments
  • 7
    Maybe, to prevent people from scrapping their data ? Maybe, to prevent people from scrapping their data ?
  • 12
    No soup for you
  • 0
    @NoToJavaScript if it's online then I should be able to scrape it
  • 5
    Because most web devs are too stupid for HTML. Sad but true.
  • 4
    @ph0sgene Yes

    But nobody said it'd have to be easy
  • 0
    div, divs everywhere!
  • 8
    @shoop It isn't bulky and weird. There are three different languages because they cover different objectives.

    HMTL - what the content is.
    CSS - how the content looks.
    JS - how the content behaves (if applicable).

    The hodgepodge comes because there are too many incompetent web devs who don't grasp this very basic concept and abuse each of these three to do the jobs of the other two.

    If anything, a "modern" standard would be worse, not better.
  • 0
    @shoop wow. I'm telling this to other web devs all the time. They deny it and keep saying the tech is perfectly fine.
  • 1
    @shoop HTML had machine learning in the 90s. Way ahead of its time. Everyone else is just now catching up...
  • 2
    @Fast-Nop Well, other UI techs have different languages to cover different objectives, too. Xaml and c# for example.
    Unlike HTML, CSS and JS they are desinged for building UI/Apps.
    HTML is horribly misused for UI and JS is just allowing HTML to be dynamic and have some logic and databinding.
    CSS is making HTML capable of styling which other UI markup techs have built in by themselves. And CSS is practically shit without LESS or SASS. Also, JS is arguably lacking, too. Otherwise TS would not be so popular.

    It's just a huge mess, compared to anything else.
  • 4
    @Lensflare HTML is of course not designed for UI. See above, that's how it works. Also, you don't need CSS frameworks because you don't need much CSS anyway.

    More than 32k of CSS (minified, not gzipped) for a whole website is usually a sign that the web dev has no clue of what he's doing. Typical root cause is failure to understand how HTML and CSS work, writing presentational markup and fudging that together with presentational CSS.
  • 5
    @Fast-Nop That saves room for 5Megabytes of ads and tracking scripts.
  • 0
    @shoop It would not make it cleaner, on the contrary, because then the difference in the objectives would be completely lost. Easier for sure - easier to do even worse garbage than today, and more difficult to do something good.

    Also, accessibility would go right out of the window in the resulting hodgepodge. The only ones who would benefit are people who shouldn't have a place in web dev anyway.
  • 1
    Let’s scrap it all and start again, a webreformation... webformation... webform... shit
  • 2
    Grep and sed, grep and sed, my friend
  • 0
    @ph0sgene By that logic you should be able to scrape every goddamn Facebook, Instagram, Twitter, google account etc even if it'd required authentication.
Add Comment