#cffi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cffi, aggregated by home.social.
-
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. 🤞
-
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. 🤞
-
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. 🤞
-
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. 🤞
-
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. 🤞
-
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! https://github.com/keelah-mt/cl-kl-c2ffi
-
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! https://github.com/keelah-mt/cl-kl-c2ffi
-
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! https://github.com/keelah-mt/cl-kl-c2ffi
-
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! https://github.com/keelah-mt/cl-kl-c2ffi
-
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! https://github.com/keelah-mt/cl-kl-c2ffi
-
-
-
-
-
-
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:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025 -
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:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025 -
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:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025 -
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:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025 -
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:
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-pycups-is-intelligent/
Thanks @soumyadghosh
#OpenPrinting #Python #Pythonic #CFFI #CUPS #GSoC #GSoC2025 -
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
-
✨ 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 -
✨ 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 -
✨ 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 -
✨ 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 -
✨ 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 -
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction -
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction -
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction -
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction -
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction -
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 🤔 🤔 🤔
https://github.com/pawamoy/duty/actions/runs/9147683333/job/25149389495
-
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 🤔 🤔 🤔
https://github.com/pawamoy/duty/actions/runs/9147683333/job/25149389495
-
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 🤔 🤔 🤔
https://github.com/pawamoy/duty/actions/runs/9147683333/job/25149389495
-
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 🤔 🤔 🤔
https://github.com/pawamoy/duty/actions/runs/9147683333/job/25149389495
-
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 🤔 🤔 🤔
https://github.com/pawamoy/duty/actions/runs/9147683333/job/25149389495