Fucking frontenders…

So tired of your fucking hip things…

Always something new…

Always something ”innovative”

Fucking MB and MB and MB of images…

Make it fast you imbecils! It’s 2023!

*laughs in backend*

/me cries in frontend

fucking "frontenders" who don't understand frontend

Unexpected. The hippest (not really, been standard for ages) frontend thing in my world has been using srcSet and lazy loading images to ensure a minimal amount of image kilobytes are loaded.

To the point where backend folks think it's over engineering.

"what's this img element html with an incomprehensible srcSet value- is it really worth it?"

Bwahahaha and all those mbs of frameworks for the most simple things.

@jiraTicket things changed. Now most front end designers think that everybody are on fiber optic connection and intel i7 processor.

SVGFTW

I want a calculation of how much energy is consumed by all javascript engines out there. All css cpu time.

Fucking-traversing-all-the-dom-again-and-again-and-again…

Fucking retards…

@ostream
> half of [the stupid shit done on the Internet] is unnecessary
The half that's porn or the other half?

@daniel-wu When you say "now" - since how long ago do you mean? I feel like there was a period a long time ago (when you could still have mobile as an afterthought and design a public website as "primarily desktop") where some would have a complete disregard for performance. But for the past 5 years I've felt like there's quite high performance awareness - for example with many clientside SPA moving to suggesting initialt server side rendering with some clientside hydration.

@ostream I am not blaming people. I am blaming the system. I have written numerous times that I love frontenders. Because it is a needed value. And I know for sure that I will quit my job in an instant if leadership creates a situation where I even have to wtite a single line of frontend stuff.

But why oh why has the industry still not come to terms with the issue, oh let me think, of remembering the scroll position when clicking back? And what the fuck is up with the huge images? Again and again and again and again.

It never stops. Never! Completely new fucking frontends. Just incredibly bloated with another new ”innovative” way of navigating. Huge images. Wasted scroll positions. Etc.

We can talk about everything. But it is just not going to be that much of constructive discussion. I am not saying that ”the rest” is good! I am saying that it is 2023 and the frontend business is a land of freaking chaos and it consuming vast amount of resources and causing much pain.

@saucyatom funny! But the internet is probably one of human kinds most valuable innovations if you can call it that. It’s right up there with the book. It has been a catalyst for almost everything on Earth. From good to bad.

@jiraTicket Agreed! We are throwing out everything that not passes our new architectural guidelines and our new roadmap. Frontend perf is now a thing much more than it was in the past. At least at our little store (multi-multi-multi-billion dollar industry). You don’t got it, you will not pass the gate. And this was only changed a year or so back! We are big, we did a bad job previously and we are trying to get to a better position. It’s hard.

Previously, we did not even care. It seems like we let anybody onboard and now we suffer. And even that was good compared to (some of ) the shitty stuff we developed internally!

(And I am only talking about frontend even though everything is linked. I get it.)