News for hackers. Stuff that matters.
Re:Make Front End Shit Again (2018) by onion2k on Thursday January 20, 2022 @02:42AM (#30005961)
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 do (serverside tracking is mostly fine in my opinion, and unavoidable really, but it's still tracking).

It's fun, and oddly similar to my first website actually, but I'll take the modern Web over this sort of nostalgia every time.

Re:Make Front End Shit Again (2018) by skinkestek on Thursday January 20, 2022 @02:53AM (#30006038)
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.

Re:Make Front End Shit Again (2018) by aasasd on Thursday January 20, 2022 @04:05AM (#30006544)
> with >400 "partners"

You can update the number to 500, as that's what Yahoo has (something like 530, but I don't remember for certain).

Re:Make Front End Shit Again (2018) by ItsBob on Thursday January 20, 2022 @04:34AM (#30006729)
I was on a news site, might have been a newspaper site, and it had 640... beat that! :)
Re:Make Front End Shit Again (2018) by chriswarbo on Thursday January 20, 2022 @04:54AM (#30006850)
> - works best in IE^HChrome

There's a GIF at the bottom declaring "This page is best viewed with Netscape 3.0"

Re:Make Front End Shit Again (2018) by skinkestek on Thursday January 20, 2022 @05:50AM (#30007231)
I'm chuckling silently over here. Well done whoever did it :-)
Re:Make Front End Shit Again (2018) by liftm on Thursday January 20, 2022 @04:16AM (#30006608)
> - Horizontal scrolling because it isn't properly responsive.

It actually is properly responsive: it has horizontal scrolling on desktop too, and by just the exact amount, no matter what the window size is. (At least on FF.)

Re:Make Front End Shit Again (2018) by vosper on Thursday January 20, 2022 @03:38AM (#30006354)
> it doesn't reflow when the device orientation changes

Does anyone design sites for landscape any more?

Re:Make Front End Shit Again (2018) by brettermeier on Thursday January 20, 2022 @03:51AM (#30006442)
Who doesn't is the question? I view nearly everything on landscape mode, 'cause I don't like visiting websites with my phone.
Re:Make Front End Shit Again (2018) by HelloNurse on Thursday January 20, 2022 @05:59AM (#30007301)
> it doesn't reflow when the device orientation changes

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) by kamray23 on Thursday January 20, 2022 @02:46AM (#30005981)
Sound autoplay doesn't really work anymore in modern browsers.
Re:Make Front End Shit Again (2018) by DocTomoe on Thursday January 20, 2022 @02:55AM (#30006051)
And thank whatever deity you may or may not believe in that this changed. Yes, it sucks for these traditional websites, but advertisers abused it so much it hurt.
Re:Make Front End Shit Again (2018) by kamray23 on Thursday January 20, 2022 @03:03AM (#30006107)
Indeed. The end of autoplay being on by default or not being a setting at all is a blessing far more than anyone worth their salt has even thought it could be a curse.
Re:Make Front End Shit Again (2018) by codethief on Thursday January 20, 2022 @03:07AM (#30006134)
Shouldn't it be possible to still achieve auto-play using JavaScript? It's just a tiny bit more effort. :)
Re:Make Front End Shit Again (2018) by mmis1000 on Thursday January 20, 2022 @03:29AM (#30006302)
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.

Re:Make Front End Shit Again (2018) by Accacin on Thursday January 20, 2022 @03:45AM (#30006401)
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.
Re:Make Front End Shit Again (2018) by kamray23 on Friday January 21, 2022 @05:10AM (#30021500)
Only works well on single-page applications. A much more insidious strategy is to bind to the "Accept cookies" button.
Re:Make Front End Shit Again (2018) by danw1979 on Thursday January 20, 2022 @04:05AM (#30006546)
and now all we need to do is the same for video...
Re:Make Front End Shit Again (2018) by easrng on Thursday January 20, 2022 @04:09AM (#30006567)
Video does the same thing, except you can autoplay it if it's muted.
Re:Make Front End Shit Again (2018) by EGreg on Thursday January 20, 2022 @03:34AM (#30006335)
Oh man, you're right!

https://www.zombo.com/

(Defeats the whole purpose of the site hehe)