RBO2

These are good points but no name is ever perfect. Just felt that secc was more memorable and would offer more levarage to this great project :-)

Why not call it secc ("sexy") ?

Correct. Progressive MP4 also do the trick. Many open-source tool such as ffmpeg (generalist), gpac (specialized in this and leveraging ffmpeg), etc. in the area.

I love the idea of static recompilation. It is a promising way to make statically linked code more reusable/sustainable!

I don't know who downvoted you but you're correct. The point is that most devices embed an HEVC hardware decoder.

I agree with you but hey JPEG also had its own patent issues (https://en.wikipedia.org/wiki/JPEG#Patent_issues).

HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration.

HEIF is made by MPEG. HEIG is extensible (see AVIF fusing the AV1 royalty-free codec). Also an application format (MIAF) will ensure interoperability.

While waiting for native browser support, some js implementation would do the job.

What else?

How different is this from Chromium and Chrome?

Note that this is a Apple requirement for HLS. Most people don't realize that the GOP size doesn't impact the latency, but it impacts start-up time.

> I've heard from colleagues that this won't be possible with DASH due to the switch to fMP4 format.

That's incorrect. With DASH the latency depends on the fragment duration, not the segment duration. You can start sending the segment when its first fragment is generated, and use chunk-based HTTP transfer as mentioned in other comments.

Link for further details on low latency: https://www.gpac-licensing.com/2014/07/09/lowering-dash-live...

I think they're almost there in two ways. 1) is https://github.com/gpac/gpac/issues/790. 2) is to extend FFmpeg to include the MP4Box muxer: http://www.gpac-licensing.com/signals/

Also I use ccache on all my projects. Rebuilds times are now at 10s for a 50 kloc project.

Unfortunately these codecs still have a few important issues (http://www.gpac-licensing.com/2016/07/12/vp9-av1-bitstream-f...). I wish AV1 can fix those but they want to go for such a tight timeline...

That's mostly partial acceleration. Chips now support a lot of codecs. And aside H264/AVC chips makers cannot afford to use so much hardware surface for codecs that are not so popular.

Agreed. Some opponents of DRMs say this is the beginning of the end of open computers. We've heard recently about the Intel Management Engine.

On the other hand, almost all DRMs were broken because the content is available in clear: http://betanews.com/2016/06/26/chrome-drm-streaming-video-fl... https://iseclab.org/media/uploads/zotero/Steal_This_Movie_-_...

You're right, I meant "contributors". It is not only a question of money: these companies can dedicate people to lead the standardization tasks and push their own interests. That's mostly visible at MPEG with patents (yet another hot subject).

Standards are very important. But the way we make them is still highly improvable.

Agreed. That's one of the reason why this initiative stalls. However the back idea is to standardize a DRM protocol that would be accepted by the copyright owners and that's a step in the right direction.

> the organizations that develop the most influential browsers do

The problem here is that 3/4 browser makers are also DRMs makers (Apple, Microsoft, Google) and are also the biggest W3C donators.

W3C did this move because its biggest sponsors are the DRM makers (Google, Microsoft).

To make it acceptable they made it optional. But in practice all major browsers implemented it.

The right answer is now to standardized the W3C CDM black box by standardizing DRMs as ETSI has started (https://lists.w3.org/Archives/Public/public-html-media/2014F...). W3C should contribute to this effort.

Useful link on EME: https://www.w3.org/2016/03/EME-factsheet.html

These area are huge. Switzerland is 41,285 km^2, Belgium is 30,528 km^2, The Netherlands is 41,543 km^2.

The main question is: who pays to make the standards?

W3C's biggest sponsors are corporate companies such as Google or Microsoft. It gives these companies a lot of weight.

> Scott Meyers has written lots of good stuff on how to use C++ properly.

Scott Meyers "retired" from C++ in December 2015 (http://scottmeyers.blogspot.fr/2015/12/good-to-go.html / https://en.wikipedia.org/wiki/Scott_Meyers). There may be a link to C++ itself don't you think?

PS: I still write most of my projects in modern C++, but slowly switching to D and other alternatives.

Yes that's exactly what it is about! Unfortunately, our current result shows that it still requires much time to model the spec correctly. Any help appreciated, my contact is available on the message above :)

Thanks! I'm contributing to an open-source project where we do a lot of standardization (including MP4). We're trying to improve the parser generation by using a model from the specification. We even have some funding for this. I'd be happy if we could discuss this ([email protected]). Better standards means a better world for everyone :)

Very interesting. How can we get more info on this? Is there any public code or product out there?

Why wait for Rust when D is already there?

It is not a hasard to have this kind of laws in France. France hasn't known dictatorship for long. French representatives don't know what a Stasi-like security state would look like. It would be harder to have such a law in Germany.

The low number of delegates during the vote whows how archaic the French politic system is: they are against their own party so they prefer to be missing. There is little discussion. And there is no way to make a petition in France that would go to the parliament or provoke a referendum.

France just shows how current institutions are overwhelmed by new technologies.

+1 LLVM is a background topic for me. Your newsletter is both informative and joyful on my Monday morning.