Personally I like using server side rendering when I can. The UI should be as light weight as possible and you can do a lot with just HTML and CSS. That said, it’s pretty hard to build a responsive web app without at least a little bit of JavaScript.
That said, it’s pretty hard to build a responsive web app without at least a little bit of JavaScript.
Not really. You just need to learn the difference between width and max-width.
I do UserCSS now and then and 2 of 3 sites use them wrong. That and position: fixed overuse. Also, use @media (min-width) only for layout changes, not for sizing.
And also, functionality/layouting first, design after.
I’m the other way around. For me, the UI can be chonky frameworks or whatever as long as the user experience is good and it works on lots of platforms.
But keep every bit of UI out of my back-end systems. The data and business logic layers should be so divorced from the UI that they didn’t even get visitation rights with the kids.
That said, it’s pretty hard to build a responsive web app without at least a little bit of JavaScript.
And then the question comes up, why would you need responsiveness. Auto-completion of search results? Hate that crap. Endless scroll with loading additional contents? Hate that crap. Everything blinking and whistling? I suppose JS in that case is possible, but purely for stylistic purposes and not functionality.
Personally I like using server side rendering when I can. The UI should be as light weight as possible and you can do a lot with just HTML and CSS. That said, it’s pretty hard to build a responsive web app without at least a little bit of JavaScript.
Not really. You just need to learn the difference between
widthandmax-width.I do UserCSS now and then and 2 of 3 sites use them wrong. That and
position: fixedoveruse. Also, use@media (min-width)only for layout changes, not for sizing.And also, functionality/layouting first, design after.
I’m the other way around. For me, the UI can be chonky frameworks or whatever as long as the user experience is good and it works on lots of platforms.
But keep every bit of UI out of my back-end systems. The data and business logic layers should be so divorced from the UI that they didn’t even get visitation rights with the kids.
Modern server side rendering can luckily be separate from your actual back end. Doesn’t even have to live in the same server.
And then the question comes up, why would you need responsiveness. Auto-completion of search results? Hate that crap. Endless scroll with loading additional contents? Hate that crap. Everything blinking and whistling? I suppose JS in that case is possible, but purely for stylistic purposes and not functionality.