ogv.js VS ruff

Yeah, that's what they do using this https://github.com/brion/ogv.js/

I've been told this at least three times now on HN over the years (pretty soon I'm going to start keeping a list of URLs so people know I'm not exaggerating.) Every single time it turns out that it isn't actually true.

It was added to desktop Safari. iOS Safari supports VP9 only in WebRTC. It may have changed, but I can't find any evidence that it has.

If you see it working somewhere, it is almost definitely using the polyfill[1].

[1]: https://github.com/brion/ogv.js/

I found a library "ogv.js" that says it decodes .ogg/.webm using WebAssembly, and this demo plays on my iPhone SE3 in Safari.

I believe Wikipedia has resorted to polyfilling it using this:

https://github.com/brion/ogv.js

That's great and all, but it has limitations, and obviously, is ludicrously less efficient than it should be.

We already have JS/WebGL video decoders (e.g: Broadway.js, OGOV.js). Much of the earlier video playback/acceleration work was getting it accelerated on GPUs-- using DirectX, OpenGL, or other GPU programming standards.

This is great and overdue. Hopefully all major browsers will add some support for open source/royalty free codecs.

Emscripten/WebAssembly actually worked rather well with audio (OPUS is just awesome) but when it comes to video it's just unfeasible, especially if you are looking at doing low latency streaming. That said, I cannot fail to mention the incredible effort done by ogv.js [1] to make a/v decoding possible almost anywhere.

Looking forward to experiment with this new API.

[1] https://github.com/brion/ogv.js/

Ruff is an open-source Python linter created by Astral Sh that stands out for its impressive speed, adaptability, and wide-ranging features.

Leverage Python Tools: Tapyr takes advantage of Python’s ecosystem tools, including ruff, pytest, and others.

I think I mention this all the time when this comes up, but I learned the most 'best practices' through using ruff.

https://docs.astral.sh/ruff/

I just installed and enabled all the rules by setting

Ruff is a Python linter that helps to identify and remove code smells. Over 700 built-in rules: Ruff includes native re-implementations of popular Flake8 plugins, like flake8-bugbear. And also built-in caching to avoid re-analyzing unchanged files.

Because the Python's "ast" modules is too slow, and lacks proper "format" feature (it has unparse but it removes comments, and forgets the current style completely). I use "ruff" a lot (https://github.com/astral-sh/ruff) which is in Rust. But I want to be able to implement fast custom linters in Go (linters that ruff / fixit lack, and Python linters lack or are too slow).

I think it’s interesting that rye uses ruff (https://github.com/astral-sh/ruff) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.

I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.

Adding more weight to ease of setup and configurability, the choice came down on flake8. It is easy to integrate, since its also available through pip and let’s you configure which standards you want to omit by simply stating them as a list via the --ignore switch. Moving to ruff appears quite smooth, so future updates may do so.

I confess I stole the pip recipe from Charlie :D

https://github.com/astral-sh/ruff/blob/main/.github/workflow...