🎉 maturin-guide-l10n is published!
🚀 Preview:
https://projects.localizethedocs.org/maturin-guide-l10n
🌐 Crowdin:
https://localizethedocs.crowdin.com/maturin-guide-l10n
🐙 GitHub:
https://github.com/localizethedocs/maturin-guide-l10n
#Crowdin #GitHub #mdBook #Rust #Python #Maturin #PyO3 #CFFI #UniFFI
Colors are not mine, this is just how #wgpu-native has it 
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!!! 
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?
Behold, the monstrosity! https://github.com/keelah-mt/cl-kl-c2ffi
Made some progress on webgpu‑native CL bindings. I still have no idea if this is going to work, but up until an hour ago it was going pretty well 
I’ve gotten to about one‑third of The Triangle example – https://github.com/gfx-rs/wgpu-native/blob/trunk/examples/triangle/main.c. (by line numbers)
Since I’m writing the GLFW and WGPU bindings in parallel, it takes time… So far I’ve managed to create a surface with wgpuInstanceCreateSurface… but then… well, I knew from the start I was stepping onto a minefield. My first problem is that CFFI can’t take arguments passed by value to callbacks from C . At least there’s a PR trying to fix it – https://github.com/cffi/cffi/pull/351.
I’m too tired to continue right now, having spent days working on this non‑stop. Time to decompress a bit. So the question “Will it render?” will remain open… Also, I still have a day job - I just remembered, it is going to happen tomorrow .
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
Is that really so? PyCups3 is intelligent? Well, short answer is YES. It is intelligent. Damn, sweetheart, you made an AI for PyCups? Not everything that’s intelligent is an AI. An imaginary conversation, between me and my girlfriend. Now, what’s the twist here is, PyCups3 is actually very very intelligent. So, from my last blog post, I detailed how, PyCups2 got lost due to the lack of upgrades and implmentation of new APIs.
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
Representative and generated So long of GSoC and No blog yet? Why Soumya? Yeah, yeah, I know. It’s been a while, and no blog posts yet. But hey, between wrestling with CFFI + C + Python and libcups with its 150+ APIs, blogging kind of took the back seat. But enough excuses - let’s dig into what’s been cooking. A little history (with C in it) Back in the day (almost 15 years ago!), Tim Waugh wrote the first version of pycups as a C extension module for Python. That worked well, but like all old code, it aged… let’s just say, not like fine wine. After Tim, Zdenek took over as maintainer, but with multiple projects of OpenPrinting and other projects in the mix, there wasn’t much room to modernize PyCups2 for him.
Halfway there! 🚀 Midterm blog for #GSoC2025 is live →
https://soumyadghosh.github.io/website/interns/gsoc-2025/gsoc-until-midterm/
Representative and generated So long of GSoC and No blog yet? Why Soumya? Yeah, yeah, I know. It’s been a while, and no blog posts yet. But hey, between wrestling with CFFI + C + Python and libcups with its 150+ APIs, blogging kind of took the back seat. But enough excuses - let’s dig into what’s been cooking. A little history (with C in it) Back in the day (almost 15 years ago!), Tim Waugh wrote the first version of pycups as a C extension module for Python. That worked well, but like all old code, it aged… let’s just say, not like fine wine. After Tim, Zdenek took over as maintainer, but with multiple projects of OpenPrinting and other projects in the mix, there wasn’t much room to modernize PyCups2 for him.
✨ 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
Localize The Docs
Kira Verhovyh 
Frigid Crystal Tormented Wrath
Till Kamppeter
Soumyadeep Ghosh
Soumyadeep Ghosh(সৌম্যদীপ ঘোষ)
treefit