exerceo
3h

The "JavaScript-based web app" starter pack.
Build web sites, not web "apps".
JavaScript is an enhancement, not a replacement for HTML.

Comments
  • The "boomer or backend dev who has no idea what he's talking about" starter pack
    How about we go back to PHP in 2000 where you need a full page refresh for every single action 🤡🤡
  • @devRancid Read my post again.

    JavaScript is an enhancement, not a replacement.

    This means the initial page load is via HTML, but enhancements such as posting comments without reloading the page are done via JavaScript.
  • Only js vs enhancements vs static html isn't gonna get rid of network/loading issues so what's the point of the image
  • @exerceo every place I’ve worked we use JS frameworks. I can’t say I really have much control over the "initial loading" phase.

    This is the type of stuff you should be addressing to JS framework developers, not run of the mill devs on devRant
  • @black-kite A lightweight static version could be displayed instead of an error message if the JS framework fails.

    The JS framework just needs to hide itself if it detects it failed.
  • where do I sign?
  • Javascript is a way of life. A religion. You just don't get it.
  • It depends on the level of interactivity the page requires. There are some legitimate web apps. Though the tech is overused. YouTube is a great example. The only reason YT needs to be a web app is because their premium version supports offline video. Which is neat, but is it worth making the whole thing a slow, glitchy experience on desktop browsers? I don’t think so.
  • @kiki In the comments :-)
  • @devRancid With progressive enhancement (HTML first, then JavaScript), the useful content loads first.

    With a JavaScript app, the useful content loads last. Only after all those megabyte-sized JavaScript files.
  • what OP says is unequivocally right in any scenario I can imagine. Always start with HTML. Even if I'm making a camera app, I would still start with HTML. HTML and CSS are my mockup tools. It's only when every screen is ready and looks production level that I can start making it dynamic with JS. This is even true for apps that work offline. I see no case in the browser where this approach wouldn't work, but “let's do everything in JS” would
Add Comment