Make front end shit again • Hacker News Board

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?

> ... 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?

Yes?

I can't be certain but I think that was the point.

Re: Make front end shit again

#25

Post by tombert » Sun, May 13, 2018, 7:36 PM UTC

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.

Re: Make front end shit again

#26

Post by jlgaddis » Sun, May 13, 2018, 7:37 PM UTC

What, no !?

Re: Make front end shit again

#27

Post by gerdesj » Sun, May 13, 2018, 7:38 PM UTC

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?

Shouldn't this literally be a single page, hand-built HTML file with inline CSS? Is this trying to be self-ironic or something?

Yes, I'm going to assume that is a parody. However, signs of FrontPage or Word as an editor would be cool.

Re: Make front end shit again

#28

Post by lgessler » Sun, May 13, 2018, 7:38 PM UTC

Check out Digital Folklore[1] if you're into this aesthetic, it's a good collection of essays on Geocities, the early web, and related topics. One of the authors' web site[2] is also worth a look (warning: there's sound :) ). She also runs a Tumblr blog[3] that posts screenshots of real Geocities sites.

[1]: http://digitalfolklore.org/

[2]: http://art.teleportacia.org/olia.html

[3]: http://blog.geocities.institute/

Re: Make front end shit again

#29

Post by peatmoss » Sun, May 13, 2018, 7:40 PM UTC

gerdesj wrote: post #22

kbody wrote: post #7

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

I might have done this: http://www.ex-parrot.com/pete/upside-down-ternet.html to an entire business division for a while. Might have.

https has ruined everything :-)

Re: Make front end shit again

#30

Post by wereHamster » Sun, May 13, 2018, 7:40 PM UTC

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 punchcards and a 20ton 'computer' for all I care.