Hmm, do we have an example?
We do. We even have an accompanying rant.
This meme was, uhm… inspired by Jamendo.
Great service. You can download Creative Commons music for the cost of creating an account there. That’s at least part of why it’s “Oh dear, oh dear. Gorgeous.”.But well, the button for downloading whole albums is broken.
So, what I’ve been doing, is to just open each song in a new tab, and then repeatedly click download → confirm → close tab.
And then by resizing the window, it’s even possible to align the download- and confirm-buttons, so it’s just double-click → Ctrl+W.But because of said loading screen, I have to remember to resize the window before I open all the tabs. Otherwise, I’ll get the loading screen every single time I’m put onto a new tab.
I’m guessing, it doesn’t use CSS to do the responsiveness, but rather it’s JavaScript that grabs the window dimensions and calculates how big everything has to be. But it doesn’t get told about the window having been resized until the tab is shown again, and because the JavaScript rendering is slow, you get this short loading screen every single time.
“Meh, fuck it. Good enough. We’ll fix it in phase two.”
“There is nothing more permanent than a temporary fix”
- Old African proverb
Yeah, maybe. My interpretation was that this webpage got implemented around a decade ago, when this was just how lots of webpages did responsive design, and it has only seen light maintenance ever since. But yeah, I’m also just spitballing…