puppy
@duckinator.bsky.social
a pile of small dogs in a meaty land vessel • KC1QGV • they/them
prone to creating technological cognitohazards
playing with synths again
#rustlang, #rubylang, #pythonlang, #cprogramming
prone to creating technological cognitohazards
playing with synths again
#rustlang, #rubylang, #pythonlang, #cprogramming
so, I got my electric guitar, used, back in 2013-2015.
it's had a bad pickup selector switch the whole time.
i just kept smacking it until it worked for... *checks notes*... a decade.
FINALLY open it up to try to fix it, and discover it's a fucking crime scene.
it's had a bad pickup selector switch the whole time.
i just kept smacking it until it worked for... *checks notes*... a decade.
FINALLY open it up to try to fix it, and discover it's a fucking crime scene.
November 11, 2025 at 3:48 AM
so, I got my electric guitar, used, back in 2013-2015.
it's had a bad pickup selector switch the whole time.
i just kept smacking it until it worked for... *checks notes*... a decade.
FINALLY open it up to try to fix it, and discover it's a fucking crime scene.
it's had a bad pickup selector switch the whole time.
i just kept smacking it until it worked for... *checks notes*... a decade.
FINALLY open it up to try to fix it, and discover it's a fucking crime scene.
Absolutely fucking cursed discovery:
If you create a gem, you can set its version to:
0.a.a.a.b---.---c---
And when you do `gem build`, it converts that version into:
0.a.a.a.b.pre..pre..pre...pre..pre..pre.c.pre..pre..pre.
(last dot is included in the version)
If you create a gem, you can set its version to:
0.a.a.a.b---.---c---
And when you do `gem build`, it converts that version into:
0.a.a.a.b.pre..pre..pre...pre..pre..pre.c.pre..pre..pre.
(last dot is included in the version)
November 2, 2025 at 11:26 PM
Absolutely fucking cursed discovery:
If you create a gem, you can set its version to:
0.a.a.a.b---.---c---
And when you do `gem build`, it converts that version into:
0.a.a.a.b.pre..pre..pre...pre..pre..pre.c.pre..pre..pre.
(last dot is included in the version)
If you create a gem, you can set its version to:
0.a.a.a.b---.---c---
And when you do `gem build`, it converts that version into:
0.a.a.a.b.pre..pre..pre...pre..pre..pre.c.pre..pre..pre.
(last dot is included in the version)
!!! `jim release` can now:
1. build itself as a .gem,
2. pack itself into a single-file script,
3. publish both of these to GitHub Releases
Try out the packed `jim.rb` file. It should be completely self-contained:
github.com/duckinator/j...
1. build itself as a .gem,
2. pack itself into a single-file script,
3. publish both of these to GitHub Releases
Try out the packed `jim.rb` file. It should be completely self-contained:
github.com/duckinator/j...
October 30, 2025 at 12:17 AM
!!! `jim release` can now:
1. build itself as a .gem,
2. pack itself into a single-file script,
3. publish both of these to GitHub Releases
Try out the packed `jim.rb` file. It should be completely self-contained:
github.com/duckinator/j...
1. build itself as a .gem,
2. pack itself into a single-file script,
3. publish both of these to GitHub Releases
Try out the packed `jim.rb` file. It should be completely self-contained:
github.com/duckinator/j...
FUCK YES.
`jim build` can successfully build itself.
It's a little cursed, and absolutely needs some cleanup, but it works well enough I was able to do `jim build` then `gem install build/jim-0.1.1.gem`.
I'm super excited about this. :3
`jim build` can successfully build itself.
It's a little cursed, and absolutely needs some cleanup, but it works well enough I was able to do `jim build` then `gem install build/jim-0.1.1.gem`.
I'm super excited about this. :3
October 17, 2025 at 6:30 AM
FUCK YES.
`jim build` can successfully build itself.
It's a little cursed, and absolutely needs some cleanup, but it works well enough I was able to do `jim build` then `gem install build/jim-0.1.1.gem`.
I'm super excited about this. :3
`jim build` can successfully build itself.
It's a little cursed, and absolutely needs some cleanup, but it works well enough I was able to do `jim build` then `gem install build/jim-0.1.1.gem`.
I'm super excited about this. :3
guess who just generated a valid tar file using ~150 lines of Ruby~
Tar file writer implementation:
github.com/duckinator/j...
And the code that uses it:
github.com/duckinator/j...
Tar file writer implementation:
github.com/duckinator/j...
And the code that uses it:
github.com/duckinator/j...
October 17, 2025 at 1:17 AM
guess who just generated a valid tar file using ~150 lines of Ruby~
Tar file writer implementation:
github.com/duckinator/j...
And the code that uses it:
github.com/duckinator/j...
Tar file writer implementation:
github.com/duckinator/j...
And the code that uses it:
github.com/duckinator/j...
Hey #CSS / #flexbox folks:
On pup-e.com I have a `nav ul` rule with `display: flex` and `flex-wrap: wrap`
With flexbox, is it possible to only put a character between each item that's on the same row?
atm I put a mid-dot between each item, but it looks like shit if it goes over multiple lines.
On pup-e.com I have a `nav ul` rule with `display: flex` and `flex-wrap: wrap`
With flexbox, is it possible to only put a character between each item that's on the same row?
atm I put a mid-dot between each item, but it looks like shit if it goes over multiple lines.
October 13, 2025 at 3:00 PM
What if gem hosts had NPM-like scopes & your Gemfile could be:
source "https://gem.example"
gem "@duckinator/jim"
OR:
gem "https://gem.example/duckinator/jim"
... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server?
github.com/gem-coop/gem...
source "https://gem.example"
gem "@duckinator/jim"
OR:
gem "https://gem.example/duckinator/jim"
... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server?
github.com/gem-coop/gem...
October 11, 2025 at 6:53 PM
What if gem hosts had NPM-like scopes & your Gemfile could be:
source "https://gem.example"
gem "@duckinator/jim"
OR:
gem "https://gem.example/duckinator/jim"
... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server?
github.com/gem-coop/gem...
source "https://gem.example"
gem "@duckinator/jim"
OR:
gem "https://gem.example/duckinator/jim"
... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server?
github.com/gem-coop/gem...
you ever have one of those days where your code just gets so excited it segfaults?
September 25, 2025 at 9:22 PM
you ever have one of those days where your code just gets so excited it segfaults?
These posts mean the Ruby Central board signed off on all of this.
If your goal was to secure the supply chain, you failed. Y'all made rapid fire permissions changes without understanding the implications of your actions.
You removed the team at the root of the supply chain you're "protecting".
If your goal was to secure the supply chain, you failed. Y'all made rapid fire permissions changes without understanding the implications of your actions.
You removed the team at the root of the supply chain you're "protecting".
September 19, 2025 at 9:14 PM
These posts mean the Ruby Central board signed off on all of this.
If your goal was to secure the supply chain, you failed. Y'all made rapid fire permissions changes without understanding the implications of your actions.
You removed the team at the root of the supply chain you're "protecting".
If your goal was to secure the supply chain, you failed. Y'all made rapid fire permissions changes without understanding the implications of your actions.
You removed the team at the root of the supply chain you're "protecting".
@cafeaubun.bsky.social hey! Am I remembering correctly that these album covers were your work? I sadly have lost my records from 2017 so have to rely on my memory of things from 8 years ago. 😅
September 14, 2025 at 1:48 AM
@cafeaubun.bsky.social hey! Am I remembering correctly that these album covers were your work? I sadly have lost my records from 2017 so have to rely on my memory of things from 8 years ago. 😅
sometimes it feels like C compilers are optimized for being frustrating.
warning because variables are "unused" -> explicitly mark as used -> get 2 additional warnings about the [[used]] attribute being ignored
*facedesks*
warning because variables are "unused" -> explicitly mark as used -> get 2 additional warnings about the [[used]] attribute being ignored
*facedesks*
September 11, 2025 at 2:13 AM
sometimes it feels like C compilers are optimized for being frustrating.
warning because variables are "unused" -> explicitly mark as used -> get 2 additional warnings about the [[used]] attribute being ignored
*facedesks*
warning because variables are "unused" -> explicitly mark as used -> get 2 additional warnings about the [[used]] attribute being ignored
*facedesks*
projects i work on always seem to have a very specific vibe
September 8, 2025 at 5:42 PM
projects i work on always seem to have a very specific vibe
After ~12 years, I finally got an adapter for the $8 telephoto lens.
5.5 inch long pen and 8 inch long plushie for scale.
5.5 inch long pen and 8 inch long plushie for scale.
May 14, 2025 at 8:22 PM
After ~12 years, I finally got an adapter for the $8 telephoto lens.
5.5 inch long pen and 8 inch long plushie for scale.
5.5 inch long pen and 8 inch long plushie for scale.
me: [accidental keysmash]
vim: oh, right, i know what that means! [smears text across the screen like a child who has been left unattended with paint]
vim: oh, right, i know what that means! [smears text across the screen like a child who has been left unattended with paint]
January 22, 2025 at 5:39 PM
me: [accidental keysmash]
vim: oh, right, i know what that means! [smears text across the screen like a child who has been left unattended with paint]
vim: oh, right, i know what that means! [smears text across the screen like a child who has been left unattended with paint]