• gmhafiz@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    1.2 million page views per month

    1,200,000 / 30 days / 24 hours / 60 minutes / 60 seconds is 0.46 requests per second.

    That is crazy low and is nothing to shout about. I notice people like to this in months to inflate the number to looks bigger. But calculating it down to RPS puts it to a perspective.

    So why not create a website out of really, really old technology?

    PHP 8.0 is no longer supported so I hope they update the “really, really old technology” to at least PHP 8.1 today.

  • bitcrafter@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    Wait… I just noticed this:

    [XHTML] never took off on the web, in part because in a website context so much HTML is generated by templates and libraries that it’s all too easy to introduce a syntax error somewhere along the line; and unlike HTML, where a syntax error would still render something, the tiniest syntax error in XHTML means the whole thing gets thrown out by the browser and you get the Yellow Screen of Death.

    This confuses me; don’t you want to make sure you are always generating a syntactically valid document, rather than hoping that the browser will make something suitable up to work around your mistake?

    • DeLift@feddit.nl
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      I feel the idea was that anyone should be able to make a webpage by just copy pasting snippits and to help with that html and Javascript will attempt to continue as best as it can, even if there are glaring issues.

        • DeLift@feddit.nl
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          Oh yes, Front-end developers suffer this decision daily. Luckily there things like Typescript to ease the pain.

    • polakkenak@feddit.dk
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      The thing with XHTML is that even a minor problem will make the page refuse to render and display a full page error message instead of any content. Having the browser guess how to handle the malformed HTML isn’t ideal, but it’s a lot better than showing nothing at all.

      • atheken@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        As an end result, maybe. But it also means that you get specific feedback on how to properly author it correctly and fix it before pushing it live.

        IDK, I lived through that whole era, and I’d attribute it more to the fact that HTML is easy enough to author in any text editor by complete novices. XHTML demands a hell of a lot more knowledge of how XML works, and what is valid (and, more keystrokes). The barrier to entry for XHTML is much, much, higher.

        • bitcrafter@programming.dev
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          I completely agree with that assessment, but what is weird to me is that most people use frameworks so they don’t actually touch any of the markup themselves.

          • atheken@programming.dev
            link
            fedilink
            arrow-up
            0
            ·
            6 months ago

            I don’t know if it’s “most people,” but I agree, there is no excuse for frameworks producing sloppy output - that being said, XHTML is a bit more chatty than HTML(5), so there is some minor benefit to not using the less verbose standard.

  • bitcrafter@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    Thanks, it’s actually kind of nice to hear someone who likes using PHP explaining in detail why they like it.