postmodern @postmodern@ruby.social

https://github.com/rubysec/bundler-audit/blob/master/ChangeLog.md#061--2019-01-17
bundler-audit 0.6.1 has been released, which supports bundler 2.x.

Eric Pigeon solved the regexp issue that was blocking bundler-audit 0.6.1. Was missing the `!` character...
https://github.com/rubysec/bundler-audit/pull/205/commits/da7a0137474eb9599618150d6b93aeeeb3bf4f98

FYI will be traveling for work, so expect bundler-audit 0.6.1 to be released on/after Thursday.

Ruby hivemind: RabbitMQ vs. Kafka?

Proc#<< might get merged into ruby-trunk. Functional style closure composition! Shweet!
https://bugs.ruby-lang.org/issues/6284

One anti-pattern I'm starting to see with GraphQL, is the temptation of getting all of the data in one request. The problem with that mindset is that some of your associated models do not need to be queried/embedded/retransmitted for each request/response. Ideally one would request the shared data, cache it, and join it on the client-side.

So what have people built using Serverless or FaaS Ruby? I'm curious what the limitations/constraints are.

Also I really wish LXD caught on. I like how it gives you the benefits of both containerization and the familiar structure of a GNU/Linux base system (systemd, crond, /bin, /sbin, etc).
https://www.youtube.com/watch?v=90oxad2r8_E

Catching up with 2018. Noticing there's a few variations on a stock ruby app Dockerfile. Most use puma, while some use the passenger base image + nginx. Am I the only one who finds it odd how we've gone back to reverse proxying requests to a ruby web server?

Anyone else see the similarities between Rails' Action Text and Shoes, Processing, or Arduino's light-weight editor? Certainly a nice-to-have user-friendly feature, but not a new idea.

https://github.com/postmodern/digest-crc/issues/13 had no clue ruby-kafka was using digest-crc. Looks like I'll be spending some time optimizing digest-crc soon.

I heard that GraphQL cannot handle Hashes with arbitrary/dynamic keys. Is this true? Are we starting to hit the upper-limits of GraphQL's flexibility?

Say, what are #Rubyists using for JSON builders in the year 2018? Is there a dry- equivalent?

https://github.com/cinchrb/cinch#example
cinch is an amazing library. Only took a few minutes to slap together a #Twitch bot; it helps that Twitch's chat API is really just an IRC server. Also has snazzy ANSI logging to boot. #ruby

bot = Cinch::Bot.new do
configure do |c|
c.server = "irc.chat.twitch.tv"
c.port = 6667
c.nick = "twitch_username_here"
c.password = "oath:..."
c.channels = %w[#mychannel]
end

on :message do |m|
# ...
end
end

bot.start

#ruby could use a REPL like Jupyter Notebook or Matlab. I want to be able to save/load sessions or projects, edit code in my $EDITOR and have it auto-loaded into the session, load/save data from external sources, and have everything saved into a standard project file structure. Something that helps you do one-off tasks, but also generates reusable artifacts that could be converted into gems once the code/data has become mature enough for distribution.

also where have you been all of my life "Delete & re-draft" option?! #mastodon

If you thought Rails was boring, wait till you try Padrino! :P
https://padrinorb.com/

Of course Ruby's Fixnum is actually a C unsigned integer, with two least-significant-bits reserved to denote it's object ID (3).
https://ruby-hacking-guide.github.io/object.html

It would be nice for data science (and C bindings) to be able to allocate large buffers of native ints and access them directly.

So now that Go, Rust, Crystal and Julia support native types, are people OK with fixed size and unsigned integers? I guess the performance/size is worth the risk of integer overflows/underflows. Is this something Ruby should consider adding?