• pythonoob@programming.dev
      101·
      1 year ago

      You and I are off the fucking scale. In which direction? Nobody can sa… It’s the left side. I am on the left side.

  • Potatos_are_not_friends@lemmy.world
    462·
    1 year ago

    Some frontend guy said this best. It was something along the lines of:

    “JS frameworks went real hard in client side rendering and branding server-side rendering old and archaic. But that they hit performance issues and began re-adopting server side features and trying to make it look cool again after shitting on it for a decade.”

    • mr_tyler_durden@lemmy.world
      191·
      1 year ago

      I’ve got nothing against SSR, never have, but CSR or even better SSR+CSR side steps a metric shit ton of issues. I’ve written untold lines of code to render something out in PHP then needed to add jQuery logic to the frontend for UX/UI reasons and then I’ve had to duplicate UI generation in JS/jQuery to match what PHP spits back (think: add a new row to an interface after an Ajax call finishes). It’s hell, you have to keep the two in sync and it’s a bug minefield.

      Compare that to CSR where all the DOM is generated though a single codepath. Now take CSR to the next level with SSR+CSR and you’ve got a winning combo. Fast initial render and SEO gains (if you even need that) and only 1 DOM generation pathway.

      People want to sound all smug “Oh, back to SSR are we?”, “Uh yeah, we had to CSR first to get to SSR+CSR which is VASTLY superior to SSR alone”.

      Tech is circular in that way. See also mainframes, to personal computers, to cloud or any other similar cycle.

  • bleistift2@feddit.deEnglish
    234·
    1 year ago

    Are web servers that serve real HTML responses still a thing? Honest question. I thought JSON+client side rendering were the default by now.

          • SpaceNoodle@lemmy.world
            31·
            1 year ago

            🙄

            I’ll admit that it’s been quite a while since I’ve touched PHP, but that was never my main focus.

        • Ricaz@lemmy.ml
          91·
          1 year ago

          Coming from C-like syntax, Python looks horrible to me. PHP has come a long way with 7 and 8.

          • Tenshi@lemmy.world
            41·
            1 year ago

            I heard a lot of complaints about Python, but it’s looks weren’t any of them. It’s the sexiest language out there.

            Since I moved to python I wish all languages would just drop brackets, they’re dirt.

            • Ricaz@lemmy.ml
              1·
              1 year ago

              I hear it a lot from almost all my engineer friends, so I guess it just depends on your field.

          • SpaceNoodle@lemmy.world
            54·
            1 year ago

            I’ve got a C background as well, and I find Python o br considerably cleaner (and the code isn’t 50% dollar signs).

      • magic_lobster_party@kbin.social
        8·
        1 year ago

        Especially with frontend. Feels like every few years there’s a complete paradigm shift that forces everything to be rewritten from scratch.

        • argv_minus_one@beehaw.org
          11·
          1 year ago

          Because web development sucks, web developers are always trying to reinvent web development such that it doesn’t suck, and they keep failing.

          They keep failing because it’s impossible, and it’s impossible because the requirements are directly contradictory.

          • Web application code must be simple and understandable (which requires the application to use a minimum of libraries and frameworks), but web applications must look and feel modern and fancy (which requires big, complicated frameworks).
          • Web development must be easy (which requires the project to be written in JavaScript or something similarly simple), but web applications must have sophisticated functionality and not crash (which requires the project to be written in TypeScript, Rust, or something similarly non-simple).
          • Web development must be easy (which requires the entire project to be written in a single language), but web applications must work to at least a basic degree with scripting disabled (which requires the project to contain non-trivial amounts of HTML and CSS in addition to JavaScript/TypeScript/Rust/etc).
          • Web applications must be fast and not crash (which requires a compilation step with type checking), but it must be possible to iterate very quickly (which requires there to not be a compilation step).
          • And so on.

          And they keep failing because, quite frankly, they don’t know how to succeed. Most web developers are not grizzled 50-year-olds with decades of experience and a solid understanding of things like type systems and build automation, and most grizzled 50-year-olds with decades of experience and a solid understanding of things like type systems and build automation want nothing to do with web development. Microsoft somehow managed to scrape together enough exceptional individuals to create TypeScript, but they seem to have exhausted the supply of such individuals.

          Most web developers don’t even seem to fully appreciate what TypeScript does and why it’s important, let alone have the skill to write similarly sophisticated tools themselves. Consider, for example, Vite not running TypeScript type checking with every build. Vite’s developers cite compilation speed as their motivation for cutting this corner. These people clearly do not understand the importance of correctness checking.

          Another example: as far as I can tell, no web application build tools track dependencies between source files for incremental compilation, nor am I aware of any standard format for compilers (TypeScript, Sass, Babel, etc) to communicate that information to the build tools invoking them (Webpack, Vite, Grunt, etc).

          Every once in a while there’s a ray of hope, like TypeScript, but that’s all it is: hope. The web developer experience has never been anywhere close to the caliber of developer experience you’ll get with a language like Rust, and sadly I don’t foresee that changing any time soon.

          And no, htmx is not the answer to our prayers. It seeks to fix HTML, and HTML is not what’s fundamentally broken.

          • bleistift2@feddit.deEnglish
            1·
            1 year ago

            no web application build tools track dependencies between source files for incremental compilation

            Angular builds are incremental by default.

            Web development must be easy

            Why should that requirement hold for web development but not for any other kind of development?

            it must be possible to iterate very quickly (which requires there to not be a compilation step)

            Again, Angular makes an incremental build in about a second, maybe 5 for large applications. Compare this to Java, where even simple backends require 20–30 seconds of build time.

            Web application code must be simple and understandable (which requires the application to use a minimum of libraries and frameworks)

            This makes no sense. Which is simpler – a function called mergeObjects from a library or a recursive function of 30–50 lines to do this without the library? Libraries’ whole purpose is making things simpler.

            Web applications must be fast and not crash (which requires a compilation step […])

            Ever heard of just-in-time compilation?

            TypeScript, but they seem to have exhausted the supply of such individuals

            TypeScript has minor-point releases about every 3–4 months. What makes you think it’s dying?

            To conclude, because this post is long enough: Your comment is full of opinions, but little else.

      • MyNameIsRichard@lemmy.ml
        71·
        1 year ago

        Centralise what’s decentralised and decentralise what’s Centralised and you’ll look like a genius.

        • Square Singer@feddit.de
          9·
          1 year ago

          At my last company, there was a massive half-year project for the whole department to move all the microservices and all that stuff (multiple hundred projects) into a monorepo.

          Then my team was transferred to another department. Here we had a massive, half-year project for the whole department, to pick apart a similarly-sized monorepo into separate microservice repos.