Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Make front end shit again

makefrontendshitagain.party

Post reply on HN
Print view View original

31–40 of 227 posts

Re: Make front end shit again

#31

Post by zzzcpan »

jameskilton wrote: post #19

I love the point the site is trying to make but I'm confused as to why this is built with a vue.js static site generator requiring node/npm/yarn and an almost 7,000 line yarn.lock file. Shouldn't this literally be a single page, hand-built HTML file with inline CSS? Is this trying to be self-ironic or something?

This is more like fun old web being reborn as brutalism in web design. Sadly, doesn't have anything to do with hand made html and css, just visuals.

EDIT: An article on brutalism and antidesign: https://www.nngroup.com/articles/brutalism-antidesign/

Re: Make front end shit again

#32

Post by objplant »

When I see a page like that I remember Mahir's page and its popularity: http://mahir.faithweb.com/original.htm

It's nostalgic and definitely different from what we are used to today, but I don't really miss animated gifs, dozens of font styles and colors smashed together into a html. For me a cherry on the top was changing status message when hovering a link from target url to some custom text.

Re: Make front end shit again

#33

Post by antod »

kbody wrote: post #7

"We used to make websites because it was fun and at a point we lost the way." Indeed.

I can't help feel that most of that fun was the relative novelty at the time. Without that novelty, it's not so fun any more. Although I miss Usenet more than GeoCities and webrings etc

Re: Make front end shit again

#34

Post by bmuon »

tombert wrote: post #25

I agree with the sentiment of this site. I have an nginx proxy set up for personal stuff, and the home page was done in an homage to GeoCities: https://brucewillis.sexy/ Eventually I will get midi music playing correctly with mouse-tails.

I feel like your site is better than the OP site at what the OP site tries to do.

Re: Make front end shit again

#35

Post by citricsquid »

A few months ago I created a project called Hypertext Town, a simple project where anybody can create "camps" (a collection of HTML, images etc.) and connect them together through "towns". A town lives at a subdomain (e.g: town.hypertext.town) and a camp lives at /~camp (e.g: town.hypertext.town/~camp). I never "launched" it so it's just been languishing in obscurity on the www but if anybody wants to make cute little creative HTML websites without the need for hosting, it's live to use at: https://www.hypertext.town

1. click "Set up camp in www" 2. make an account 3. choose your camp name 3. add your html / images etc.

edit: visit https://hackernews.hypertext.town (by TeMPOraL)

Re: Make front end shit again

#38

Post by Camillo »

That was not "front end", that was webpages. There was no "back end" and no business, the webpage was the whole thing. And you were not paid as a "front end engineer" or even a "designer", in fact you were not paid at all, you were just some guy making a webpage.

Re: Make front end shit again

#39

Post by TobiasA »

wereHamster wrote: post #30
jameskilton wrote: post #19

I love the point the site is trying to make but I'm confused as to why this is built with a vue.js static site generator requiring node/npm/yarn and an almost 7,000 line yarn.lock file. Shouldn't this literally be a single page, hand-built HTML file with inline CSS? Is this trying to be self-ironic or something?

Hand-build HTML file with inline CSS, that you edit with $YOURFAVOURITETEXTEDITOR which requires an OS that's 50 million lines of code. And you're complaining about 7000 lines in an auto-generated file, which doesn't even have to be touched nor edited by a human? The tools we use are insignificant, what's important is the result. If the result is a HTML file with inline CSS, who cares how it was created? You can use…

Way to miss the point.

Re: Make front end shit again

#40

Post by mherrmann »

wereHamster wrote: post #30
jameskilton wrote: post #19

I love the point the site is trying to make but I'm confused as to why this is built with a vue.js static site generator requiring node/npm/yarn and an almost 7,000 line yarn.lock file. Shouldn't this literally be a single page, hand-built HTML file with inline CSS? Is this trying to be self-ironic or something?

Hand-build HTML file with inline CSS, that you edit with $YOURFAVOURITETEXTEDITOR which requires an OS that's 50 million lines of code. And you're complaining about 7000 lines in an auto-generated file, which doesn't even have to be touched nor edited by a human? The tools we use are insignificant, what's important is the result. If the result is a HTML file with inline CSS, who cares how it was created? You can use…

Tools come with overhead and complexity. You're right that only the end results matter. But (eg.) loading time is one aspect of it.
Post reply on HN