4 ms·

I'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

I'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 problematic than a few animations. Also, most surviving websites from that era aren't that bad when it comes to animation: use marginalia to search for food recipes and see what I mean.

styeco 5y ago
And it's all done in Nuxt.js/Vue
hulitu 5y ago
Same experience here. It loads instantly when 99% of the sites need 30s to 1 min to load. It looks decent on mobile (not too big, not too small). Contrast is good, fonts are readable. This guy should give web design lessons.
- King-Aaron 5y ago
  > This guy should give web design lessons https://twitter.com/NikkitaFTW https://twitter.com/NikkitaFTW I would assume it's 'this girl', but I do agree
- brettermeier 5y ago
  It looks like poo on mobile, no offence, but you can't see the whole page and you can scroll to the right and stuff. It's just ugly.
onion2k 5y ago
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.
- kamray23 5y ago
  Sound autoplay doesn't really work anymore in modern browsers.
  - DocTomoe 5y ago
    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.
    - kamray23 5y ago
      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.
    - codethief 5y ago
      Shouldn't it be possible to still achieve auto-play using JavaScript? It's just a tiny bit more effort. :)
      - mmis1000 5y ago
        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.
        Accacin 5y ago
        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.
ahoka 5y ago
It's full of tracking though.
- skinkestek 5y ago
  That is sad to hear even if it loads instantly. Does it have 400 "partners" too?
divbzero 5y ago
It’s actually built with Nuxt, a Vue framework [1]. I believe this style is called “faux retro”. [1]: https://github.com/SaraVieira/make-frontend-shit-again/ https://github.com/SaraVieira/make-frontend-shit-again/
sapht 5y ago
The only thing worse about this than whichever 2020-era website was the "Right click is disabled!" as I tried to leave. (That made me chuckle). The other stuff is just nostalgia and not really related to the degradation of web UX. Irrelevant gifs and ugly colors are easier to ignore than 1000-page cookie dialogs.
- brobinson 5y ago
  For Firefox/Librewolf users, you can hold shift when you right click to bypass scripts that try to disable your ability to right click. I laughed when that popped up for me. A very authentic experience.

styeco 5y ago

And it's all done in Nuxt.js/Vue

hulitu 5y ago

Same experience here. It loads instantly when 99% of the sites need 30s to 1 min to load. It looks decent on mobile (not too big, not too small). Contrast is good, fonts are readable. This guy should give web design lessons.

King-Aaron 5y ago
> This guy should give web design lessons https://twitter.com/NikkitaFTW https://twitter.com/NikkitaFTW I would assume it's 'this girl', but I do agree
brettermeier 5y ago
It looks like poo on mobile, no offence, but you can't see the whole page and you can scroll to the right and stuff. It's just ugly.

onion2k 5y ago

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.

kamray23 5y ago
Sound autoplay doesn't really work anymore in modern browsers.
- DocTomoe 5y ago
  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.
  - kamray23 5y ago
    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.
  - codethief 5y ago
    Shouldn't it be possible to still achieve auto-play using JavaScript? It's just a tiny bit more effort. :)
    - mmis1000 5y ago
      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.
      - Accacin 5y ago
        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.

ahoka 5y ago

It's full of tracking though.

skinkestek 5y ago
That is sad to hear even if it loads instantly. Does it have 400 "partners" too?

divbzero 5y ago

It’s actually built with Nuxt, a Vue framework [1]. I believe this style is called “faux retro”. [1]: https://github.com/SaraVieira/make-frontend-shit-again/ https://github.com/SaraVieira/make-frontend-shit-again/

sapht 5y ago

The only thing worse about this than whichever 2020-era website was the "Right click is disabled!" as I tried to leave. (That made me chuckle). The other stuff is just nostalgia and not really related to the degradation of web UX. Irrelevant gifs and ugly colors are easier to ignore than 1000-page cookie dialogs.

brobinson 5y ago
For Firefox/Librewolf users, you can hold shift when you right click to bypass scripts that try to disable your ability to right click. I laughed when that popped up for me. A very authentic experience.