Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Slashdot Deals: Cyber Monday Sale Extended! Courses ranging from coding to project management - all eLearning deals 20% off with coupon code "CYBERMONDAY20". ×

Comment Re:This is not news (Score 1) 165

An test aiming to measure support for modern "html5" should not award bonus points for non-standard (speech apis)

Webaudio is a W3C standard.

At issue are the speech (sythesis+recognition) API's, not the audio API's. However...

outright rejected features (websql).

In fact it does not award points for it: it is listed, but its inclusion does not award any points. Firefox does not have it and it still gets 35/35 points in that test.

You're right - I was mislead by the fact that the feature is listed as providing 5 points, but that seems to be in error. The same also goes for speech api's incidentally.

The test isn't as bad as it seemed at first glance (though it's unfortunate that it's unclear what counts for what). Nevertheless, it counts proposed and experimental features, and misdetects at least keygen (which doesn't bode well for others), fails to do even basic validation whether a feature is implemented correclty, and it doesn't clearly make the distinction between html5 and the living spec, going so far as to link to the w3c spec for features like datetime inputs, even though that's not in the spec, but is in the whatwg living spec (from which likely later iterations 5.1 will emerge). It largely follows the living spec, but not everywhere (e.g. keygen, as you point out.)

In short: it's still not a good idea to read anything much into these numbers.

Comment Re:What's for cows (Score 1) 165

You're quoting out of context. What you say is true, but doesn't affect the validity of my argument that html5test is poorly designed.

Note that if you're going to exclude the living spec in an attempt to rationalize html5test's behavior, be aware that many features it checks for aren't present in the static html5, only in the living spec.

Comment Re:HTML5Test is not a test of standardscompliance. (Score 1) 165

There are multiple perspectives here. As you point out, keygen wasn't always deprecated, and it hasn't been removed from the standard yet. So, as you point out, it's OK for a browser to support that. And I totally agree with that.

But also look at the context - the suggestion here is that a low score means a browser that is lagging in standards support. And that's clearly misleading. There may be nothing wrong with supporting keygen; but clearly the aim is to *remove* it, and there should certainly not be anything wrong with actually doing that. I understand that webkit+blink need to deal with a lot of legacy, but we shouldn't be cheering that on, just like we weren't cheering on all the IE6 quirks that lingered for years on the web.

If html5test wants to promote a modern, standards compliant web that keeps up to date with the standards - and clearly that *was* once its aim - then it too should deprecate keygen. It's understandable to support keygen (and if you do - follow the deprecated standard). But it's best to move on and drop support.

Incidentally, evaluating keygen due to this conversation leads me to question html5test even more - I tested keygen in chrome+firefox+edge, and it actually works in chrome and firefox, even though html5test suggests it works only in chrome. In other words, the test isn't just misguided, it's buggy too...

Comment Re:What's for cows (Score 1) 165

The keygen feature has been deprecated. It's likely edge will support more open formats in the future:, including opus+vorbis.

Between firefox, chrome and edge, I'd suggest that today it is chrome that has the greatest support for non-standard features, tracing back to the hastily designed extensions to webkit for the early iphones. In particular many non standard things like speed synthesis and recognition are only on in blink/webkit, as is WebSQL (which, to be fair, was at least once proposed as a standard, even though it was rejected). Those three features alone account for a 15 point headstart (17 if you count keygen) that chrome has over edge+firefox, even though their support should if anything, decrease the score.

It's no coincidence than non-webkit browsers started supporting -webkit- prefixed css properties - webkit has included a large amount of non-standard extensions over the years. Edge's declared preference for feature toggles (and firefox I believe prefers those too, exposing speech api's only if an about:config flag is set for instance) is friendlier to standardization because it means that non-standard features do not become entrenched and hard to fix.

If anything, a high score in html5test means a non-standard browser. Just take a look at the actual features where the major browsers differ and that amount to chrome's advantage - almost all of them are experimental, entirely non-standard, deprecated, or rejected. Why exactly should that count as standards compliant?

Comment Re:Benchmarks... (Score 1) 165

Well, sunspider certainly doesn't have the most reliable name:

Don't read too much into sunspider scores. Octane v2 isn't perfect either, but it's a lot better. Mozilla's kraken is probably even better, but it's much more focused on what CPU-intensive JS can do than on what normal JS actually does. I wouldn't call it a general purpose JS benchmark.

Comment Re:This is not news (Score 1) 165

Despite what the summary may suggest, there's no evidence presented that edge lacks standards compliance or indeed that chrome leads in standards compliance. The test used (html5test) isn't a test of standards compliance nor of html5; it's simply a large grabbag of features some of which happen to be defined in html5 - and those features aren't even really tested for, they just use feature detection. Many of those features are experimental (i.e. it's probably better if a browser *doesn't* support those without a feature toggle or prefix), and a few are deprecated or even rejected.

html5test should probably be renamed webkit-as-of-2013-test. As is, higher scoring browsers aren't more standards compliant, they simply include more legacy and experimental features (i.e. are *less* standards compliant).

Comment HTML5Test is not a test of standardscompliance. (Score 3, Informative) 165

HTML5test is not a test of standards compliance; the title is misleading. It's a wishlist of features, some of which are standardized, but many of which are not (or are not part of HTML5). For example, html5test doesn't (in general) test whether you've really implemented a feature correctly (or really - at all) it just uses feature detection to check whether you've claimed to implement a feature. Fortunately, browsers are never buggy and this distinction doesn't matter.

Then, html5test follows the whatwg's "living standard" instead of the less-cutting year-old actual standard html. This makes sense at first glance - we want to know which browsers support "new" features too! As a developer, that's great. As a score for a browser, that's questionable. Many features are added to the standard because one of the browsers initially experimented with a non-standard extension; lately that's been webkit/blink due to the mobile push, but previous names have included IE6. By *intent* the whatwg living spec is a few steps ahead of the browsers. What this means is that if you use this as a score is that you're going to penalize whoever is following the spec, and promote those leading the spec. That deserves at least a separate score.

Then, there are HTML5 features that are deprecated, like . The continued support for scores chrome two points, and edge+firefox none. Is that really what you wanted to know? I bet there are *lots* of deprecated features in old IE; if you're going to start counting those...

Then there's features like speech synthesis and recognition. Those aren't part of the spec, have never been part of the spec, yet they're worth 5 points together. Or worse, the Web SQL features, that have explicitly been rejected, also worth 5 points (only webkit-derived browsers support this).

Almost all of the point differences between browsers can be explained by features that are experimental, deprecated or rejected.

In short: don't use html5test. It's pointless.

Comment Re:Not useful without more data (Score 2) 97

Many laptops have a battery preservation mode which avoids full recharges. Long term storage (or worse, usage) at 100% capacity is damaging to a lithium ion battery, so limiting charge capacity to (e.g.) 50% the lifetime can be dramatically extended. It helps in any case, but it's particularly useful if your laptop is usually plugged in. Unfortunately, this feature is often hidden away somewhere, or requires an extra download - almost nobody uses it, which is a shame.

Comment Re:so, I'm in the more than 8 yrs ago camp (Score 1) 391

I've got a similar rig, but I'm using the seasonic 400W platinum power supply. It's similarly priced, but it's entirely fanless, and more efficient at typical loads. With just the iGPU, the machine - overclocked and overvolted - still only uses around 20W, which is just next to nothing. At full load it's not much over 100W, and you need to load the GPU and use AVX to even get it to 100W. It's enough for even fairly high end single card GFX builds, and, of course, it's silent.

I use the thermaltake HR22 CPU cooler, which is also fanless (If you want high overclocks, you can always add a fan).

Comment Re: meeses (Score 1) 361

The Performance MX really is brilliant - works on almost any surface; wireless with good range (I use it as a remote, too); rechargable but you can continue using it while charging since it just means plugging in a usb cable - brilliant!

Those who claim the dead never return to life haven't ever been around here at quitting time.