all 48 comments

sorted by: hot top controversial new old
[–] 70 points 3 years ago (2 children)

A highly compatible design with no ads, unnecessary images, videos, animations, scripts that goes straight to point delivering you exactly the information you need and nothing else? Something that's easily accessible even with old feature phones allowing older people to get information easily?
Simply something that loads instantly and just works?

Who would want that?

  • source
  • hideshow 4 child comments
  • [–] 26 points 3 years ago (1 child)

    Found the backend dev. "CUT THIS AESTHETICS NONSENSE! GIMME THE VARIABLE CONTENTS ALREADY! WE'RE 3.54 NANOSECONDS BEHIND!"

  • source
  • parent
  • hideshow 2 child comments
  • [–] 15 points 3 years ago (2 children)

    Frontend: "Come on, this needs at least some flair. This isn't the 90s."

    Throws React at it

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 3 years ago* (last edited 3 years ago)

    yeah, just css is enough.
    you don't need js unless you need to fetch data dynamically.
    you can do all of your animations, dropdowns and transitions in css.
    like this menu i made. no js in sight.

    https://streamable.com/4ba0gg

    also fully accessible and you can tab right into it without clicking enter or whatever
    (and respects prefers-reduced-motion)

  • source
  • parent
  • [+] 11 points 3 years ago (2 children)
  • [–] 0 points 3 years ago

    Entirely true.

    I'm currently working on a little project that's interesting to me (a low-spoiler walkthrough system for adventure games) and after a lot of back and forth, I decided to cut all of JS out of the picture. Just get rid of all of it, and do good old 90s server-side rendered HTML with modern CSS placed on top of it.

    And that's, honestly, a joy. The first draft of a page looks like the first screenshot, then you add some semantic classes to the html and throw some simple CSS at it and it looks acceptably neat. And I could get rid of so much janky toolchain I just fail to understand.

  • source
  • parent
  • [–] 15 points 3 years ago (2 children)

    The page at the top looks perfectly fine. It's useful, it gets the job done and it's lightweight.

  • source
  • hideshow 4 child comments
  • [–] 13 points 3 years ago (5 children)

    what is wrong with this frontend? not enough ads? loads too quickly?

  • source
  • hideshow 10 child comments
  • [–] 12 points 3 years ago (3 children)

    Good, that we have specialists for both and nobody is advocating that everyone should be doing full-stack work... oh wait.

  • source
  • hideshow 6 child comments
  • [–] 7 points 3 years ago (2 children)
  • [–] 1 point 3 years ago (1 child)
  • [–] 3 points 3 years ago

    As a backend developer who occasionally has to work on the frontend, that top image is pretty accurate although it requires bootstrap smeared all over to pretty things up a bit. After that it will have the "Good Enough" seal of approval.

  • source
  • [–] 2 points 3 years ago*

    I do front and backend work. Biggest issue I see is people not thinking through interfaces properly (e.g. efficiencies & atomicity of operations), sanitizing inputs on both sides, error handling, and putting in the appropriate validation, authorization & testing.

  • source
  • [–] 2 points 3 years ago*

    A proper backend developer would have the query be a URL using the GET method with a parameter that the user can fill-in directly in the address bar and the result be a text/plain page with just a bunch of numbers separated by pipe characters (or an application/json page with that info encoded as JSON if you wanna be fancy).

    This has the added advantage of working both for humans and as an API for use in machine to machine communications via HTTP.

  • source
  • [–] 2 points 3 years ago* (1 child)
    [–] 0 points 3 years ago (1 child)

    From my experience, devs be like:

    Backend, yay! Frontend, nay! ... and I the end, not even the backend works properly.

  • source
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

    What if I want the weather in Paris, TX?

  • source
  • hideshow 2 child comments
  • [–] 0 points 3 years ago

    As a full stack dev I'd like to say that the issue I see most from backend devs isn't a lack of styling, it's their need to wrap every element in 15 motherfucking divs. They don't seem to understand that most html elements are self contained and can stand on their own.

  • source
  • [–] -1 points 3 years ago

    The frontend developer made the backend so inefficient that it runs out of memory

  • source
  • [–] -3 points 3 years ago (1 child)

    God I wish weather pages were more like that first one.

  • source
  • hideshow 2 child comments
  • [–] 2 points 3 years ago (2 children)

    I like to use this one: https://wttr.in/

    You can get info for a specific city by appending it like this: https://wttr.in/newyork

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago*

    It seems to be down right now, but if i remember correctly this one also works when you are using a terminal and curl, i.E. curl wttr.in/newyork

    Edit: It works again, you can use the command as written above :D

  • source
  • parent