text
stringlengths
0
1.17k
[415.38 --> 421.84] specific issues where certain platforms will change things um and it has to be cognizant of all this
[421.84 --> 428.46] and then there's also issues with how it organizes rubies um like if for instance you basically
[428.46 --> 432.88] assumes that it should be installed into your home directory you can install it system-wide but
[432.88 --> 439.36] the installation of the software is coupled to the location where it actually installs the rubies and
[439.36 --> 444.82] that really kind of annoyed me because i really kind of wanted all my rubies out of my home directory
[444.82 --> 450.76] i wanted my software installed globally so other users on my system maybe like i have some
[450.76 --> 456.94] automated scripts that ran under like a you know dummy user account for safety reasons i wanted it
[456.94 --> 462.22] to have access to it and i want to have rubies installed in some global location and then also
[462.22 --> 467.06] have rubies installed in some like you know my home directory or you know i have other partitions
[467.06 --> 472.70] where i usually just like a dump code where i want to like check out the latest version of rubinius
[472.70 --> 478.20] so i'll pull that down some other directory and build it build it there and that really wasn't
[478.20 --> 485.26] possible if rvm uh it will be possible if rvm2 with the ability to mount arbitrary installation
[485.26 --> 491.64] paths where ruby is installed maybe you threw it in the opt directory or somewhere else so that was
[491.64 --> 497.46] kind of one of the things and then eventually i like that just got so many bugs where i kind of
[497.46 --> 503.04] like went back to using system ruby because it was just really useful and most of my work involved
[503.04 --> 510.30] uh just developing against like you know 2.0 right and then using travis ci to test all the other
[510.30 --> 516.02] versions right but then um i got like started a contract and i was like oh crap i'm gonna really
[516.02 --> 522.72] need to get a working environment here that i can just you know use any sort of um version so i kind
[522.72 --> 526.56] of got thinking about it and it's like you know usually when i start projects there's always this
[526.56 --> 532.06] period of like deep thought and kind of research so i was kind of like do i really want to spend the
[532.06 --> 537.56] time developing like a ruby switcher i mean there's rvm it's giant am i gonna like fall down the same
[537.56 --> 545.14] path that um you know kind of like the the developers of rvm have like uh i believe uh wayne
[545.14 --> 550.28] kind of got burnt out with dealing with all the issues and michael pappas is uh or michael pappas is
[550.28 --> 555.40] doing a really good job of maintaining it but still like really stressful so i was like i went around
[555.40 --> 562.62] and kind of like researched how rvm um basically like changed manipulate the path and then i also
[562.62 --> 568.88] got uh i looked at rbm as i started like okay well let's let's look at the alternatives before i jump
[568.88 --> 573.72] into like starting a huge project right before a contract job where i'm gonna have to be like
[573.72 --> 579.64] heads down dedicated and so there's like lots of various other ruby switchers out there
[579.64 --> 586.94] and um rbm is pretty much the only shims based ruby switcher and so there's kind of like issues
[586.94 --> 592.88] when uh because i tried it when it was still kind of pretty new and fresh and so and it was kind of
[592.88 --> 599.50] confused with how the shims worked and this they had like different levels of setting which desired
[599.50 --> 605.08] ruby do you want like you had like that was it shell local system global or something like that yeah
[605.08 --> 612.66] and then also i've i felt like it it copied a lot of features not copied but you know it re-implemented
[612.66 --> 620.32] a lot of rvm ish features so i kind of felt like it wasn't really thinking outside the box it wasn't
[620.32 --> 626.14] like unthinking it was still kind of following in the shadow or the footsteps of kind of like how all
[626.14 --> 632.60] of us rubyist have sort of like grew grew up expecting the environment to work in the tools and
[632.60 --> 638.42] you know like even has a sub command feature which is like a very rvm ish thing in my opinion
[638.42 --> 643.12] and instead of having multiple separate utilities and scripts that work together in conjunction
[643.12 --> 649.54] has this huge like sub command thing um but yeah there's also lots of other weird ruby switchers it
[649.54 --> 653.96] turns out that is like kind of looking around by the way i define ruby switcher as something that
[653.96 --> 660.30] only switches the ruby version uh that seems to be the the thing that you say most is like this is just
[660.30 --> 666.24] a switcher it doesn't install like rvm does it's one job of one job only which i guess falls back on
[666.24 --> 672.64] your linux unix background too of of you know one job really well right and there's lots of other
[672.64 --> 677.46] basically implement implementations of this and i found that like i kind of went through and kind of
[677.46 --> 684.00] rated them or scored them on like uh features and it's uh one of the kind of the probably the most
[684.00 --> 693.58] well-developed ones was uh rbfoo uh were by hmans that's his github handle and so i tried that i was
[693.58 --> 697.74] like okay this might be it's not what i'm looking for and because they just need something really
[697.74 --> 703.24] minimal that just manipulates path and you know sets some couple environment variables you know it
[703.24 --> 709.48] shouldn't be this hard and so i looked at it and like some of the things were nice um but one of the
[709.48 --> 713.62] things that kind of annoyed me with it was kind of the syntax so when you actually type the version
[713.62 --> 719.76] for some reason he like began the versions with an at sign and then there was also kind of the whole
[719.76 --> 724.92] coupling where it expected the rubies to be in your home directory and sure you could probably sim
[724.92 --> 729.16] link them out but i really want to have like a configurable list where i just give arbitrary paths
[729.16 --> 734.92] right and then also i noticed a lot of these ruby switchers would always sets what they would hard
[734.92 --> 741.28] code the gem path and gem uh gem home which are kind of the locations where it should look up the
[741.28 --> 749.30] ruby gems and one of the things that kind of annoyed me is the so when you install since was it ruby 1.9
[749.30 --> 756.40] ruby gems has been uh shipped with ruby so it actually ruby gems has its own main gem directory
[756.40 --> 763.06] inside ruby and actually now ruby comes with some uh pre-installed gems like a big decimal
[763.06 --> 770.82] um what was it io console uh some other ones i can't remember off the top of my head but anyways
[770.82 --> 778.54] so it's really important that first of all you're not supposed to assume that the gem directory of
[778.54 --> 785.50] that's in the main ruby install is always in that location because rubinius actually has its own also
[785.50 --> 790.56] gem directory that they that's you know kind of in when you install rubinius it also installs its own
[790.56 --> 795.84] gem directory and said not in the same location which is kind of a little annoyance but um also
[795.84 --> 803.00] the fact that the uh you need the actual api version of the ruby so for instance uh this is not the
[803.00 --> 808.62] actual version of the ruby but the actual kind of overarching api version like you know um all the
[808.62 --> 816.42] 1.8 series it was just 1.8 but since uh mri 1.9.0 was kind of a botched release that had like some
[816.42 --> 822.72] showstopper bugs in it they actually bumped the api version to 1.9.1 so that's kind of another kind
[822.72 --> 830.78] of like hiccup you have to detect and then also um the gem directory might not be writable um people
[830.78 --> 835.12] assume it's going to be writable because the ruby install is in your home directory and you probably
[835.12 --> 839.40] have a writable access to that and i kind of felt that that was kind of violating the whole unix
[839.40 --> 845.84] principle of uh keeping software separate from the users so you don't actually delete it or you know
[845.84 --> 851.04] download some weird virus and you know embeds itself in the software you have writable permission
[851.04 --> 857.10] separation where you you would separate the gems you installed as a user versus the gems you install
[857.10 --> 863.48] as roots which is something also i i you know copied from how fedora sets theirs up and i think uh
[863.48 --> 870.64] deviant also has updated has done something similar and also wanted basically be able to switch between
[870.64 --> 875.78] rubies from arbitrary locations and it would just automatically detect the gem directory
[875.78 --> 881.70] and calculate it all out the other thing uh that also annoyed me about using rvm was the fact
[881.70 --> 887.08] that they made gem directories specific to each patch level which was really annoying when you upgrade
[887.08 --> 891.82] because you have to upgrade all your gems and like it's only a patch level guys it's not like
[891.82 --> 899.30] a big feature feature breaking version release um so that's kind of like that i put all that together
[899.30 --> 903.08] i think i spent about a week week and a half kind of like doing all this research and
[903.08 --> 908.98] kind of like figuring out the features and how to go about doing them and uh kind of wrote up my
[908.98 --> 914.02] first initial version and so so you spent the the couple weeks trying to figure out the features
[914.02 --> 919.50] and then the feature you landed on uh the feature set you landed on is like very very small it's
[919.50 --> 926.46] interesting and just to clarify like we've had kind of the longer this show goes on like in terms of
[926.46 --> 932.06] the changelog as a whole not this particular show uh we've obviously had like predecessors and then
[932.06 --> 938.04] like current the new hot and then you know the the future people will inevitably come but just to
[938.04 --> 943.50] just to make sure that nobody here it thinks this way like we're not here to disparage against any of
[943.50 --> 947.96] the previous ones because what they do is they they set up a path and like a you know you can learn
[947.96 --> 955.14] lessons and ch ruby has in postmodern has benefited greatly from the things that the the ones before
[955.14 --> 963.64] him have done and so yeah go ahead uh also i was going to point out that uh uh michael pappas uh the
[963.64 --> 969.52] current maintainer of rvm1 and also who's working on rvm2 basically i kind of showed it to him and
[969.52 --> 975.12] this was like the first version of ch ruby which didn't even support auto switching and he was like
[975.12 --> 982.36] oh great another ruby switcher you know oh you're gonna gonna just you know disparage rvm and you know
[982.36 --> 987.86] poo poo on it and like it was like no no no it's just completely different scale down it only does
[987.86 --> 992.96] this one thing it's not supposed to try it's not trying to compete with rvm or even rbm as far as i
[992.96 --> 998.64] can tell too when michael was on the show recently too he was saying that rvm 2.0 was going to expand
[998.64 --> 1004.42] not only into ruby but also python and be and go beyond so i mean i think he had like this much
[1004.42 --> 1010.48] larger scope to go towards yeah he's talking about basically um also integrating with the package
[1010.48 --> 1017.02] manager and so it's very similar to certain things like um oh red had has a single was it software