24
Fast-Nop
148d

Bootcrap. Just looked at their main page, and it's a whopping 75k of markup plus 294k of CSS (W-T-F?!), and 224k of JS. All of that shit for a page that shouldn't be more than 10k of markup, 16k of CSS, and that has no reason to even use JS at all.

<a class="d-flex flex-column flex-lg-row justify-content-center align-items-center mb-4 text-dark lh-sm text-decoration-none

Yeah, that crap is supposed to be "easier" to write. That's what you get for totally failing to understand how HTML/CSS even work, clinging to late 1990s practices, and ditching decades of progress since then.

Although the Bootcrap folks do manage to write valid HTML. As low as that sounds, but that counts already as an exceptional skill in the notoriously low-skilled frontend "dev" world that is all about making shitty websites.

Oh, and the rest like Failwind and Bulimia aren't any better. They already fail at delivering valid HTML on their websites.

Comments
  • 4
    It’s a race to be the best overengineer
  • 5
    @TeachMeCode Nah, overengineering has engineering as prerequisite to begin with (d'uh). It takes skill to overengineer.
  • 2
    @Fast-Nop good point 😁
  • 3
    Using bootstrap in 2023 is like buying fancy bottled water when ur tap water is perfectly safe to drink, but also the fancy bottled water actually tastes a lot worse.
  • 5
    I had a colleague who had five years of frontend development under his belt. He used bootstrap intensively.
    He didn’t know that CSS flexbox and grid existed
  • 2
    Frameworks in general seem to use differnt ways of orgnizing and thinking about things than me. CSS frameworks are no difference and therefore they obviously all suck.

    But don't forget that CSS frameworks especially aren't actually made for devs. They are made for human WYSIWG website editors - code monkeys tasked to transfer a design into HTML and CSS. They don't start making templates but copy some existing stuff and modify it until it looks like the design. For the add/remove-until-it-fits workflow, even the absurdity of Tailwind is probably fine.

    What gives us PTSD is a great help for the monkeys out there. And they (luckily) are the majority dealing with HTML and CSS - not us.
  • 0
    @Oktokolo I think it does impact people when these monkeys don't understand how HTML and CSS work. Normally, it "only" bloats up the site, especially bad on mobile connections.

    However, it's a lot worse for impaired people who rely on assistive technology. If the monkeys only fudge around until their mess looks right on their screen, then screenreaders won't make sense of a document structure that just isn't there to begin with.

    Shit like garbled heading hierarchies, links for in-page actions that should have been buttons, or even divs with click handlers attached that don't react to keyboard navigation. The latter is important e.g. for folks suffering from Parkinson's or other diseases that make mouse control difficult.
  • 0
    @Fast-Nop Sure, it sucks. But that is the most you can expect a code monkey to do and the main metric in this shitwork economy is cheap time to market, not quality.

    The frameworks aren't the cause of this social problem - just one of the symptoms.
  • 0
    @Oktokolo that why you have to lay down the law and tell the code monkeys no
  • 1
    @Oktokolo Bootcrap came from Twitter, and at a time when they did have ample engineering resources. It's also not true that this trainwreck saved any time.

    It's not only made for unqualified people who don't understand what CSS even is, it's also by such people.

    All their money didn't get them a competent CTO who would have shot that nonsense down from the get-go. Also, he would have seen the need to immediately schedule dev trainings because the same gross incompetency that begot Bootcrap has a strategic business risk of also rearing its ugly head in other projects.

    It's not that the implementation is bad - the very idea already is.
  • 0
    @ostream You havn't even understood what the rant is about. I take it that you're in frontend? That would explain why.
  • 0
    @ostream Looks like I hit the mark, given that one reply by me was enough for you to delete your whole miserable rant.

    You little motherfucker dish out left and right, but are unable to take the slightest flak.

    You're not only as dumb as 10m of wet field path, you're also as pathetic as a rabbit that a bear has abused as toilet paper!

    (Edit: and now he deleted his whole account.)
  • 1
    but if their code wasnt so uneffiecient we wouldnt have any reason to upgrade our devices :(
  • 2
    i get so much shit when i say that i loathe bootstrap. this post makes me feel sane again ;_;
  • 2
  • 0
    MinE CsS library is better!!!
    https://pogromistdev.github.io/bull...
  • 0
    @Pogromist Just one example from your docs:

    <div class="bc-btn green">amazing</div>

    You failed to understand the point of HTML and CSS, just like all other CSS frameworks, and that's because the very idea of a CSS framework pretty much requires you to not understand HTML and CSS to begin with.
Add Comment