Earlier quoted context omitted.
Upvote for serious criticism. I still take this over: - the noncompliant cookie warnings - ... with >400 "partners" (yes, I have counted) - works best in IE^HChrome - 20 seconds loading - written for Googlebot, instead of for a human like either the author or me. (Meaning it is bland, formula-driven.) websites I often deal with as long as it provides the answers/entertainment I am looking for.
> - works best in IE^HChrome There's a GIF at the bottom declaring "This page is best viewed with Netscape 3.0"
Make Front End Shit Again (2018)
171–177 of 177 posts
Re: Make Front End Shit Again (2018)
#172I'm on mobile. It loads quick. I saw no ads. It was reasonable straight to the point: no explanation about this being grandmothers pie recipe or anything to that effect. (In fact, if you consider the point of the website to be funny it is actually straight to the point.) If it is fast, doesn't track me and provides the answers I need I can put up with some animations. I'd say what we have today is far more problemati…
I loaded it on mobile too.. - Horizontal scrolling because it isn't properly responsive. - it doesn't reflow when the device orientation changes - no sound (there's an audio control so I guess there's meant to be..) - the audio control sits over the flags - wildly different text sizes everywhere - so much layout shift - from an error loading the Korean version I think it's running on a platform that tracks what users…
When you lift a CRT and turn it sideways, it is usually done because it's placed incorrectly (no "reflow" wanted). It's also unusual to attempt to read a website on it at the same time you are risking injury.
Re: Make Front End Shit Again (2018)
#173Re: Make Front End Shit Again (2018)
#174This faked nostalgia is becoming irritating. Websites which were like that didn't last long, and mostly were hosted on free webservers. If you want to get rid of nostalgia please spend 60 whole minutes making sense of HTML+PHP5.6+jQuery copy pasted code. And make it IE6 compatible. And use tables for layout. And don't use stackoverflow, caniuse, or an IDE. You'll soon understand how we reached the current state of th…
// For example, instead of
$("#somebutton").click(() => alert("Hello"))
// You would do
document.querySelector("#somebutton").addEventListener("click", () => alert("Hello"));
// Instead of
$("#message").text("Important Message")
// You would do
document.querySelector("#message").textContent = "Important Message";
// Instead of
$("#things .thing").css("color", "red")
// You would do
for(let e of document.querySelectorAll("#things .thing")) e.style.color = "red";
// Instead of
await $.ajax("https://httpbin.org/get").then((_1, _2, {responseJSON}) => responseJSON)
// You would do
await fetch("https://httpbin.org/get").then(e => e.json())Re: Make Front End Shit Again (2018)
#175Re: Make Front End Shit Again (2018)
#176The website makes bold claim of being best viewed in Netscape 3. That does not seem to be the case though https://i.imgur.com/WKpmd28.png
Wow, that's the nostalgia at the bottom of your screenshot: "27% of 3182K (at 1.5K/sec, 25:33 remaining)"
Re: Make Front End Shit Again (2018)
#177Earlier quoted context omitted.
No, the browser checks the call stack of the javascript function. If the play() isn't a direct result of some kind of user interaction. It will just deny you from playing audio. So play upon you open the page is no longer possible. You at least need to wait for the user to touch somewhere on the page.
Yeah there's all sorts of nonsense you can do to do autoplay. I kind of remember at one of my old jobs, to get autoplay working on some elearning courses, when the user clicked 'Start', we'd start the audio but not play anything, and then switch out the file that was played when required which would 'autoplay' as the user had already initiated the sound. At least that was the general idea afaik.