iskin

Using AV1 <video> tag with a single frame is an amazing hack. Thanks for sharing.

Wow, I really wait for this release

This is great links, thanks.

What arguments can be added to FFmpeg AV1 encoding command to improve the result for browsers?

Was this dynamic optimizer framework from Netflix released already to be used in web video encoding for webpages?

Yeap. But technically, you can use WebM container (a subset of MKV) for AV1. Chrome and Firefox support it. But size is a little bigger and WebM container seems like is not really official for AV1.

> I doubt they understand the implications of the commands they're running.

I put a description for every arguments used by me in FFmpeg commands.

https://evilmartians.com/chronicles/better-web-video-with-av...

Is it not enough?

Good idea. I will change the number in the article.

Not only. It is also based on Xiph's/Mozilla's Daala and Cisco's Thor.

Hardware will support both AV1 and AV1.1 too.

I think the pirate scene will be the first, which will take AV1. They always are very advanced in terms of technologies.

AV1 is just a very new codec. You can use it in the Web for Chrome and Firefox. But it is too early to use for downloadable video files. For video files you need a OS support. Microsoft has it only in Beta. Android will support it in Q. Linux supports AV1 already.

I think in next year we will see more and more AV1 everywhere, including pirate torrent trackers.

Right now 30% of the global market uses AV1 enabled Chrome and Firefox on desktops.

Nope, you can use AV1 without waiting for AV1.1.

AV1.1 players will support AV1.

Yeap. Technically, it is encoder (a thing which generates AV1 files).

However, next-gen fast AV1 decoder (a thing which will play video), dav1d is not Rust-based.

Because of this reason, AV1 is now disabled for mobile devices.

On desktop hardware support is not critical.

Main reason to use PostCSS is not to replace preprocessor. Main revolution happens outside a syntax-sugar world right now.

This is why main reason to use PostCSS is to have non-preprocessors tools:

1. Autoprefixer.

2. Stylelint. Like ESLint, but for CSS. It will automatically find a mistakes in your CSS.

3. postcss-inline-svg, changes a SVG color when you insert it with base64.

4. CSS Modules, automatically isolate your CSS components (like auto-BEM, but with better isolation).

5. postcss-cssnext, if you are fan of CSS Custom Properties and want to use them right now (for some simple cases, of course there is no dynamic Custom Properties).

If you asked about PostCSS-based preprocessors (it is small part of PostCSS features) — there is a 2 solutions:

* postcss-cssnext, preset of CSS drafts polyfills. It is not 100% preprocessor, but because of CSS custom properties and CSS nested polyfill it could do preprocessor work. * PreCSS, preset of PostCSS plugins with Sass-like features.

I use PreCSS. It is more simple preprocessor. It has no some Sass features by design, to keep your code clean of code.

Using PreCSS doesn’t give me some addition features, just same old $style variables, nesting, mixins.

The reason why I use PreCSS — performance and compatibility. If you use Autoprefixer or Stylelint, you already have PostCSS in your build processor. In this case, why you should use other parser? PreCSS will share parsing with Autoprefixer, Stylelint and other PostCSS tools.

PostCSS will parse CSS only once and all that plugins will work on top of same AST. As result build process will be simpler and faster.

PostCSS is a framework to create a CSS tools. Preprocessors (Sass/Less) is only one type of tools that you could build on top of PostCSS.

So using PostCSS != not using Sass. You could use Sass for processors, but still using PostCSS for other CSS tools types — for Autoprefixer, Stylelint, cssnano.

I use Sass with postprocessors. They are not enemies. Sass and preprocessors are better to fix CSS syntax. Postprocessors are better for some automatically task, like autoprefixing, media queries packing, polyfills, etc.

Unfortunately, Sass is not so flexible as JS. Even simple things require a lot of code. And a lot of task is just impossible on Sass (for example, Autoprefixer, RTLCSS).

Idea behind Rework (real preprocerssor, not language) is better and more flexible https://github.com/visionmedia/rework

Unlike Ruby on Rails build-in I18n library, R18n autodetect user locale (for Rails, Sinatra and desktop apps), translate models or any objects, has flexible filters, use better locales architecture, can load translations by any way (files, database, etc) and use nice Ruby-style syntax.

Nice. I often miss error on long deploy, because I hide terminal window.