4 ms·

The latest release[1] on Github should have binaries combinations for almost everybody here. If you don't find a binary for your environment, you can probably j

The latest release[1] on Github should have binaries combinations for almost everybody here. If you don't find a binary for your environment, you can probably just run the javascript files and it'll be fine. If you are wondering why the binaries are so large, it's because they are packaged-up node.js binaries. I tried to learn a compile-to-native language to rewrite this in so you won't have to download such bloated binaries but didn't get far. I learned Swift and still have a WIP branch up for it[2]. I gave up after learning that there's no well maintained windows http server for swift. I'm currently on my journey to learn Rust. So maybe one day when I do, you'll see the binary sizes drop. [1]:https://github.com/steelbrain/ffmpeg-over-ip/releases/tag/v3.0.0 https://github.com/steelbrain/ffmpeg-over-ip/releases/tag/v3... [2]:https://github.com/steelbrain/ffmpeg-over-ip/tree/swift-lang https://github.com/steelbrain/ffmpeg-over-ip/tree/swift-lang

Cyph0n 2y ago
Go would be a good fit for this kind of application. But Rust is a great choice too. Keep up the good work!
chrisldgk 2y ago
You might be able to switch to Bun or Deno with relatively little effort and create binaries that are probably a lot smaller (and maybe also faster) with each of their compile commands [1][2]. In the end I do also believe that a compiled language like Swift, Rust or Go might be a better fit though. [1] https://docs.deno.com/runtime/reference/cli/compiler/ https://docs.deno.com/runtime/reference/cli/compiler/ [2] https://bun.sh/docs/bundler/executables https://bun.sh/docs/bundler/executables
- steelbrain 2y ago
  FWIW, `bun` produced larger output files ~/P/s/ffmpeg-over-ip bun build ./src/client.ts --compile --minify --sourcemap --bytecode --outfile ffmpeg-over-ip-client ; ls -lah | grep ffmpeg-over-ip-client [6ms] minify -90.92 KB (estimate) [3ms] bundle 6 modules [44ms] compile ffmpeg-over-ip-client -rwxrwxrwx 1 steelbrain staff 56M Oct 6 16:53 ffmpeg-over-ip-client and `deno` produced even bigger outputs ~/P/s/ffmpeg-over-ip deno compile --allow-read --allow-net ./lib/client.js ; ls -lah | grep client Compile file:///Users/steelbrain/Projects/steelbrain/ffmpeg-over-ip/lib/client.js to client -rwxr-xr-x 1 steelbrain staff 65M Oct 6 16:56 client

Cyph0n 2y ago

Go would be a good fit for this kind of application. But Rust is a great choice too. Keep up the good work!

chrisldgk 2y ago

You might be able to switch to Bun or Deno with relatively little effort and create binaries that are probably a lot smaller (and maybe also faster) with each of their compile commands [1][2]. In the end I do also believe that a compiled language like Swift, Rust or Go might be a better fit though. [1] https://docs.deno.com/runtime/reference/cli/compiler/ https://docs.deno.com/runtime/reference/cli/compiler/ [2] https://bun.sh/docs/bundler/executables https://bun.sh/docs/bundler/executables

steelbrain 2y ago
FWIW, `bun` produced larger output files ~/P/s/ffmpeg-over-ip bun build ./src/client.ts --compile --minify --sourcemap --bytecode --outfile ffmpeg-over-ip-client ; ls -lah | grep ffmpeg-over-ip-client [6ms] minify -90.92 KB (estimate) [3ms] bundle 6 modules [44ms] compile ffmpeg-over-ip-client -rwxrwxrwx 1 steelbrain staff 56M Oct 6 16:53 ffmpeg-over-ip-client and `deno` produced even bigger outputs ~/P/s/ffmpeg-over-ip deno compile --allow-read --allow-net ./lib/client.js ; ls -lah | grep client Compile file:///Users/steelbrain/Projects/steelbrain/ffmpeg-over-ip/lib/client.js to client -rwxr-xr-x 1 steelbrain staff 65M Oct 6 16:56 client