text
stringlengths
0
1.17k
[1017.02 --> 1022.26] collection layers or something like that but basically he wants uh an environment manager
[1022.26 --> 1028.34] literally and it's something that can install my sequel and dump a really nice auto you know
[1028.34 --> 1034.70] basic configuration so you can you know start using it out of the box um yeah but and also he's
[1034.70 --> 1039.92] helped me a lot with a lot of the bash issues and sort of bouncing ideas off him like well how did rvm
[1039.92 --> 1044.94] handle this weird obscure that's awesome honestly i mean michael's a good guy i know he took over for
[1044.94 --> 1051.52] wayne when when things kind of got harder for him and we've had uh several people on the show come and
[1051.52 --> 1059.14] talk about um burnout i can't recall his name andrew helped me out but he was um on just like four or
[1059.14 --> 1064.52] five shows back names gap me right now i have to look at our show list but i think to andrew's point
[1064.52 --> 1069.88] was to say that you know we're not here to bash any predecessors we're here to this is open source
[1069.88 --> 1076.76] things change software is the most complex volatile market ever so i mean obviously that's the case we
[1076.76 --> 1082.30] love mike we love rvm and but we we lift up everybody to to kind of get their word out and what they're
[1082.30 --> 1088.54] doing and why it's important and why rubia should care yeah yeah definitely let's pause the show for just
[1088.54 --> 1093.54] a minute give a shout out to our sponsor code chip they're also a partner of ours so super excited to be
[1093.54 --> 1098.44] working with code chip they're a hosted continuous deployment service that just works you can easily
[1098.44 --> 1104.40] set up continuous integration for your application today in just a few steps and automatically deploy
[1104.40 --> 1109.68] when all your tests pass code chip has great support for lots of languages test frameworks as well as
[1109.68 --> 1116.38] notification services they easily integrate with github or bitbucket and can deploy to cloud services like
[1116.38 --> 1123.50] heroku aws nojitsu google app engine or even your own servers get started today with
[1123.50 --> 1130.44] their free plan setup only takes three minutes head to code chip.io and also check out their blog
[1130.44 --> 1139.44] blog.coachip.io and one more thing to mention for our members you can save between $294 and $2,994
[1139.44 --> 1145.34] on your first year with code chips so make sure you take advantage of that head to the change all.com
[1145.34 --> 1155.34] benefits to learn more once again code chip.io try it today so to kind of move forward the when i first
[1155.34 --> 1162.28] found chruby which was i don't you know maybe 10 months ago a year ago 15 i don't know so somewhere in
[1162.28 --> 1169.50] the past uh the way that everyone was using it was uh basically using ruby build which was built by sam
[1169.50 --> 1177.62] stevenson and others um i think originally just was supposed to be purely for rbm and then they
[1177.62 --> 1184.14] decided to like make it easier to use as a standalone thing and so chruby was just a switcher and a lot
[1184.14 --> 1190.94] of people were using ruby build to actually install rubies um and uh just recently i you know went back
[1190.94 --> 1197.68] and started evaluating these things again and i saw that now there's ruby install um which essentially
[1197.68 --> 1204.24] does the same thing as ruby build it actually allows you to install rubies so why so i obviously
[1204.24 --> 1208.46] we see why you you created chruby and you know looking at all the other ones what about that
[1208.46 --> 1214.84] why did you create ruby install so initially i also used ruby build because you know it's it was a nice
[1214.84 --> 1219.90] decoupled tool and i could just use it for its one specific purpose but there's lots of things about
[1219.90 --> 1225.00] it that kind of got under my skin and so i started this whole process of kind of like evaluating it
[1225.00 --> 1231.62] and evaluating how rvm also handles uh compiling installing and of course they go into way more
[1231.62 --> 1238.54] detail of handling weird obscure uh platform specific issues but um so what the way ruby build
[1238.54 --> 1246.26] works is it has basically definitions for every single version so literally you can you can you have to
[1246.26 --> 1250.94] actually specify the fully qualified version and that was kind of one annoyance because literally i just
[1250.94 --> 1257.16] i when i install uh you know some version i really don't care just won't give me the most recent 193
[1257.16 --> 1264.20] that you know of um or you know literally copy and paste the version from uh the the news the news
[1264.20 --> 1268.76] announcement on ruby lang when they release a new version they're it's going to be there so just copy
[1268.76 --> 1274.52] and paste in the command line but then as i kind of like dug into it more um that was kind of a minor
[1274.52 --> 1280.28] nuisance but um i dug into it a lot more i found that it does lots of really weird things with
[1280.28 --> 1288.18] trying to detect um kind of when libraries are available and it also can download um its own
[1288.18 --> 1294.26] versions of open ssl and compiles those and then links ruby against that and that kind of like that
[1294.26 --> 1298.22] worried me because i automatically knew that eventually there's going to be a vulnerability
[1298.22 --> 1304.18] in these libraries and there's not going to be an easy way to to update them you can't just go
[1304.18 --> 1309.48] like oh update the library like it's it's compile installed into its own directory and literally you
[1309.48 --> 1314.16] have to reinstall the rubies to cause to force the newer version to get downloaded and then
[1314.16 --> 1319.14] the ruby compiled against the newer version so i was kind of like well obviously that's kind of a
[1319.14 --> 1324.88] that should be another feature is just use the package manager uh because every system the packages are
[1324.88 --> 1331.12] there available you can compile against them and they die the ruby dynamically links against them and so
[1331.12 --> 1336.96] when there's a vulnerability you just update the package you're good go and also distributions are
[1336.96 --> 1341.78] really good about backporting security fixes and so you can update and not worry about getting weird
[1341.78 --> 1348.76] api breakage um you literally just get that one fix so that was kind of another thing that inspired me and
[1348.76 --> 1356.36] and i really just want something that would work on as many systems against many package managers as
[1356.36 --> 1362.72] possible and of course it's a lot easier because uh chruby has to work in both bash and zsh
[1362.72 --> 1368.90] whereas ruby install was a utility and so i could just write against bash 3 and uh do that
[1368.90 --> 1379.00] yeah and so and i basically kind of took a very um declarative uh design to it where literally you
[1379.00 --> 1384.94] have like individual files build files for each major implementation and they define the configuration
[1384.94 --> 1391.82] step the compile step and the install step and then kind of like any sort of specific uh package
[1391.82 --> 1396.20] manager configuration like you have to do some weird things with homebrew because its packages
[1396.20 --> 1404.08] aren't in like a place where a lot of the um the auto the auto conf scripts of mri can find them so
[1404.08 --> 1409.68] you have to literally hint at it which is something i learned from uh rvm where there's an option call
[1409.68 --> 1416.30] was it with opter and you have to pass that in specifically for homebrew and and mac ports also
[1416.30 --> 1423.16] because mac ports installs in that's still around um yeah yeah actually and i got a recently got a uh
[1423.16 --> 1431.10] a bug report from a user who was attempting to use think which is like super old yeah and like back in
[1431.10 --> 1436.60] the day actually i had was at the uh the last generation ibook and it's i ran osx for a while and
[1436.60 --> 1443.36] then uh back when it's like power pc and i went back to uh running like linux on it so i knew about think
[1443.36 --> 1450.54] and i was like whoa that's still what's people use that still but yeah oh yeah just glancing at the
[1450.54 --> 1455.58] glancing at the project home page they are still getting regular releases which is pretty cool to
[1455.58 --> 1462.66] see it lasting this long yeah that's cool so i guess that's a you kind of hit on uh you had a a
[1462.66 --> 1470.92] not a feature request but a bug report and uh you do the ch ruby and ruby install they do such
[1470.92 --> 1478.52] small things so how often like ch ruby is 90 lines of code right so maintaining this seemingly would
[1478.52 --> 1484.56] be much easier than maintaining rvm uh so how much of your time do you have to dedicate to actually
[1484.56 --> 1491.04] maintaining ch ruby um it's pretty much feature complete at this point uh basically i'm sort of
[1491.04 --> 1495.30] waiting it's kind of one of the first projects where i've been really skeptical about feature
[1495.30 --> 1500.90] requests uh normally a lot of my projects i'm like always trying to please whoever is submitting the
[1500.90 --> 1505.32] issue and you know thinking up crazy new features to add this is the first one where i actually
[1505.32 --> 1511.06] really constrained myself and that was caused primarily because the lot of the line uh line
[1511.06 --> 1517.90] count uh limitation because i want to keep it the core of it in 100 lines and um of course there's
[1517.90 --> 1522.80] other additional things like the the auto switching but that's in a separate file that you can choose not
[1522.80 --> 1529.02] to load because a lot of um on a previous job there's worked with this system administrator who just
[1529.02 --> 1534.62] like cringed at the idea of having some sort of crazy bass script that you know auto detects and
[1534.62 --> 1540.64] switches rubies when you see the injured directories and so um but yeah so that really has kind of
[1540.64 --> 1544.48] constrained me and that's going to kind of really interesting where i actually really critically look
[1544.48 --> 1549.52] at features and whether they can be uh implemented by like third party tools or if they have to
[1549.52 --> 1555.02] integrate it or do we even really need them because a lot of the feature requests were uh basically
[1555.02 --> 1561.82] things that people are used to coming from rvm and i kind of think like well do we really need this
[1561.82 --> 1568.54] like or is this is something we're really kind of familiar with and we miss did i miss why you said
[1568.54 --> 1574.50] that there's a constraint why the hunter line constraint so basically i wanted to keep it as small as
[1574.50 --> 1581.12] possible i didn't want to like go out of control and you know develop a you know a sub command system
[1581.12 --> 1586.90] or any of these other things that the bigger kind of ruby switchers managers have and so i kind of
[1586.90 --> 1591.50] like i always kind of like look down on the whole idea of like putting line constraints line count
[1591.50 --> 1596.52] constraints on projects as kind of like it's kind of like a hat trick you know it's kind of like vim golf
[1596.52 --> 1603.62] yeah but really it does it does help you it forces you it like it sets a real kind of like um
[1603.62 --> 1610.02] like risk points or danger point where it's like you cannot pass this line that's this invisible barrier
[1610.02 --> 1617.30] once you do you're in some danger right and um yeah and so that that's that's kind of helped me
[1617.30 --> 1622.04] um dealing with maintenance uh there was a period when i first rolled out the auto switching that i
[1622.04 --> 1627.36] did have to deal with tons of bugs and weird shell issues and so i spent a lot of time asking stupid
[1627.36 --> 1633.32] questions in the bass irc channel and getting really kind of like burnt out uh disgruntled replies