News for hackers. Stuff that matters.
Re:Resource Hints for Modern Browsers by amelius on Thursday September 10, 2015 @07:48AM (#10197460)
I'm wondering why W3C is using some limited declarative "language" instead of the more powerful Javascript to figure out these hints.
Re:Resource Hints for Modern Browsers by drdaeman on Thursday September 10, 2015 @08:04AM (#10197528)
Sanity reasons, I suppose. One does not need to run a program in Turing-complete language just to express something as simple as few weighted sets.
Re:Resource Hints for Modern Browsers by wtbob on Thursday September 10, 2015 @10:07AM (#10198084)
Wow, Poe's Law strikes again. Are you making a joke or are you serious?
Re:Resource Hints for Modern Browsers by amelius on Thursday September 10, 2015 @02:56PM (#10199866)
I wanted to make clear that I was serious, but there is no seriousness punctuation, only irony punctuation [1]

[1] https://en.wikipedia.org/wiki/Irony_punctuation

Re:Resource Hints for Modern Browsers by wtbob on Friday September 11, 2015 @01:44AM (#10202180)
Well, then see drdaeman's response. There's no reason to add anything more which requires JavaScript unless there's absolutely no alternative.

Otherwise, why not just serve up a blank page which executes JavaScript to add characters one at a time?

Re:Resource Hints for Modern Browsers by SimeVidas on Thursday September 10, 2015 @12:47PM (#10199137)
These hints can be placed inside the HTTP response header. A JavaScript API can only be used via `<script>`, which can only appear on the page (after the HTTP response has arrived).
Re:Resource Hints for Modern Browsers by mccr8 on Thursday September 10, 2015 @11:45AM (#10198713)
Off-hand, I'd guess you can use these hints earlier in the loading process than you could start executing JS.