text
stringlengths
0
1.17k
[2823.72 --> 2832.44] gem path and then passes that to the uh subshell uh process and then when the subshell initializes uh
[2832.44 --> 2839.16] basically then ch ruby loads and then it resets the gem home and gem path and so it's like it's
[2839.16 --> 2845.88] it's a dicey kind of uh way to deal with it without coupling the tool the two uh tools together where right
[2845.88 --> 2851.88] i didn't want to like have some sort of like flag of like you know do not reload ch ruby you know
[2851.88 --> 2856.56] that would feel like a little too much coupling even though if even though if it was just one
[2856.56 --> 2863.38] variable but like yeah yeah let's pause the show for just a minute give a shout out to our sponsors
[2863.38 --> 2868.46] new relic if you've got a web or mobile application you need to know about new relic
[2868.46 --> 2875.24] it's your new best friend basically it's your easy to use analytics dashboard that basically gives you
[2875.24 --> 2880.04] powerful code level visibility into the real-time performance of your application so
[2880.04 --> 2886.14] this means that you can spot bugs see bottlenecks and fix problems fast hopefully before they even
[2886.14 --> 2891.46] affect your users and thanks new relic you no longer have to ship your app to production and
[2891.46 --> 2896.10] then helplessly wait around hoping for the best until negative app reviews and tweets start to roll
[2896.10 --> 2902.80] in new relic empowers you to to see what's going on and what's what is working and what isn't working
[2902.80 --> 2907.22] all in real time and the way it works is really straightforward they give you a lightweight
[2907.22 --> 2912.94] agent that you unpackage into your production level apps that agent sits around quietly and
[2912.94 --> 2917.84] securely in the background kind of gathering real-time metrics across geographies devices
[2917.84 --> 2924.30] platforms all the way down to the end user level and then displays all that data in real-time graphs
[2924.30 --> 2929.00] so coders can have the visibility they need into the performance of their web applications
[2929.00 --> 2933.16] and make everything awesome so go and check out new relic today by visiting
[2933.16 --> 2939.16] newrelic.com slash the changelog to learn more and use the offer code the changelog and take advantage
[2939.16 --> 2946.46] of this special 30-day extended free pro trial available exclusively to our listeners
[2946.46 --> 2953.72] newrelic.com slash the changelog so it surprised me i don't know like i don't and i'm not really
[2953.72 --> 2959.34] even necessarily sure why it surprised me but it surprised me that ch gems even exists in the first place
[2959.34 --> 2965.56] yeah um it would be kind of nice if uh either this functionality was kind of like baked into
[2965.56 --> 2972.20] ruby gems itself or uh which it actually you can do i mean literally just set gem home to some path and
[2972.20 --> 2980.82] there you go uh just it's also the making sure that um the bin directory of the gem dur is uh you know
[2980.82 --> 2985.80] takes precedence in the on the path so any serve executable in there you can just run and it'll go to
[2985.80 --> 2992.02] that one and uh yeah and like that's another thing also kind of wish that uh bundler would kind of
[2992.02 --> 2997.90] invest time into doing is provide some sort of shell script you can load that will automatically uh
[2997.90 --> 3004.06] kind of like detect the bin stubs and put those in the path or use set up aliases or something
[3004.06 --> 3009.56] just so you wouldn't have to bundle exec every time yeah or install or clutter your bin directory
[3009.56 --> 3015.52] with bin stubs and like which can actually clobber existing files in there which is kind of annoying
[3015.52 --> 3022.36] super annoying yeah and yeah so that was kind of like my kind of like trying to answer that but of
[3022.36 --> 3029.10] course like it is kind of a difficult problem so is there a definitive blog post or write-up that
[3029.10 --> 3036.78] kind of prescribes how to use uh ch ruby ruby install and ch gems just for i mean we got a lot of
[3036.78 --> 3042.80] new listeners to the show that are just getting started and we have a lot of very seasoned developers
[3042.80 --> 3048.90] also using it so we kind of have both chasms um and i'm not sure if i've ever seen a full write-up of
[3048.90 --> 3053.14] like here's why you and i know you're kind of on the show to talk about it a little bit but here's why
[3053.14 --> 3058.36] i did it here's you know why you should use it and here's the implications of using it these you know
[3058.36 --> 3064.58] these several tools together is there a write-up that's just like clear as day so there's actually lots
[3064.58 --> 3069.66] of write-ups um and i kind of let users write their own uh this is kind of the first usually
[3069.66 --> 3076.06] um previous projects i'd always kind of like naively uh kind of put together this project and you know
[3076.06 --> 3081.32] think like boy people are gonna love this and then i post it to reddit and then it just gets eviscerated
[3081.32 --> 3086.90] yeah oops yeah and it's basically kind of like that whole uh i feel like some some of the some of the
[3086.90 --> 3090.98] criticism is valid but i think a lot of people um like they kind of use that as a way to like
[3090.98 --> 3097.56] pump themselves up of like kind of criticizing other projects that initial criticism can actually
[3097.56 --> 3102.94] hinder the project and hold you back and so i literally just did word of mouth marketing kind
[3102.94 --> 3107.92] of i just recommended it like hey here's this thing check it out you know you you make your up make your
[3107.92 --> 3114.08] own uh decision on it so uh users have actually wrote up a lot of different blog posts about uh their
[3114.08 --> 3120.38] experiences um so literally you could just google for like chruby and you'll find a dozen or so blog
[3120.38 --> 3125.74] blog posts and a couple actually in japanese and spanish which is kind of cool um so we're
[3125.74 --> 3131.70] crossing that language barrier and yeah it's kind of give the basic rundown of like here's how i set
[3131.70 --> 3136.08] it up here's you know here's how you switch rubies here's how you install them and here's kind of caveats
[3136.08 --> 3143.96] and like yeah because i know one thing that i've always gotten held up on was always having coming
[3143.96 --> 3151.98] from you know rvm to chruby i you know kind of depended on gem sets and i've um i've you know
[3151.98 --> 3156.50] with bundler and the way it handles things i've kind of gotten rid of gem sets i don't use it anymore
[3156.50 --> 3163.58] obviously i don't use ch gems yet and i haven't really had a need for it but i i find myself um only
[3163.58 --> 3172.28] here and there having conflicts um and is that in maybe maybe i don't do enough with ruby to
[3172.28 --> 3178.16] understand why someone would want to obviously isolate their their gem into a their gem you know
[3178.16 --> 3185.06] gems for a project into a gem set but most often the reason you know clearly is for you know just
[3185.06 --> 3190.08] the fact that you don't have any any bumps there's clear isolation from other projects
[3190.08 --> 3197.04] yeah and also you're using environment variables to achieve this and so you don't have a lot of the
[3197.04 --> 3204.00] magic quote-unquote that uh bundler does to ensure that it isolates all the dependencies right and but
[3204.00 --> 3208.88] i mean there you shouldn't you should be able to like get away with just uh migrating gem set projects
[3208.88 --> 3216.36] to using uh bundler and uh kind of like sharing gems that way uh of course you can also just directly
[3216.36 --> 3223.06] edit the path and gem home and gem path environment variables and set your gem set that that way and
[3223.06 --> 3229.10] you just have to then ensure that every time that uh project is ran it's ran in a shell that loads up
[3229.10 --> 3236.92] the configuration and um yeah so yeah actually i've been thinking about like uh there's this tool that
[3236.92 --> 3243.26] someone wrote uh called rev which allows you to kind of like add you know set and uh reset gem sets
[3243.26 --> 3248.10] and i thought it'd be kind of interesting if someone actually wrote a tool that basically just
[3248.10 --> 3254.28] pushed and popped uh directories on the gem path and then uh set gem home accordingly and that would
[3254.28 --> 3261.02] allow you to actually like more fine-grained control of the gem gem directory kind of like search uh
[3261.02 --> 3266.22] search variable the order in which it you know checks all the directories for the for all your gems
[3266.22 --> 3271.78] and so i kind of felt like you know that'd be kind of interesting uh way to do it but really i mean
[3271.78 --> 3279.26] it seems like there's a lot of confusion about how gem sets work ideally and a lot of people are trying
[3279.26 --> 3283.90] to kind of like reinvent them and explore different areas and so it's not kind of really a solved problem
[3283.90 --> 3289.80] yet yeah mind does that answer it yeah i mean it's i mean like you said it's a tough problem to solve
[3289.80 --> 3295.66] anyways and i don't think there's really a one way to do it but i you know i now don't even depend at all
[3295.66 --> 3300.52] on obviously gem sets but i kind of miss them because i have had some conflicts then i end up
[3300.52 --> 3304.76] doing something that andrew kind of mentioned earlier which is like obliterate all my gems which
[3304.76 --> 3312.96] i have just uh um i am happy to be a zsh user so i just type uh fo and up a couple times and i find
[3312.96 --> 3318.16] the most recent for loop that i've written you know that basically obliterates all my you know all my
[3318.16 --> 3322.74] gems installed and i just because they're so easy to install and it probably even upticks the numbers
[3322.74 --> 3329.02] of installs anyways i just obliterate all my gems and just you know bundle install and i'm good to go
[3329.02 --> 3333.14] in happy world but you know so that's okay with me but it still feels a little dirty you know it feels
[3333.14 --> 3338.74] dirty to not have that segregation yeah yeah and plus you know the fact that the default behavior of
[3338.74 --> 3343.70] bundlers to install into the gem directory as opposed to like installing always into a vendor directory
[3343.70 --> 3349.04] and kind of like you get that trade-off where it's like well i can clutter up my gem directory or you
[3349.04 --> 3353.46] know i can blow it up the vendor directory so this might elongate the conversation a tiny bit further
[3353.46 --> 3360.96] but you know it's it's it's uh impossible to kind of um miss the millions of dollars recently that npm
[3360.96 --> 3366.94] has gotten to become npm inc and you've got other package managers they come up to play like what is
[3366.94 --> 3373.52] is ruby playing catch up is there something new out there that's being done by npm and bauer and other
[3373.52 --> 3379.02] package managers that simplify the way they're distributing and versioning for individual projects
[3379.02 --> 3386.62] well um actually i haven't looked at npm yet i actually should do that but uh one of the
[3386.62 --> 3393.60] things that is really interesting to me is haskell's package manager uh cabal and it apparently has its
[3393.60 --> 3399.32] own concept of sandboxes and so and also what i really like about cabal is the fact that the
[3399.32 --> 3408.42] specification for your project is literally um key value colon separated plain text and so we don't
[3408.42 --> 3414.92] have this like crazy uh uh you know pure ruby gem spec which is really kind of like gem spec was
[3414.92 --> 3420.66] originally kind of designed for internal usage of you know describing the gem and we turned it into
[3420.66 --> 3427.04] this thing where we could actually uh because ruby gems uh it's faster for it to load actual ruby code