4 ms·

So for every project you implement solutions to common problems differently?

• pjmlp 9y ago
  We use server side rendering with minimal JavaScript for dynamic behaviors. ASP.NET, Spring and JEE work just fine.
  • monkeynotes 9y ago
    The answer to the complexity of JS and associated frameworks/libraries cannot simply be "stop making JS apps". Don't get me wrong, I agree server side rendering is a lot simpler and solves many problems, but there are plenty of reasons to go with a full client-side app and in those cases libraries and frameworks, while not essential, are logical and sensible conclusions.
    • pjmlp 9y ago
      I rather prefer to eventually be able to use Web Components across all major browsers.
      • joshribakoff 9y ago
        The spec constantly evolves. At some point, there will be web components "v2" and coding "regular" web components will be outdated. As the spec evolves, browsers will evolve at different paces & implement things differently. Such is the reality of cross platform development. The only constant is change itself. To deal with it we use tools like polyfills, libs, and frameworks.
        • pjmlp 9y ago
          That matters very little because our components are wrapped in ASP.NET, Spring, JEE components. For the user of use components the difference will be quite thin, if at all.
          • joshribakoff 9y ago
            Right, those things fall into the category of tools libs & frameworks. Like Carl Sagan says if you want to make an apple pie from scratch you have to first invent the universe. There's always going to be change and need to support backwards compatibility, so polyfills libraries & frameworks likely aren't going away anytime soon, even after web components are widely supported.