My Current HTML Boilerplate

Re:My Current HTML Boilerplate by nathell on Tuesday April 27, 2021 @04:25AM (#26953423)

I won't. Under my definition, it causes the page to stop being a document and start being an application. Being able to detect JS can be useful sometimes, but, to me, it doesn't belong in a boilerplate.

http://blog.danieljanus.pl/2019/10/07/web-of-documents/

[ Parent | on HN ]

Re:My Current HTML Boilerplate by weird-eye-issue on Tuesday April 27, 2021 @11:31AM (#26957301)

The web is moving on without you.

Edit: Your blog doesn't even use SSL...

[ Parent | on HN ]

Re:My Current HTML Boilerplate by spookthesunset on Tuesday April 27, 2021 @12:07PM (#26957835)

The “documents not applications” battle is like 10 years old at this point. The web moved on a decade ago...

I’ve had the “how to deal with folks who disable JavaScript” discussion for well over 10 years and the answer in every shop I’ve worked in has always been the same... don’t bother. And it was the developers themselves making that call, not the “business people”.

[ Parent | on HN ]

Re:My Current HTML Boilerplate by weird-eye-issue on Tuesday April 27, 2021 @12:12PM (#26957916)

Yeah I was being nice. It moved on so long ago I'm not sure how he calls himself a developer. Okay there... I said it.

[ Parent | on HN ]

Re:My Current HTML Boilerplate by milkey_mouse on Tuesday April 27, 2021 @02:00PM (#26959268)

Sometimes "the industry" "moves on without" a valuable perspective. That doesn't mean those "left behind" (e.g. Richard Stallman) should give up. Something something "marketplace of ideas."

But yeah, GP, get a Let's Encrypt certificate for the sake of your readers!

[ Parent | on HN ]

Re:My Current HTML Boilerplate by nashashmi on Tuesday April 27, 2021 @02:12PM (#26959412)

OT :

What http site is left we can go to when isp or WiFi greets with a welcome login page. Going to https sites gives an error.

[ Parent | on HN ]

Re:My Current HTML Boilerplate by ziml77 on Tuesday April 27, 2021 @02:40PM (#26959776)

http://neverssl.com or http://detectportal.firefox.com/canonical.html

[ Parent | on HN ]

Re:My Current HTML Boilerplate by deathanatos on Tuesday April 27, 2021 @08:00PM (#26963712)

ISPs & WiFi APs can stop trying to attack connections like that, and implement RFC 8910[1].

Otherwise… example.com, maybe. I guess we'll see how long the http version of that lasts.

I assume ISPs will get around to this a few decades after implementing IPv6.

[1]: https://tools.ietf.org/html/rfc8910

[ Parent | on HN ]

Re:My Current HTML Boilerplate by krazerlasers on Tuesday April 27, 2021 @04:26PM (#26961069)

You are welcome to use my site: http://krazerlasers.com

You are also welcome to use my html boilerplate:

  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
  "http://www.w3.org/TR/html4/loose.dtd">
  <html><head>
  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  <link rel="stylesheet" type="text/css" href="blue-white.css">

[ Parent | on HN ]

Re:My Current HTML Boilerplate by depressedpanda on Tuesday April 27, 2021 @02:38PM (#26959751)

http://example.com/

[ Parent | on HN ]

Re:My Current HTML Boilerplate by cjohansson on Tuesday April 27, 2021 @03:50PM (#26960615)

"You can't argue with popularity. Well, you could, but you'd be wrong!" - Robbie Williams

[ Parent | on HN ]