@drahardja I've seen plenty of corporate dysfunction from the inside to know people are dumb at scale, but Google's issues with naming and re-releasing shit is still so bad it's inexplicable to me.
It can't just be "people want to get promoted" or whatever has been the ongoing narrative. It needs to be deeper. At this point, it HAS to be intentional in some baffling way. No sane leadership should approve this sort of move over and over.
- In the above video it works super duper fast because removing an audio track is basically just a copy. Other things usually take longer. - Files are not uploaded anywhere. Your content NEVER leaves your computer. It's all processed on the client side. - There's no user tracking, scripts, Google fonts, etc. A bunch of JS, but mostly local; the only exception is the FFmpeg wasm, which comes from unpkg.com (it's 31mb, too scary to host myself). - No AI! (that's a feature)
Use FFmpeg recipes without fiddling with the command line!
Consider this an early beta. There's still a ton missing:
- Ability to tweak the command line (i.e. hand editing, or selectors) - Proper mobile styles - About, disclaimers, etc - Many more command recipes - Better accessibility - "Bug fixes and performance improvements"
Programmer of visual things living in Brooklyn, NY.Brazilian, father, interpolation enthusiast, professional amateur, runner.Doing AR glasses stuff at Meta Reality Labs. Hitting your eyeballs soon(ish).Posts probably related to #programming, personal #gamedev side projects, #rust, #xr, #running.All views my own, but feel free to have them too!