Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Write HTML Like It's 1999

bradleytaunt.com

Post reply on HN
Print view View original

121–130 of 191 posts

Re: Write HTML Like It's 1999

#121

Post by lultimouomo »

_bxg1 wrote: post #93
doc_gunthrop wrote: post #91

Earlier quoted context omitted.

> Content being heavily reliant on JavaScript “injection” Salient point right here. Being served a blank white page (when JS is disabled) can deter a person from ever visiting a site again. Some peope out there want to vet a site before allowing it to run arbitrary code on their machine.

> run arbitrary code on their machine That's a bit of an exaggeration. JavaScript is strongly sandboxed and has a pretty good permissions system. The only malicious things it can really do are 1) based on cookies or 2) crypto mining. Personally I think it's unreasonable to expect today's sites to work without JavaScript completely. The real benefits of using it sparingly are: - Pages load faster - Pages are more resp…

> JavaScript is strongly sandboxed and has a pretty good permissions system

We now live in a post-Spectre world. I don't think a sandbox means all it meant in 2017.

Re: Write HTML Like It's 1999

#122

Post by cameronbrown »

SquareWheel wrote: post #119
JustSomeNobody wrote: post #95

Earlier quoted context omitted.

Sadly, the majority of web devs don’t give a rat’s butt about those users.

All they do is complain, make special demands, then go on to block ads anyway. It makes it hard to care about those users.

Seems that ad-blocking has made ads worse.

Re: Write HTML Like It's 1999

#124

Post by quickthrower2 »

Any reason it is bad to use divs with aria attributes over for a radio button choice? Because radio buttons are a pain to style and require all sorts of hacks to look nice. And in a real job you sometimes get asked to brand things, not just let the default styles come through.

Re: Write HTML Like It's 1999

#126

Post by lstamour »

majewsky wrote: post #117
arendtio wrote: post #112

While I agree that semantic HTML is a nice thing, I am also confused because the HTML I saw in 1999 didn't look like what the author suggests. If I am not completely mistaken, nav is an HTML5 element that didn't even exist back then. Instead, we used tables inside tables insides tables inside iframes to structure our navigations. CSS was still some mystic magic that only a few wizards knew how to use effectively. And…

> tables inside tables inside framesets FTFY

I was just about to say that. I also found that a surprising number of sites that used framesets would also embed midi files as entertainment...

Re: Write HTML Like It's 1999

#127

Post by snek »

Using the correct semantic element goes a huge way for people using screen readers and other assistive tech. One of the things I hate most about react/vue is how casually people use divs for everything from inputs to images. Over 20% of people use some assistive tech, whether that be zoom, contrast controls, screen readers, etc. Even if you can't test all this, being aware of it when building/coding is a huge step forward.

Re: Write HTML Like It's 1999

#128

Post by hestefisk »

I hope there will be a return to simple web pages where HTML is used for content, not apps. That’s the way the web was intended. Web assembly is nice and all, but it does smell an awful lot like Java applets in 1997. Proprietary, slow and hard to grok.

Re: Write HTML Like It's 1999

#129

Post by tuespetre »

quickthrower2 wrote: post #124

Any reason it is bad to use divs with aria attributes over for a radio button choice? Because radio buttons are a pain to style and require all sorts of hacks to look nice. And in a real job you sometimes get asked to brand things, not just let the default styles come through.

No, not unless you are for some reason doing something the intended audience’s browser may not support
Post reply on HN