home.social

#cffi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cffi, aggregated by home.social.

  1. Colors are not mine, this is just how #wgpu-native has it :blobcat_thisisfine:

    I finally looked up the story about Lemonodor, so yeah, I am way late to that party... I don't even understand why I am doing #commonlisp, but for some reason, I find it addictive.

    And so, after 3 months of pretty intense work, I proudly present this beauty—THE TRIANGLE!!! :blobcat_dundundun:

    It’s the wgpu-native triangle example implemented in CL with the #wgpu bindings lib I’ve been working on. I hope I can now exhale, relax, and take a small break. And then jump into it again. Refreshed. A bit, at least.

    There’s going to be a lot of work to clean up the mess I made while zerg rushing things with my brain cells in these past 3 months before I start expanding the API. I hope wgpu-native will continue to bless me with smooth rendering and zero crashes. 🤞

    github.com/keelah-mt/cl-kl-wgpu

    #cffi #lisp #programming

  2. Colors are not mine, this is just how #wgpu-native has it :blobcat_thisisfine:

    I finally looked up the story about Lemonodor, so yeah, I am way late to that party... I don't even understand why I am doing #commonlisp, but for some reason, I find it addictive.

    And so, after 3 months of pretty intense work, I proudly present this beauty—THE TRIANGLE!!! :blobcat_dundundun:

    It’s the wgpu-native triangle example implemented in CL with the #wgpu bindings lib I’ve been working on. I hope I can now exhale, relax, and take a small break. And then jump into it again. Refreshed. A bit, at least.

    There’s going to be a lot of work to clean up the mess I made while zerg rushing things with my brain cells in these past 3 months before I start expanding the API. I hope wgpu-native will continue to bless me with smooth rendering and zero crashes. 🤞

    github.com/keelah-mt/cl-kl-wgpu

    #cffi #lisp #programming

  3. Colors are not mine, this is just how #wgpu-native has it :blobcat_thisisfine:

    I finally looked up the story about Lemonodor, so yeah, I am way late to that party... I don't even understand why I am doing #commonlisp, but for some reason, I find it addictive.

    And so, after 3 months of pretty intense work, I proudly present this beauty—THE TRIANGLE!!! :blobcat_dundundun:

    It’s the wgpu-native triangle example implemented in CL with the #wgpu bindings lib I’ve been working on. I hope I can now exhale, relax, and take a small break. And then jump into it again. Refreshed. A bit, at least.

    There’s going to be a lot of work to clean up the mess I made while zerg rushing things with my brain cells in these past 3 months before I start expanding the API. I hope wgpu-native will continue to bless me with smooth rendering and zero crashes. 🤞

    github.com/keelah-mt/cl-kl-wgpu

    #cffi #lisp #programming

  4. Colors are not mine, this is just how #wgpu-native has it :blobcat_thisisfine:

    I finally looked up the story about Lemonodor, so yeah, I am way late to that party... I don't even understand why I am doing #commonlisp, but for some reason, I find it addictive.

    And so, after 3 months of pretty intense work, I proudly present this beauty—THE TRIANGLE!!! :blobcat_dundundun:

    It’s the wgpu-native triangle example implemented in CL with the #wgpu bindings lib I’ve been working on. I hope I can now exhale, relax, and take a small break. And then jump into it again. Refreshed. A bit, at least.

    There’s going to be a lot of work to clean up the mess I made while zerg rushing things with my brain cells in these past 3 months before I start expanding the API. I hope wgpu-native will continue to bless me with smooth rendering and zero crashes. 🤞

    github.com/keelah-mt/cl-kl-wgpu

    #cffi #lisp #programming

  5. Colors are not mine, this is just how #wgpu-native has it :blobcat_thisisfine:

    I finally looked up the story about Lemonodor, so yeah, I am way late to that party... I don't even understand why I am doing #commonlisp, but for some reason, I find it addictive.

    And so, after 3 months of pretty intense work, I proudly present this beauty—THE TRIANGLE!!! :blobcat_dundundun:

    It’s the wgpu-native triangle example implemented in CL with the #wgpu bindings lib I’ve been working on. I hope I can now exhale, relax, and take a small break. And then jump into it again. Refreshed. A bit, at least.

    There’s going to be a lot of work to clean up the mess I made while zerg rushing things with my brain cells in these past 3 months before I start expanding the API. I hope wgpu-native will continue to bless me with smooth rendering and zero crashes. 🤞

    github.com/keelah-mt/cl-kl-wgpu

    #cffi #lisp #programming

  6. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  7. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  8. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  9. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  10. Oh, so it is 2026 already? And the month is February already? The last thing I remember is diving into a rabbit hole called "Surely writing my own c2ffi translator for my WGPU project is no big deal."

    What's done is done. I am slowly recovering and ready to get back to my WGPU project. While the need for a custom translator is still debatable, I guess further practice will show if that's actually the case. Even if it was overkill, the time wasn't completely lost: I’ve learned more about Common Lisp and even did TDD for the first time in my life - who would've guessed it would finally happen in CL? :blobcat_thisisfine:

    Behold, the monstrosity! github.com/keelah-mt/cl-kl-c2f

    #commonlisp #cffi #wgpu #programming #lisp

  11. Well I got #cffi installed within #blender s internal python... but it fixed nothing

  12. Well I got #cffi installed within #blender s internal python... but it fixed nothing

  13. Well I got #cffi installed within #blender s internal python... but it fixed nothing

  14. Well I got #cffi installed within #blender s internal python... but it fixed nothing

  15. Well I got #cffi installed within #blender s internal python... but it fixed nothing

  16. how would one add #Cffi to #Blender? one of my addons keeps crashing because it cant find cffi

    installed cffi via pip but that went nowhere.

  17. how would one add #Cffi to #Blender? one of my addons keeps crashing because it cant find cffi

    installed cffi via pip but that went nowhere.

  18. how would one add #Cffi to #Blender? one of my addons keeps crashing because it cant find cffi

    installed cffi via pip but that went nowhere.

  19. how would one add #Cffi to #Blender? one of my addons keeps crashing because it cant find cffi

    installed cffi via pip but that went nowhere.

  20. how would one add #Cffi to #Blender? one of my addons keeps crashing because it cant find cffi

    installed cffi via pip but that went nowhere.

  21. For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.

    But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:

    soumyadghosh.github.io/website

    Thanks @soumyadghosh

    #OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025

  22. For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.

    But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:

    soumyadghosh.github.io/website

    Thanks @soumyadghosh

    #OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025

  23. For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.

    But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:

    soumyadghosh.github.io/website

    Thanks @soumyadghosh

    #OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025

  24. For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.

    But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:

    soumyadghosh.github.io/website

    Thanks @soumyadghosh

    #OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025

  25. For the Python programmers under you who wanted to make your app print, you probably have used pyCUPS to talk with the printing system. Perhaps you have also seen that it is not well maintained, not keeping pace with new APIs. Problem was its design, being a maintenance nightmare.

    But for libcups3 it gets much better, thanks to the most Pythonic GSoC contributor we ever had, and CFFI:

    soumyadghosh.github.io/website

    Thanks @soumyadghosh

    #OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025

  26. ✨ My first technical blogpost is out now. ✨

    If you ever wanted to learn a bit about how
    #deltachat works internally and why we have two ways to communicate with our #rust core, then this is the introduction to read

    delta.chat/en/2025-02-11-why-j

    #jsonrpc #cffi #c #rust #deltachat_desktop #deltachat_core

  27. ✨ My first technical blogpost is out now. ✨

    If you ever wanted to learn a bit about how
    works internally and why we have two ways to communicate with our core, then this is the introduction to read

    delta.chat/en/2025-02-11-why-j

  28. ✨ My first technical blogpost is out now. ✨

    If you ever wanted to learn a bit about how
    #deltachat works internally and why we have two ways to communicate with our #rust core, then this is the introduction to read

    delta.chat/en/2025-02-11-why-j

    #jsonrpc #cffi #c #rust #deltachat_desktop #deltachat_core

  29. ✨ My first technical blogpost is out now. ✨

    If you ever wanted to learn a bit about how
    #deltachat works internally and why we have two ways to communicate with our #rust core, then this is the introduction to read

    delta.chat/en/2025-02-11-why-j

    #jsonrpc #cffi #c #rust #deltachat_desktop #deltachat_core

  30. ✨ My first technical blogpost is out now. ✨

    If you ever wanted to learn a bit about how
    #deltachat works internally and why we have two ways to communicate with our #rust core, then this is the introduction to read

    delta.chat/en/2025-02-11-why-j

    #jsonrpc #cffi #c #rust #deltachat_desktop #deltachat_core

  31. Hmmm, how come #uv manages to install #cffi==1.16.0 in GitHub Actions on ubuntu-latest and #Python 3.13.0b1 while it fails locally on (Arch)Linux and Python 3.13.0b1 🤔

    There is no wheel of 1.16.0 for CPython 3.13 🤔 And sources fail to compile (not compatible with 3.13). I'm confused 🤔 🤔 🤔

    github.com/pawamoy/duty/action

  32. Hmmm, how come manages to install ==1.16.0 in GitHub Actions on ubuntu-latest and 3.13.0b1 while it fails locally on (Arch)Linux and Python 3.13.0b1 🤔

    There is no wheel of 1.16.0 for CPython 3.13 🤔 And sources fail to compile (not compatible with 3.13). I'm confused 🤔 🤔 🤔

    github.com/pawamoy/duty/action

  33. Hmmm, how come #uv manages to install #cffi==1.16.0 in GitHub Actions on ubuntu-latest and #Python 3.13.0b1 while it fails locally on (Arch)Linux and Python 3.13.0b1 🤔

    There is no wheel of 1.16.0 for CPython 3.13 🤔 And sources fail to compile (not compatible with 3.13). I'm confused 🤔 🤔 🤔

    github.com/pawamoy/duty/action

  34. Hmmm, how come #uv manages to install #cffi==1.16.0 in GitHub Actions on ubuntu-latest and #Python 3.13.0b1 while it fails locally on (Arch)Linux and Python 3.13.0b1 🤔

    There is no wheel of 1.16.0 for CPython 3.13 🤔 And sources fail to compile (not compatible with 3.13). I'm confused 🤔 🤔 🤔

    github.com/pawamoy/duty/action

  35. Hmmm, how come #uv manages to install #cffi==1.16.0 in GitHub Actions on ubuntu-latest and #Python 3.13.0b1 while it fails locally on (Arch)Linux and Python 3.13.0b1 🤔

    There is no wheel of 1.16.0 for CPython 3.13 🤔 And sources fail to compile (not compatible with 3.13). I'm confused 🤔 🤔 🤔

    github.com/pawamoy/duty/action