I've been running Fedora 29 on the Surface Pro 4 for a month or so now. I agree this form factor is almost perfect for a laptop. The screen and keyboard are great for coding.
I'm not sure if I'd recommend this as a primary work machine since you have to compile your own kernel to enable some of the features (touch screen, hibernation etc). Other than that it's been stable and better than I had anticipated.
Pi-hole seems to block windows telemetry domains by default. I don't know how complete the blocking is but there are a lot of domains like the ones listed in this thread on my top blocked domains list.
Interesting. Could you tell which model you have? I have had very few problems in general on my SP4 i7-16GB model. I've had to reset the device maybe once or twice in the last ~4 months.
So what's the best practice when it comes to valid html? This seems like a cool technology but trying to validate the https://www.ampproject.org/ site, the w3c validator fails so bad it's not even able to list all errors. The example post does a bit better but is still pretty far from valid html5.
Is there a way to do it in a standardised way or should that even be desired? All browsers I've tried seem to render it fine and quickly (assuming js and the normal bells and whistles).
To be honest, that was my bad--I didn't bother checking it because I know it used to fail validation a month or so ago.
Looking at it now though
[console.warn]
https://www.ampproject.org/:22:42 The tag 'noscript > style : boilerplate - old variant' is deprecated - use 'noscript > style : boilerplate' instead. (see https://www.ampproject.org/docs/reference/spec.html#required-markup)
That 'warning' comes up as a whopping great big red error for my AMP pages that still have the old boilerplate. It seems AMP make an exception for their project site.
Not sure why you're being downvoted. WebKit actually implements the WHATWG HTML parsing algorithm [1], and so do Trident [2] and Gecko [3].
The W3C HTML 4 spec didn't waste a word on parsing and simply referred to SGML [4], which (for very good reasons) no relevant browser actually implemented. Obviously, browser developers did some crazy/remarkable things before the WHATWG came along, but a lot of credit for today's lenient HTML parsing certainly belongs with the WHATWG.
