Software developer working in
:ruby: #ruby & :crystal: #CrystalLang
as a #freelancer and at vade.io.
:whyfox: Posts may appear in English & German.
There might be some 🇨🇭 #Swiss content too.
Pronouns: I don't care but I'll respect yours 💛
tfr
#rubylang #crystal #crystallanguage #rubyprogramming #switzerland #zurich #rails #rubyonrails
PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
@marcoroth congrats 👏🏼
You earned it
RE: https://ruby.social/@getajobmike/116002638916815102
Super honored to be selected for the Gem Fellowship 🙏
I’ll continue pushing Herb forward as we get closer to 1.0 as part of this grant!
It’s really awesome to see Mike giving back to the community in this way, especially on top of consistently supporting in-person Ruby events over the last years.
Thank you, Mike!
@noniq ja… aber nein 😂
@fglc2 @nerdinand @marioschuettel sooooooo Spamdesk?
Wishing everyone a great time at CERN PGDay by CERN, Swiss PostgreSQL Users Group, a #hybrid event starting today in CERN, Council Chamber in #Meyrin, #Switzerland and #online on the Internet
Find out more on
https://foss.events/2026/02-06-cern-pgday.html
Follow the official account: @swisspug
Connect via official hashtag(s): #CERNPGDay
GlitchTip 6 is released with performance optimizations and improved architecture
🎉 alchemy_cms v8.0.6 has been released!
https://github.com/AlchemyCMS/alchemy_cms/releases/tag/v8.0.6
@emma I found the book on Amazon and put its link to the @whysfoxes account profile but if there's an official place to buy it, it would be great for many.
I often got asked where to buy it.
the youngsters these days have no patience for gongfu tea making. i get out the books about proper gaiwan technique and the kids all say "oolong, didn't read." and then they laugh and laugh
Good Morning, Bangkok! @rubyconfth just kicked off!
Looking forward to the first Ruby Conference of 2026! 🙌🏼
Building Dependency Injection with Crystal Macros
Appreciate my absolutely cursed macros that call other macros that trigger generic specialisation to introspect on method names all just to create objects
https://willhbr.net/2026/01/31/crystal-dependency-injection/
I just wrote what I think is the most horrendous #crystallang macro ever: a dependency injection framework in 221 lines
https://codeberg.org/willhbr/geode/commit/196c20259750b23de0d073562271bff8560b35c1
Just to say we're up to a very healthly 2,400+ organisations on https://usingrails.com. You can thank @marcoroth for a bunch of those :-)
I didn't think I'd ever pull it off 😀, but the new editor framework is complete and with it support for creating polls. One nice extra—you can now choose which content editor to use (rich text or Markdown) on a per-post basis without updating your settings.
The full set of changes in this release:
Added
Fixed
closed_at handling for drafts and remote polls.I'll try not to be quite as ambitious for the next release! 😅
A new version of #RuboCop is out with many fixes and improvements! (https://github.com/rubocop/rubocop/releases/tag/v1.84.0)
Enjoy!
The @w3c Web Machine Learning #WorkingGroup invites implementations of an updated #CandidateRecommendation Snapshot of the WebNN #API. Most notable additions include a third wave of operators for enhanced transformers support, the MLTensor API for buffer sharing, and a new abstract device selection mechanism #timetoimplement #MachineLearning
▶️ https://www.w3.org/TR/webnn/
Explainer: https://github.com/webmachinelearning/webnn/blob/main/explainer.md
Feedback wlc: https://github.com/webmachinelearning/webnn/issues/
TIL #PostgreSQL 16 and above has a level above the SUPERUSER role: the “bootstrap superuser,” from whom you cannot revoke SUPERUSER privileges: https://www.postgresql.org/docs/18/glossary.html#GLOSSARY-BOOTSTRAP-SUPERUSER
And since internal components may still refer to it by name or expect it to be present, you can’t effectively rename it.
So if you create a #database cluster and decide to name that first user after the application for which you're originally using PostgreSQL, you’re stuck with that name for the life of the cluster. You may think you’re keeping things simple at the time, but you’re setting yourself (and others) up for confusion later.
Better to just initialize the cluster with the default superuser name of `postgres`, and then create an app-specific user with lower privileges.
