Actually, the AR-15 was a 5.56mm version of the 7.62mm AR-10, not the other way around.
Slashdot videos: Now with more Slashdot!
Still typically comes in at or above a buck a round. Not cheap stuff.
I own an early 1940s-vintage version of this rifle, and it's a solid piece of gear.
Nobody said it was.
1300VA Smart-UPS, Dell T110, Dell R210, Dell Optiplex 790 (Plex media server), Couple of Dell CS23. Network is Motorola SBR, HP T5740 running pfSense, Aruba IAP-225 (802.11ac), HP 2915 10-port PoE switch, Ubiquiti PicoStation feeding into Ubiquiti toughswitch to remotely connect printer and Ooma for home phone. Office phone is Yealink T38G.
Also have a couple of servers offsite in real datacenters and on EC2 and Azure.
I too have had really bad results with IPv6 (TunnelBroker) when connecting to anything Google. You would think that Google of all companies would have their IPv6 poop in a group.
Who are you saying is "against" HTML5? DASH-IF? It's a complementary technology, not a competing one. There's no "contractual" issue here. Netflix hasn't switched to DASH until very recently because the technology hasn't been fully developed until very recently. There certainly wouldn't be a contractual obligation for members of the forum to use non-DASH technologies, that would be absurd.
Correct, in order to use RTMP, you must use Flash (as I mentioned in the original post - HTML5 doesn't preclude using a Flash object). There are players such as JWPlayer that do an excellent job of using HTML5 media objects if supported and falling back to Flash if they're not, in order to provide a seamless experience to the end user (but Android is still a mess).
DASH is going a long way towards fixing the mess, but it's still very early in that lifecycle. One of the really neat things about it is that the manifest makes available a list of what video and audio segments are available (and what codecs, bitrates, etc), and the client picks what it needs based on its capabilities. If a DASH manifest makes available a 2.0 stereo audio track at 128Kbps, a 5.1 surround track, a 7.1 surround track, and a 22.1 surround track (don't laugh, 22.1 is part of the upcoming 8K spec), along with a 4K video track and various resolutions and bitrates below that, it will pick whatever's appropriate for your hardware - playing on a mobile device over headphones? Player will pick whichever video track is appropriate for your screen/bandwidth and the 2.0 stereo. Output via HDMI from the same device? Switch the audio over to the surround. And so forth.
It's not used widely at all - it was useful in the days of multibitrate audio-only streaming (it's been around for ever) but I haven't encountered it in any of the modern streaming server platforms.
Microsoft is a charter member of the DASH industry Forum (along with Adobe and Netflix and a few others) and is really pushing DASH (if the hype is to be believed, it's the Second Coming). That said, it has a lot of very useful technical benefits over silverlight or HLS.
The main reason they used silverlight is that of all the ways of streaming content, Silverlight has the most robust DRM support. It's been said that MPEG-DASH combines the best of HLS and Silverlight into an open protocol - namely, HLS' ease of use with Silverlight's robust DRM. HLS has decent DRM support as well, but it's still a proprietary Apple protocol (a "standard" in the Sony sense of the word: because they say it's a standard)
It's not a matter of what browser it THINKS you have, it's a matter of the browser supporting what you need to stream encrypted MPEG-DASH.
Chromecast also supports DASH.