3 ms·

We've created the need front-end and back-end developer distinction by creating overly complex front-end build systems, and overly complex SPA frameworks.

• Capricorn2481 3y ago
  I have the complete opposite view. I'm a fullstack dev, so I'm comfortable using Javascript and a backend language. JS replacements like Blazor clearly serve backend engineers who don't want to deal with JS. That's fine, and it's a valid way of developing, but it's clear that using JS with C# is a more holistic way of developing.
  • sebazzz 3y ago
    I'm comfortable with Javascript. I'm not comfortable with constantly having to change and upgrade my code or build system for the next breaking change in Webpack or in an unreadable complex Typescript typing, or the spider web of React libraries. Doing nothing is not an option either, because that bites you in the ass as well because that newer Node runtime turns out not to support a deprecated md5 hash function the outdated Webpack in this project, which only gets a few weeks attention per year, relied on. Now I only have Blazor for my frontend with a little bit of gulp to compile some dart-sass with design tokens and do some minification on some glue javascript.
    • Capricorn2481 3y ago
      Why are you using md5 functions on the frontend? We're talking about using javascript for frontend
      • sebazzz 3y ago
        Read again, Webpack used that.
        • Capricorn2481 3y ago
          Is gulp really better than webpack in this case? I have a few gulp projects and they're not exactly standing up to the test of time.