I’m going to channel my inner zen robot and just concentrate on the technical aspect, and only the technical aspect (after this colorful introduction of course). It’s because of the inability of the Ruby community (and others) to concentrate on the argument that in this blog post I’m not going to link to any of the heated discussions that have spawned for more than a decade, nor am I going to spice any of my comments (even if the level of insanity is begging for it). In my previous post I explained why this notion of being “nice” does not always work, and in response the Ruby community focused exclusively on me and my level of “niceness”, instead of listening to my argument. Who is the arbiter of what is “nice”? Don’t you know there is no war in Ba Sing Se? “Matz is nice and so we are nice” ( MINASWAN) is a motto of the Ruby community which sounds great in theory, but in practice simply leads to many opinions being censored because they are “not nice”. In my opinion the biggest hurdle to fixing this issue properly is the attitude of the Ruby community, where conflict is not just avoided, but actively denied.
The only approach that has not been tried is to actually fix this properly.
usr/lib/ruby/gems/3.0.0), which is virtually never the case.įor more than a decade different approaches to workaround this assumption have been tried, but they always cause one unexpected issue or another. Since the beginning the installation of Ruby gems has been broken: it is assumed the user wants to install gems in the system directory (e.g.
0 kommentar(er)
