Earlier quoted context omitted.
Reminds me of http://motherfuckingwebsite.com and http://bettermotherfuckingwebsite.com But the key, underlying point to ALL this stuff is that you do NOT NEED TO WORRY ABOUT PRESENTATION until you have the CONTENT. A huge temptation is to spend hours and hours tweaking the presentation as a way of avoiding actually creating the content; this is the real danger. (should mention https://thebestmotherfucking.website of…
> 7 fucking declarations. That's how much CSS it took to turn that grotesque pile of shit into this easy-to-read masterpiece. Such drastic difference with basic adjustments, damn
All you may need is HTML
141–150 of 328 posts
Re: All you may need is HTML
#142Earlier quoted context omitted.
> Good information design, clear visual hierarchy, accessibility, etc. all help with communication Isn't that what HTML gives us?
Well, that was what HTML was on track to give us. But once JS and CSS were introduced, semantic HTML that was actually semantic stopped developing, under the assumption that if someone needed, for example, a tab area or slide show, they could develop those themselves with CSS/JS. What we've gotten instead is extremely vague elements like "section" that don't communicate what the elements are . If HTML were truly sema…
Re: All you may need is HTML
#143I'm still using Dreamweaver 8 for some old sites. I have to run it under Wine emulation now, but it still works. It still does a good job of layout.
Is there a more modern round-trip HTML/CSS tool?
Re: All you may need is HTML
#144Some years ago I was interviewing for head of automation position, and in the process was asked how'd I go about making sure a Web admin interface (to a product that by and large doesn't need a Web interface, think, in the same category as Kubernetes) is well-tested. To which I responded that I'd not use any JavaScript. Ideally, XML with stylesheets. Very light-weight, renders extremely fast, and is extremely friendl…
If you even find new devs who'd want to work on this. Who wants to acquire very niche domain knowledge that you can't apply anywhere else?
Re: All you may need is HTML
#145Re: All you may need is HTML
#146I don’t get this argument. As a reader, I’m used to the monospace font of my OS because it’s the one I see everywhere. I don’t care at all about the fonts users of other OSes see. This custom font makes _your_ experience consistent, not the readers’.
Re: All you may need is HTML
#147I sympathise with the main thrust of the post but, to nitpick, this is just plain wrong: > But mostly css appeals to our vanity and ego. Design isn't just about aesthetics. Good information design, clear visual hierarchy, accessibility, etc. all help with communication. The author's effective use of spacing, bold, and code tags show us that they know this intuitively, despite what they write.
Message / medium have always mixed together.
Even folks who say content needs to be figured out before presentation... it's not so cut and dry. Your medium shapes your message - they are not mutually exclusive and for the receiver of the message, the medium matters for their reception of the message.
I understand the sentiment that TONS of CSS is probably a bad use of time. But trying to demonize or otherwise attach aesthetics the label of "meaningless" is, in my opinion, just as much egocentric as they claim CSS to be.
Re: All you may need is HTML
#148Earlier quoted context omitted.
Well, that was what HTML was on track to give us. But once JS and CSS were introduced, semantic HTML that was actually semantic stopped developing, under the assumption that if someone needed, for example, a tab area or slide show, they could develop those themselves with CSS/JS. What we've gotten instead is extremely vague elements like "section" that don't communicate what the elements are . If HTML were truly sema…
I agree with you, but also I think the section tag is one of the biggest leaps forward we've had. Putting an id on a whole section instead of a name= crap for references, and actually using nesting for hierarchy. All the HTML5 input types are also an example of semantics impriving. It could be way better, but it's not a total stalemate
How does this differ from how was being used before?
I've switched to using simply because it's a better name, but I'm not sure it's made any meaningful difference in my code.
Another example of the pointlessness of this issue is and . I've rarely seen code where these weren't used exactly the same as and were before. In rare cases, I've seen someone do something like make a different color rather than italic, and that's almost always been a bad idea, because when HTML authors use they almost always intend for it to be italic. In fact, I'd say we should just continue using and because those communicate intent better, but at this point I've worked in too many codebases that decided that could be hacked to mean "icon" (i.e. using FontAwesome) which is a horrible, awful, no-good, bad, hack. > All the HTML5 input types are also an example of semantics impriving. It could be way better, but it's not a total stalemate That's true, but I think we'd be moving forward a lot more quickly if we weren't devoting most of standards development resources toward giving companies more fine-grained control of our browsers through CSS/JS.
Re: All you may need is HTML
#149Earlier quoted context omitted.
Reminds me of http://motherfuckingwebsite.com and http://bettermotherfuckingwebsite.com But the key, underlying point to ALL this stuff is that you do NOT NEED TO WORRY ABOUT PRESENTATION until you have the CONTENT. A huge temptation is to spend hours and hours tweaking the presentation as a way of avoiding actually creating the content; this is the real danger. (should mention https://thebestmotherfucking.website of…
Wow, thanks for those links! No joke; the CSS on the better site is literally going to become my default CSS from now on.
tags if you are going to be like that.
If the whole point of your website is to brag about code to accomplish reasonable formatting.... can we at least have code formatting? I think I have enough bandwidth to afford some line breaks.
Client side GA????
Re: All you may need is HTML
#150Pretty much all the sites are now a days single page or with tons of JavaScript with a lot of xhr requests. Those xhr requests are huge too. Loading screens everywhere. Some of the loading screens are 5-7 seconds long.
And I have no luck with banks sites. They put a lot of efforts to block access.