Kernel#sendshould be deprecated and removed from future rubies.
sendalways felt weird when I was an active ruby developer but I have never seen any strong criticisms on it. It's either an attack on all family of send-like calls or a fierce defence that "using
sendis not a bad practice". Only some style guides argue against
sendbecause it may overlap with existing methods. This post was written after reading one of defences.
Yesterday I moved two of my ruby gems, journald-native and journald-logger, to
theforemanGitHub namepace. Developing them further is out of my current professional interest and hopefully the Foreman project will be a good home for them.
It's hard to say farewell however to the most popular library I created so far :D (8 GitHub stars, 57000 downloads)
As you may know, CommonMark is a project aiming to create unified and unambiguous Markdown syntax specification. So, I'm in. I want to spread the word and even use it in my own blog.
The strong side of Ruby CommonMark implementation, CommonMarker is its ability to parse a document to the abstract syntax tree, so let's use it to extract our blocks and highlight them with Rouge for example.
That's about string types in C and Ruby. As you may know, C uses null-terminated strings while Ruby uses more sophisticated string type, therefore C strings cannot contain null byte while Ruby strings can. Many Ruby gems are written in C but what happens when you convert Ruby string to the C string?
There is already a nice gem called
systemd-journal, why another one? Well, because there are some edge cases that it does not cover. I had a trouble with one.