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…
personally I miss the vanilla html of the late 90s (unless advanced guis) same went for emacs I stopped using themes
All you may need is HTML
151–160 of 328 posts
Re: All you may need is HTML
#152Earlier quoted context omitted.
Apple is notorious for wanting to push people away from portable and easy-to-use web applications to non-portable, expensive to develop, and frequently worse mobile apps.
"Apple hates websites because I don't like Safari's default monospace font."
Though of course there are plenty of discontents with that. On balance I think the apps that ship with MacOS are much worse than their Windows counterparts. I think iOS on the iPad is truly superior but the settings app is dark pattern city, particularly the notification that never goes away about the Apple TV trial that is about to expire but actually expired years ago.
Re: All you may need is HTML
#153Re: All you may need is HTML
#154I have been writing some puppeteer/node js scripts to download invoices/statements and to scrap some data from different vendors/service providers. (ATT, Spectrum, Gas, electric, etc). Pretty 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 lu…
There are complications, naturally: https://news.bloomberglaw.com/banking-law/small-banks-urge-c...
Re: All you may need is HTML
#155Re: All you may need is HTML
#156I 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.
> scroll the mousewheel: giant footer section slides up taking half the viewport
> move the mouse cursor up: giant ass header slide menu drops down covering half the viewport
should be absolutely no motion on a page unless i specifically click on something, like play button or slide out button. and that includes parallax bullshit.
prefers-reduced-motion should be the DEFAULT not an override. ffs haven't we learnt anything in the last 20 years of web dev - you cant rely on web monkeys to build things right (\s).
---
and f*k you to whoever thought having mouse hover popup autoplay boxes on youtube was a good idea.
Re: All you may need is HTML
#157Earlier 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…
I was happy to see someone finally referred to the motherfucking websites. On the other hand, I was disappointed to see the unique one of those I think it is worth to follow the advice [1] was not cited. For curiosity reasons, I found out about [1] on a well-known website [2] that definitely puts content in front of presentation, even though I like their website's design. [1]: https://bestmotherfucking.website/ [2]:…
Of all of them, I think the one you linked is probably the best. It is still interesting to watch the progression.
Re: All you may need is HTML
#158Earlier quoted context omitted.
> 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
I honestly prefer the original version without css. Plain browser styles have a kind of raw beauty that it's very hard to surpass.
Re: All you may need is HTML
#159I 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.
Re: All you may need is HTML
#160Earlier 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…
This...does not match history. There was never a golden era like you describe (it was a time of conflicting philosophies, people saying "eh, let's add this, that would be sweet", and browser vendors competing to add as much as possible to out "innovate" each other and the limited specs), semantic HTML helps in some cases but is never going to give you automatic accessibility, and a one size fits all browser style is…
I've been writing web code since 1997ish, so...
> There was never a golden era like you describe (it was a time of conflicting philosophies, people saying "eh, let's add this, that would be sweet", and browser vendors competing to add as much as possible to out "innovate" each other and the limited specs)
I did not describe a golden era of HTML, because a golden era of HTML never happened. Instead, it was precluded by the introduction of JS/CSS. Had JS and CSS never been invented, we might have achieved a golden era of HTML, but we would have needed web standards to mature before that could happen. What happened was, web standards did mature, but they matured to serve websites rather than users. As a result, mature web standards center around JS and CSS, leaving HTML anemic and weak.
What we have now is a time of conflicting philosophies, with websites competing to add as much as possible to out "innovate" each other. Users still suffer the same inconsistent interfaces they did in 1997, it's just that instead of browsers being inconsistent, it's websites that are inconsistent.