Live data from Hacker News

339 Bytes of Responsive CSS

blog.koley.in

21–30 of 101 posts

Re: 339 Bytes of Responsive CSS

#23
post #11
post #5

It's ironic that the author chose to use a page that loads 1.5Mb of data, including 12 separate stylesheets, to write about a minimal stylesheet.

Yep ... the first thing I did was to see if he was "eating his own dog-food". As an aside, I'd recommend against putting the linked site on a projector at work (or at least look at it first to determine whether it fits your organization's culture).

> I'd recommend against putting the linked site on a projector at work

Is it because of the linked site?

Re: 339 Bytes of Responsive CSS

#24
post #9
post #4

A nonoffensive version of "better motherfucking website"?

Ughn, I really thought that this rah-rah pseudo-masculine tough guy aesthetic was something we've collectively moved on from?

it's obvious satire and a lighthearted joke with a kernel of truth. chill :)

Re: 339 Bytes of Responsive CSS

#26
339 bytes which load an additional 241 bytes of CSS to load a 53k custom font...

What is the point people are trying to make with titles like this? It's like claiming "50 bytes to make a website" after you figure out that you can just iframe Google.

Re: 339 Bytes of Responsive CSS

#27
post #11

Earlier quoted context omitted.

Yep ... the first thing I did was to see if he was "eating his own dog-food". As an aside, I'd recommend against putting the linked site on a projector at work (or at least look at it first to determine whether it fits your organization's culture).

> I'd recommend against putting the linked site on a projector at work Is it because of the linked site?

It's because of the linked example in OP's link: https://blog.koley.in/baserock/

Re: 339 Bytes of Responsive CSS

#28
post #11

Earlier quoted context omitted.

Yep ... the first thing I did was to see if he was "eating his own dog-food". As an aside, I'd recommend against putting the linked site on a projector at work (or at least look at it first to determine whether it fits your organization's culture).

> I'd recommend against putting the linked site on a projector at work Is it because of the linked site?

Yes, definitely. He's talking about [0]. It's really unprofessional (which is a pity because it's impressive!)

[0] - https://blog.koley.in/baserock/

Re: 339 Bytes of Responsive CSS

#29
post #11

Earlier quoted context omitted.

Yep ... the first thing I did was to see if he was "eating his own dog-food". As an aside, I'd recommend against putting the linked site on a projector at work (or at least look at it first to determine whether it fits your organization's culture).

> I'd recommend against putting the linked site on a projector at work Is it because of the linked site?

@purerandomnesss OP here. Copied that from http://bettermotherfuckingwebsite.com/

I think, I should probably change the text.

Re: 339 Bytes of Responsive CSS

#30
post #9
post #4

A nonoffensive version of "better motherfucking website"?

Ughn, I really thought that this rah-rah pseudo-masculine tough guy aesthetic was something we've collectively moved on from?

i still have not. "pseudo-masculine tough guy" aesthetic are efficient, especially for learning/reading space (80% of my time spent on the net). It does not have to be as ugly as "better fing website", but still.
Post reply on HN