News for hackers. Stuff that matters.
Re:Abusing CSS3's nth-child selector to invent new ones by rrrx3 on Friday January 09, 2015 @05:24PM (#8864882)
Sorry, can't and won't get onboard with this. It's not 1995 anymore. Join the rest of us in the 21st century with pages that are functional and attractive.
Re:Abusing CSS3's nth-child selector to invent new ones by jenscow on Friday January 09, 2015 @06:11PM (#8865085)
and maintainable.
Re:Abusing CSS3's nth-child selector to invent new ones by graycat on Friday January 09, 2015 @10:12PM (#8865746)
It sounds like you have in mind a set of likely changes and have designed the HTML, CSS, and JavaScript to make the changes in that set relatively easy. Okay. For my Web pages, I questioned if that candle was worth a match. Or another such analogy goes, "Don't build a brick outhouse.". Or as I wrote, as simple as possible but not simpler. It's just a Web page! But that's the way I've been thinking and posted here to see where people differ in their thinking.

One possible issue is changing where the text, pictures, video clips, ads, etc. are depending on the number of pixels or whatever in the user's screen, browser window, etc. For my pages, I just decided not to do that -- I just didn't see any very big reason to do that. Or, if a user gets used to my Web pages, then they will still have the same layout -- text, text boxes, URLs, ads, links to Help, etc. on any other screen, with any other browser, etc.

Is it really important to change what the page looks like depending on the user's screen size? Or, if we know what text, ads, text boxes, etc. we want, can't we just display it, basically one way for everyone? Why so important to change? As a programmer it's more work for me, and as a user I just want it simple.