Another classic site to show in this regard is this Norwegian online store.
Make Front End Shit Again (2018)
111–120 of 177 posts
Re: Make Front End Shit Again (2018)
#112I'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…
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.
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.
Re: Make Front End Shit Again (2018)
#113It's been such a long time since I've seen a
Re: Make Front End Shit Again (2018)
#114The 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
The whole website is nothing but nostalgia bullsh*t :D
Re: Make Front End Shit Again (2018)
#115what this site got wrong is just "remember jquery ?", this was a modern thing back then and almost nobody used. Would make more sense "remember tables for everything ?"
Yep, and 1x1 gifs for sizing certain unsize-able elements.
I'm building a web site currently, after a looong break from web development. It's almost unbelievable how much cleaner HTML, DOM and JS have gotten. It's more of a pleasure (only relatively to the previous eras) building pages and you actually don't need frameworks.
Re: Make Front End Shit Again (2018)
#116It's a shitty website, but still uses like 500mb of node_modules to build, that's not the way we should be going to.
So true. If you want to build an oldschool website do it the oldschool way! Otherwise it's kind of lame...
Re: Make Front End Shit Again (2018)
#117It's a shitty website, but still uses like 500mb of node_modules to build, that's not the way we should be going to.
Might be part of the joke ;)
Re: Make Front End Shit Again (2018)
#118We need a simple modern serverless hit counter image like every site used to have back in the day. Maybe a S3 bucket that hosts the hit counter image and then a lambda cron job that wakes up every few hours to crawl the S3 bucket access logs, aggregate the hit count, and write out a new counter image to the bucket.
Re: Make Front End Shit Again (2018)
#119Someone once told me, “you will know what nostalgia truly is, when you see a younger generations nostalgia and think it’s still shit because you are too old for that to have been your childhood”. The jQuery era is something I’d never want to go back to. Not because jQuery was bad, but because the basic DOM api was so poor, JavaScript was much more limited and incoherent, and webpages made anything outside of text inp…
In this case I could alter that to: "You will know what nostalgia truly is, when you see a younger generations representation of nostalgia and you can point out all the anachronisms in it." Netscape 3 and websites that looked like that: 1996 Geocities: 1994-1999 (so far so good) jQuery: 2006 Blink: 2013
Huh. When I read that I assumed Blink referred to the tag, but reading again you might actually be right that it means Google's browser engine. Truly anachronistic indeed.
Re: Make Front End Shit Again (2018)
#120The nostalgia is so overwhelming I'm super sad now. Such good times!!!!