The abstraction and generic design is part of the point, though. It's not really about writing concrete examples, but experiences and how to be ready to structure based on those experiences.
Very strange take. A lot of software is built on trust and the people behind it. Hence why the social aspect of Github was so important to a lot of open source software.
Hey, thank you for staying polite while expressing disagreement. That's much appreciated.
To the risk it might seem surprising, I actually completely agree that trust is essential to software creation and and use.
Actually I would more broadly frame it as, no trust, no viable sustainable society, no technical/cultural artifact.
But trust and societies can be realized without individualism as underlying chief paradigm.
That doesn't mean total negation of individual though. One alternative, among others yet different approches, can be state as a metaphor of individual like a cell in a social body. Thus the term metastasis, as when a cell starts to degenerate in self centric behavior at the expense of the health of the body as a whole. On the other hand, no cell, no body.
There were many other options for git and version control in general at the time, though. GitHub made the onboarding to git much easier while using the platform as a social tool.
I love my Brompton. I've had mine for 12 years that I bought back in LA and brought it with me when I moved to Tokyo. It's such a great commuter for getting around the city and easily fits in my trunk when I want to take it with me for a trip.
Tokyo also has a couple of great Brompton shops for maintenance and parts.
Prompting the user to install, or auto-installing FFmpeg separately, rather than bundling the binary. The problem is FFmpeg can be configured in so many ways and the general install binaries are usually LGPL compatible.
Looks good. Good work on shipping! I love seeing video applications utilizing Web Assembly. However, it usually falls short in when it comes to longer video in the browser's sandboxed environment.
How is the performance? Curious if you've tried using the FFmpeg libraries directly (libav), rather than compiling all of FFMpeg to WASM?
I always end up using running FFmpeg directly since it's faster and more reliable, but I still have some hope for a full functioning browser-based implementation someday.
Yeah you are right about the wasm issues with video apps.
The editor itself relies fully on web codecs and the rest of the tools are halfway migrated from ffmpeg wasm anyways.
I did not look into any other alternatives for ffmpeg thinking that wasm will give me the next best thing to the cli tool and ofc since the browser is the main delivery mechanism the I was limited in my options.
I have seen your project and it is really cool!
That's not true though, is what they're saying. Quake demo files are server-to-client packets, results of the simulation, not client-to-server packets, the inputs.
If you wanted to add random critical hits and random bullet spread based on the pixels in a live feed of a lava lamp cam, clients could still record .dem files and they would still work.
Still iterating through refinement and features. It's built on Rust + Tauri with a React frontend, in case anyone is curious.
I've created various open-source and commercial tools in the multimedia space over the last 10+ years and wanted to put it all together into something more premium.
reply