Conversation

Notices

1. Embed this notice
   Emma (ipg@wetdry.world)'s status on Monday, 25-Mar-2024 08:03:48 JST Emma

   ffmpeg have never been more real

   • Haelwenn /элвэн/ :triskell:, :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: and :lazer_A: :lazer_N: :lazer_O: :lazer_N: :lazer_I: :lazer_c: :lazer_u: :lazer_s: like this.
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Friday, 29-Mar-2024 07:48:24 JST Wolf480pl

     in reply to

     • LisPi

     @lispi314 @Makura @ipg
     it's also needed when you gotta go fast and the compiler doesn't know how to use the fancy special case CPU instructions that are only useful for FFT

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Friday, 29-Mar-2024 07:48:25 JST LisPi

     in reply to
     @ipg @Makura On the other hand, I'd rather C disappears and Ada replaces it, for those things where space constraints are a major concern.
     
     As for Assembly, yes, ultimately it's needed to bootstrap anything else. Even Forth.
   • Embed this notice
     halva(0) (halva@wetdry.world)'s status on Friday, 29-Mar-2024 07:51:32 JST halva(0)

     in reply to

     @ipg nah fuck c lmfao, there's absolutely no reason to cling to it other than sentimentality

     asm makes sense as a direct representation of machine code, it's not like there's any other way to do it, but C is just another high level language (albeit a very old and influential one)

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 29-Mar-2024 07:51:32 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • halva(0)
     @halva @ipg There's a lot of reasons why people would still cling to C, specially for things like ffmpeg where a lot of it is directly interfacing with the rest of the system where the only API you have is C.
     Which is why the core of your favorite Java/Go/Rust/… stuff is still C, and ffmpeg is pretty much a core library.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 31-Mar-2024 04:14:28 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • halva(0)
     • LisPi
     @lispi314 @halva @ipg If you target Linux yeah it's somewhat doable (although like strace does you'd need to parse C headers at one point, good luck).
     But if you want portability… nope.
     
     https://utcc.utoronto.ca/~cks/space/blog/programming/GoCLibraryAPIIssues
     https://utcc.utoronto.ca/~cks/space/blog/unix/CLibraryAPIRequiresC
     
     And sadly the Linux kernel isn't the only ABI you need to care about, like if you do OpenGL/Vulkan/… you'll end up with having to deal with C.
     (And there's core system libraries that are very security-sensitive like the nsswitch.conf stuff and pam where it's stuck to C)
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Sunday, 31-Mar-2024 04:14:29 JST LisPi

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • halva(0)
     @lanodan @ipg @halva You don't have to make the core in C and there are quite a few self-hosted languages that don't.
     
     Linux has a stable ABI for userspace (mostly), so it is possible to even do the whole thing from scratch and communicating directly with the system that way, skipping C entirely. In general instead such languages deem it simpler to make a C wrapper which can communicate with their own ABI instead.