Live data from Hacker News

Solving FizzBuzz with CSS

dabblet.com

21–30 of 30 posts

Re: Solving FizzBuzz with CSS

#21
post #15

Earlier quoted context omitted.

Usually IE8 users are stuck in IE8 unless they let the OS upgrade their browser, so most of the users that started with IE8 are still stuck in 2009. Chrome/FF users tend to have less issues with upgrades.

Not to mention those of us in a workplace still using XP (and thus unable to upgrade past IE8).

All horrible arguments. "Stuck?" Download a real browser.

IE8 viewers expect devs to slow progress or cater to them would be like horse and buggy drivers from days of yore lobbying to prevent cars from going faster than horses.

Stop complaining, get off your horse and get a (free) car. Encourage your clients to do likewise.

Re: Solving FizzBuzz with CSS

#22
post #21

Earlier quoted context omitted.

Not to mention those of us in a workplace still using XP (and thus unable to upgrade past IE8).

All horrible arguments. "Stuck?" Download a real browser. IE8 viewers expect devs to slow progress or cater to them would be like horse and buggy drivers from days of yore lobbying to prevent cars from going faster than horses. Stop complaining, get off your horse and get a (free) car. Encourage your clients to do likewise.

Corporate environments sometimes lock down their computers completely, and don't give admin/install privileges, let alone OS updates.

So yes, "stuck".

Re: Solving FizzBuzz with CSS

#23
post #22
post #21

Earlier quoted context omitted.

All horrible arguments. "Stuck?" Download a real browser. IE8 viewers expect devs to slow progress or cater to them would be like horse and buggy drivers from days of yore lobbying to prevent cars from going faster than horses. Stop complaining, get off your horse and get a (free) car. Encourage your clients to do likewise.

Corporate environments sometimes lock down their computers completely, and don't give admin/install privileges, let alone OS updates. So yes, "stuck".

good thing you don't need to install chrome to run it then!

Re: Solving FizzBuzz with CSS

#25

Goes to show how many (greatly needed) programmatic features CSS is adding. Also shows that some people love a creative way to attack a problem.

As God is my witness, CSS will need to be split into a presentation language and a logic language. /s

You know, that’s not such an outlandish claim. CSS is accumulating features that seem to me completely out of place in a styling language. Then again, HTML isn’t perfect, nor JavaScript, nor PHP or any language—but we still get stuff done with them, so who am I to complain?

Re: Solving FizzBuzz with CSS

#26
post #13
post #3

Correct me if I'm wrong, but I don't believe you need any of the :not statements, and instead or (3n) and (5n) you can just use 15n for the 'fizzbuzz'. The cascade of the CSS will take care of the cases the div is a 'fizzbuzz'. Sorry I can't post the example, Dabblet is working strangely for me this morning. CSS that should work: /** * FizzBuzz with CSS */ body { counter-reset: fizzbuzz; } div { width: 100px; height:…

This should also work: div:nth-child(3n):after { content: ""; } div:nth-child(3n):before { content: "fizz"; } div:nth-child(5n):after { content: "buzz"; }

Brilliant.

Re: Solving FizzBuzz with CSS

#30
post #22
post #21

Earlier quoted context omitted.

All horrible arguments. "Stuck?" Download a real browser. IE8 viewers expect devs to slow progress or cater to them would be like horse and buggy drivers from days of yore lobbying to prevent cars from going faster than horses. Stop complaining, get off your horse and get a (free) car. Encourage your clients to do likewise.

Corporate environments sometimes lock down their computers completely, and don't give admin/install privileges, let alone OS updates. So yes, "stuck".

The dev community should not be at the mercy of incompetent sysadmins. Evolve or die. Such is life. Such is business.
Post reply on HN