1999: dang all the cool kids have a Dreamcast

2019: dang all the cool kids have a Dreamcast

This is quite interesting!
Hey ya'll! I'm learning Ruby from Launch School which is an online school for Software Engineers. Cheers everyone✨

Hi, I'm Jan, also known as halfbyte on the internet. Together with Florian, who's not on the Fediverse, I run Depfu.com, your friendly dependency update robot factory. I'm interested in weird and odd uses of ruby. I occasionally speak at conferences. I co-run the Hamburg Ruby Usergroup.

@ioquatix This is interesting because it isn't something I think much about. I've searched around and this is a point of contention several places; especially depending on how you define "diagnostic information".

Some links I found:


My current thinking is that "standard out" is for the standard (expected/typical) output? It is certainly more nuanced, though, than my initial reaction.

@ioquatix There's a good explanation why it should go to stderr in "A Research UNIX Reader: Annotated Excerpts from the Programmer’s Manual":

In the following Ruby code, should logger default to `$stderr` or `$stdout`?

logger = Logger.new

CSV do |csv|
logger.info "Generating row..."
csv << ['1', '2', '3']

Please reply with your reasoning.

@postmodern @ioquatix I ran a Dell XPS for a few years with Ubuntu, it was great. I’m back on a Mac now though, but for other reasons

When debugging , I always struggled to get to enter the contents of a block, painstakingly stepping through internal methods and watching out for the yield. If you've ever debugged and/or callbacks, you'll know this pain.

Today, I learned you can just type `c <line number>` to jump straight into the block while skipping all of the plumbing that yields to it.

:ruby: 🐜 🚫 👍

@ioquatix I swear by Lenovo ThinkPads (T or X series). Dell XPS is also good, from what I hear. Opt for Intel or AMD hardware to avoid driver issues. Cellular modems are still a gamble, because of the manufactures/OEMs.

I heard that some SF startups actually do all of their dev over SSH on EC2 boxes. Of course this only works if you're close to the datacenter, or always have a stable network connection...

@ioquatix just watched the presentation. Very sad... 1800+ stars, 16 contributors, <1% participation but lots of "thoughts and prayers".

I have been saying for years now that macOS is no longer a developer friendly platform (unless you work entirely in XCode). This news about Apple removing Perl, Python (2.7), and Ruby, might just be the final nail in the coffin. Each year I watch developers on $birbsite struggle to workaround the issues in the latest macOS release in order to setup a *nix-style development environment, all of which can easily be installed on Linux/FreeBSD with one or two package manager commands.

While I'm kind of glad Apple finally decided to pick a direction to go in, this move is likely going to disrupt Homebrew which relies on system Ruby; and they can't rely on ruby-build/ruby-install because those in turn rely on homebrew. I suppose this shift is going to finally increase demand for precompiled releases of scripting language runtimes that can be extracted into `/usr/local`. I doubt that Apple will be generous enough to maintain their own precompiled packages of Perl, Python, Ruby.

Let's improve thread creation in Ruby by an order of magnitude: github.com/ruby/ruby/pull/2227 😍

Here is my PR to improve fiber allocations by amortising stack allocations into a pool. github.com/ruby/ruby/pull/2224

Show more

A Mastodon instance for Rubyists & friends