Valentino Stoll
Appearances
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
This is really interesting because we are kind of missing a, you know, a hard stance on front end in the Rails community, at least, but definitely in Ruby as well. And Opal has been kind of the closest thing I've seen. It's interesting you built kind of like on top of Opal. I know we've had Elian here before.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
talking about opal and it's like a really great work uh just so smooth of a process uh and i love your the dsl you have here uh in your to-do list app that you've made uh which is like so simple and easy to read uh we'll share it here in our show notes um so i'm like really curious a lot of this looks uh similar to kind of like the flex markup for those familiar with uh the
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
you know, Joel Draper's Flex project, where they have like a DSL for kind of building up the DOM elements and mutating them. I'm curious, like, you know, now that you've been like kind of reworking, even like React stuff, like what is, as a Ruby developer, like, I am assuming that you've developed in Rails?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, I mean, so, like, what's been your overall experience, like, as far as, like, you know, why move to Glimmer as an example? Oh, good. You know, like, is it kind of straightforward if, like, a team that hasn't seen Glimmer before to, like, make the transition pretty easily? I guess you'll find out.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
That's really cool.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
No, I'm not familiar.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
There's been so much work and to be honest, so many failed attempts as well along the way. But I think we're finally getting somewhere. Looking at your example Rails app here, you have a sample Glimmer DSL web app for Rails. People can check out as well. It definitely makes a lot more sense now as you've been explaining it. Seeing it as, like you said, the data binding aspect of
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
connecting the front end components to the backend. And it makes a lot of sense. And it's definitely like, we are getting closer here.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, totally. And so like I wanted to dig in here a little bit because what we're talking about is kind of like componentizing like these front end pieces into a more modular way that can be reused and encapsulated in more of the Ruby way and trying to keep it to Ruby as much as we can, right? Without like degrading the front end performance too much.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
And so I want to talk about that componentization, like creating these web things, right? Like if I have a form, can I make a form component? Is that like straightforward to do with the Glimmer DSL? What has been your experience with like encapsulation there?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, that's really cool. And I mean, I think that's been one thing that's caused the divide too, to be honest, in that, you know, people like to stylize and make their own web components with React or whatever framework that they've, you know, that they've chosen and handle all their, you know, front end interactions and stuff. But then
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
you know, have to request that the backend team like help supply that data or new, like as data changes, like how do you add and adjust to the component without, uh, you know, the data being there on the backend. And so you have this like dual edge coupling. Uh, and if we have that coupling anyway, why not have it all in the same place? I think it makes a lot of sense to me personally.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Um, so how, I'm wondering like, uh, you know, does this also like appease like teams that grow in skies and like have devoted front end teams? Like, is there still kind of that, is this like trying to like consolidate the team structure or is it,
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
also like supporting the idea of, okay, we're gonna have front end people that are gonna be focusing specifically on styling and adjusting the components. Like, is it still kind of a straightforward process of like HTML, CSS kind of manipulation for front end styling of the components? Or is it take more of like a, I need to learn Glimmer DSL, you know, aspect of things?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
I see. Yeah, I mean, that makes a lot of sense. Looking at more of these examples in this Rails sample, you're using an external code highlighter, which is really cool. And it's just all in Ruby. Yeah, really, really cool. So I'm curious, what's the deploy process look like for this stuff? Is it the same as any Rails app, any Ruby app? What's that look like?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Maybe I'm just old. I don't really know if that's like still used even. Is that a close comparison to what we're talking about?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, totally. And thinking more about, like, the bundler aspect of it, it makes me think of, what was it, Rails Assets, if you were familiar with that, where Rails Assets was, like, basically just a gem format where you could pull in Node-related NPM packages into your Rails asset pipeline, which was, to me, like, super great. It didn't require any of the, you know,
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
javascript packaging systems or or extra dependencies like that uh and it worked great and just bundle install and it included all the assets that you needed and handled all that and i do miss that and so i'm hopeful with this uh kind of uh push here that we can kind of get back to something like that uh which makes brings me to my next topic uh of uh turbo
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, I agree with you there. Definitely, and having the context switch constantly between the two definitely slows down the development. For me personally, I don't want to speak for everyone, but... Yeah, I mean, I feel like we've been driving like we keep talking about this.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
We keep driving toward like a more like view component style, like in an application development process that is getting closer. And this seems to be like crossing that bridge of the missing pieces to of, well, we still need JavaScript. JavaScript libraries are still helpful. Like, how do we use them in the context of our application, but not have to just use JavaScript to couple our backends.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
I see that. It makes a ton of sense. I guess, like, thinking about, like, styling, are you pretty, like, restricted then to, of, like, the, you know, operating systems style limitations for a lot of these components?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, very awesome. I'm looking forward to seeing that come together. I'm sure I'm not the only one. Yeah, me too. So like this brings me to my like last kind of question, I guess, is like the, you know, how does, are there any plans to bridge the gap of consolidating the application development to allow automatically creating both for web and desktop?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
and mobile and XYZ, like, is that a desirable future? Or is that better to keep things separate still?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, that makes sense. I know having worked with like React Native, it is painful even just between like, you know, separate provider platforms of iOS and Android and having to do Windows and Linux and managing that, you know, I can't imagine that's helpful to have to do that. for everything.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Well, this is awesome. Uh, I love seeing this work happening. Uh, and you have so many great examples here. Uh, that, that brings me to, uh, kind of like, uh, Before the show we were talking about, you're gearing up for your RubyConf talk and workshop.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Do you want to shed some light on the workshop that you're doing and maybe how people can start to get involved in a lot of this Glimmer stuff you're building?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, I was looking at their readme with all the examples. It's pretty slick. It has all of the major components that you'd want to use to build a simple desktop app. from the first glance. So very cool.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, very cool. I love to see all the examples here. How do you find time for all this?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
enhance my work experience significantly uh if we adopted in my company right now yeah totally i could see that for sure uh and i would love to see somebody uh maybe ingesting some of these examples to AI to help with adjusting to the DSL because that's probably one of the biggest aspects of learning new frameworks to me personally, at least.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
It's interesting you mentioned gaming aspects because I know the Ruby gaming engine of choice lately is DragonRuby. I know that evolved from Ruby Motions. as the de facto desktop builder application. I don't know if that's still maintained or not. Is there any comparison you can make between Glimmer and RubyMotion?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
That's awesome. Yeah. I might have to play with this around, uh, myself because, uh, it looks like a lot of fun. Um, All right, we're kind of getting to the time here. Is there anything else you wanted to share or talk about before we wind down to fix?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, I mean, you're doing it all, it seems. I love to see all of the, you know, the options that people have even within the Glimmer ecosystem. It's really, you know, please keep it up because... I think you're heading in the right way. So let's move to picks. Do you have anything, or do you want me to go first? I can give you some time.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, totally. That's, that's the path I'm going to take. Uh, so I, well, I, uh, I don't really have too much to share here other than I'm building a robot arm. Cool. By Hugging Face. It's called LeRobot. And you can train it to do things. It has like, it's two arms, but it has like a follower arm and, you know, a leader arm.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
everybody welcome to another episode of the ruby rogues podcast i'm your host today valentino stoll and we're joined by a very special guest today andy mala did i say that right andy uh andy male yep male sorry i should have asked you before uh do you want to just introduce yourself and i i'm sure some people uh have heard you before on our show here uh but just give everybody an introduction and uh you know why you're famous
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
And so you can lead the other one and show it how to pick up things and push buttons. And I hope that one day I get it to like type on the keyboard and like look at my screen and then just like work for me. But it's a lot of fun. I'm just to the assembly phase. I completed that. And it's been a lot of fun. So I'm looking forward to diving in.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
So this particular one, they have a couple different versions of the arms. But this one, you basically have two of the same kind of arm. And you can move one of them that moves the other.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
uh in the same ways so it mirrors it they call it tele operation uh but they have like you know you can have multiple robot arms so like you can have multiple leaders multiple followers uh and so uh there is a camera aspect that lets you train and learn kind of what is happening that way and so i think maybe in the future it will get to the point where you could just use your own arms and hands uh but i think right now it's just like uh because the dexterity is not there yet
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
It's just two arms and you train one with the other kind of thing.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
So right away I had a bunch of screws that were all different sizes that came in the same package and I want to just sort it rather than me sort the screws. Uh, So like that will probably be my first one because it's like they're tiny screws and they're hard to sort. And like that should be something easy or not easy, but like straightforward to train the arm to do.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
But there are examples that they have are like Lego sorting. Right. Finding the right colors. Like I think they had one example where they're, you know, pushing buttons on something else. So I don't really know what I'm going to do with it yet. it's mostly just fun to explore, uh, all of this real world, uh, AI aspects stuff. So, yeah. So check that out if you're interested, uh, the robot.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Um, well, it's been awesome talking to Andy. I appreciate you coming on again and, uh, all the work you're doing in the space. Cause you know, we need it. And I love to do more Ruby than anything else. So, uh, I appreciate it. And, uh, Yeah. If people want to reach out to you or find you on the Internet, how do they do that?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Awesome. Well, thanks again for coming on and thank you for listening. Thanks for having me. Yeah. And, you know, until next time, more Ruby on the way.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Yeah, that makes sense. I mean, he's the best tool for the best job. And I love so like, thank you for the backstory and Glimmer. And I mean, we had you on today to talk about this new, you know, thing you've been working on with Glimmer Web, which is fascinating to me. What What drew you in this direction? Do you want to describe maybe what the Glimmer DSL for web is?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
And it's because it's funny you mentioned that, you know, we as web developers are really desktop app developers. So you want to just like dive into how that correlates?
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
That's awesome. Yeah, I didn't know you won the Fukuoka Ruby Award. Congratulations on that.
Ruby Rogues
Building Better Ruby Apps: Glimmer's Component Slots and More - RUBY 653
Awesome. So what is Glimmer?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
is is identifying that use case and exposing what what you actually care about uh as far as all these things that are because i mean you know there's http logs there's like also all kinds of logs and information available that's just like emitting all the time like how do you know and identify you know which are really important uh and i i think it just depends right like
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
What are you yeah, what are you trying to capture? So it's a it's a great like stepwise way to just like start to figure that out. Right. Because, yeah, I guess depending on your role and depending on what, you know, your responsibilities are, that could change and that could be different. And your observability needs will change with that. So identifying that is probably most important, I think.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
uh, flow of things, uh, as people start up. Um, do you want to just give us like a high level, like what is observability and why should we care? Uh, what, you know, we could drill into the details of it after.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And I'm all also like, you know, let's not just add New Relic to every app that we deploy. Or, you know, is Bugsnag even needed for every app? Like, these are questions that I ask myself, too. Like, what value are you getting from all these auxiliary services that give you the observability into, like, just blanket things? Yeah.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
At what point do you stop that kind of mentality and be like, every Rails app should at least be able to get insight into the logs so that you can see what the application is doing. How long do you capture that? What kind of time frame? Do you have any default standards where you're like, well, I know that I'm going to need to look at this at some point in the application cycle.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
What are your defaults?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, you mentioned kind of some key pieces I always think of with observability in general, which is like separating the pieces into their own puzzle, right? Like we have logs, which are kind of just like our data. And then we have individual metrics that we're like snapshotting the logs for particular segments like traffic or number of people using it, like the number of jobs that are running.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And then there are traces, which we could dig into next, because I have a lot of love for all of the standards that are coming out of this with open tracing and things like that. I'd love to dig in there. But also like alerting, like, you know, how does anybody know that there's ever a problem?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, I mean, and I love, I love like thinking about it in these separate groups and categories, because I think it also helps to think about like the overarching theme, which is like getting insight, but also like, getting meaningful insight.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And like when you want really like the only the only reason anybody ever cares about observability anyway is like when something goes wrong or something is problematic that causes something to go wrong. And you want to either catch it early or, you know, try and remediate. And so like.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Where do you find like I mean, background jobs are like kind of like I feel like the first instance where people realize like, oh, like we need to start looking at, you know, what it's doing. Right. Like you start throwing stuff in the background. You're like, OK, great. Like it's doing the work.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Uh, and then you don't maybe realize if you're on the same node, like, well, those, you know, slow requests can block the web requests. Uh, right. And then, okay, well, if you split those up, finally you got that resolved, but then, okay, well, one problematic, you know, job can back up a queue that it's on. Uh, you know, like where do you, uh,
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
To me, like the background processing aspect is like why we have tracing to begin with, because it does like it's concurrency. Right. So it's like that's where everybody like ends up hitting their pitfalls is as soon as you start doing things like all at once, like and thinking, oh, like we just throw it in the background and like process things as they come.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And as things start to scale, it causes more problems as you try and figure out timing and stuff like that. Where do you find the most important pieces of making sure that you are capturing the right segments and the right flows in that process?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, I mean, it's more of like an open question. I guess like when trying to think about like one of my biggest debugging pitfalls is like trying to like reconstruct the state of what happened when something went wrong. It's like I feel like that's like one of the most typical things. It's like, OK, something happened. Like, well, like it's the data has changed since something had happened.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Maybe the change resolved the issue. But like, you know, trying to figure out what that is and going running through those questions. Right. Like. How do you think about like reconstructing data or reconstructing the state of an issue? Like, is that not the right way to go about it? Or do you try and like do something else?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Okay, so there'll be a lot of- Wait, what are the three pillars?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Okay.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
I think that you're making some great points of capturing the transactional like user information or user's actions. Yes.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
I guess I do have like maybe some specific instances where metrics alone can help like identify things. And that's more where it's like the granular metrics are the things that you're actually looking like care about. Right.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like, let's say, for example, like back to the sidekick background jobs example, like if you notice like your queues piling up and you happen to have your dashboard of metrics just looking at queue size and looking at throughput, like you can easily say, oh, like there's something blocking it and gives you kind of a point of confidence. where to look at in this specific instance.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Or as an example, like also, you know, you can notice like there's a leak in memory by monitoring, you know, your memory consumption of the app and just looking at the metrics for that and getting an alert and saying, why is the memory not stopping growing after a certain amount of time? I mean, these are like, you know, very specific examples that I'm giving, but like, uh, I agree.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like if, if you're looking for like, you know, it's not going to tell you like if your users are like back to your like token expiration, like are people having a problem with our application that we've made? Like, Uh, you know, and like, we keep getting these, you know, client, uh, you know, emails coming in like, oh, I can't like sign into your app. Like what's happening.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
You know, you can't just like take that and be like, oh yeah, it's obviously the tokens like expiration, right? Like it's your customers emails aren't going to like translate directly to that. And you're not going to know right away, uh, without having your tracing in place. Uh,
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
I mean, I would love to dig more into tracing in general and maybe more of the distributed aspect of it. Because I think what you're talking about is very important. Like, If we're just talking about tracing through a single request in a Rails app, it's not as useful as maybe where tracing really comes into play is where there's multiple things that start happening.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Once you start having more than one application and the you know, the data starts trickling from one application to the other, uh, even in sidekick example, right? If you're throwing stuff into the background, how does that data snapshot transition through the background jobs? Especially if you have ones that start depending on each other, how do you then manage the queue?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like in the making sure that you know where it started and you know where it's going, because sometimes you can catch a problem before it starts, uh, by having the traces in play and know where it's heading. Right. Uh, And so I would love to dig into those aspects.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like where do you, like what tooling, or maybe we shouldn't talk about tooling specifically, but like what aspects of tracing are most important for like holistically looking at your system outside of like, you know, running through your question. Like I think at this point we're beyond like having your questions of what you're trying to look at and that you already know what those
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
questions are and where do you start setting up tracing? Because I know at Doximity we use open tracing as an open standard for tracing and observability across platforms, languages, and things like that. Do you find that the industry standards are heading in the right direction or where are the pitfalls there? Because I know it just introduces a lot
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
of dependencies once you start to adopt a lot of these things.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, it's funny you mentioned Datadog. We've had Ivo on before from Datadog to talk about a lot of the, like, I think memory profiling. He works on a lot of granular Ruby performance tooling, really interesting stuff. But yeah, I mean, I would love to see maybe some more, I don't know, higher level examples of like making use of open telemetry in the Ruby space in general.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Because I think that level, I mean, especially with all of the solid queue or solid trifecta or whatever stuff that's coming around, it would be nice to see something like tracing specifically introduced to Rails that would make more sense in that ecosystem. Yeah. I mean, where do you where do you start profiling stuff is like kind of like an intro to tracing. Yeah.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like if you wanted to see like the request, it reminds me of was a rack mini profiler tool. Right. Where you you can just see a little tiny tab that says, oh, it took this number of seconds to load. this particular page you wanted to get. And you can click on and expand and see, oh, well, what did your application do at each step of the way and see how long each thing took, right?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
dynamically and explore the space and come to some conclusions yeah i think that's a great overview uh and your uh your your debugging uh reminded me of the i had the lucky experience of uh running rails with uh ruby 1.87 and every once in a while you just had to like
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And I think of that as like a trace a lot of the times, right? Yeah. And it's very like useful, like even when you're just starting out to see that. Right. And it helps you visualize that.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And so I feel like maybe that's what's missing is a lot of like visualization aspects of all this tracing stuff, because there's something that you look at or find useful when you're starting to dig into like structuring the traces and things like that.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
give the server a little kick because it started to grow in memory size and just, you know, giving it a quick little flush, like reset things. And you're just like, oh, I guess that's how we're going to do it until we can get like some insight into what's happening. Right. And I think that's definitely underlines the importance of observability in general.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like, you know, how do you get those insights to begin with? Yeah. And maybe that's a great starting point. Like where do you start like looking at it, like adding this insights, right? Like what's the, is there a modular approach you could take or is it more of like you should look at doing everything all at once kind of thing?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Hey, everybody. Welcome to another episode of the Ruby Rogues podcast. I am your host today, Valentino Stoll, and we are joined by a very special guest today, John Gallagher. John, can you introduce yourself and tell everybody a little bit about yourself and why we had you on today?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
you know, the new rails, like, you know, logger. where you could tag, you know, the tag logger was kind of like a start to kind of this idea of, okay, capture all of these pieces with this tag. And it's like almost a pseudo trace, I call it. But it does go along that formatting aspect of like, okay, format all the things like this in a specific way.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And I agree that there's definitely a lot to unwind there. Uh, we'll have to have you on more, uh, if you, you know, when you, uh, you know, put this together as a gem or something, cause, uh, I would love to dig into that. Um, I love the idea of the domain objects and extracting those out into a formattable way that you can then trace and follow through.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
That design decision is definitely missed a lot. Seeing things like Packwork as an example was a great step in the right direction, I thought. I'd like to see more of that evolve in the Rails ecosystem of abstracting the domains into their own kind of segments and then being able to format them for traceability and things like that. I think you're onto the right. You're onto a lot here.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, I mean, that's definitely one thing that I look for when I'm looking for, you know, installing dependencies, right?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Like does the gem have its own, you know, base error class that it then can, you know, give metadata about whatever that it's raising the errors about, like more than just like a string of some error that then you have to figure out what it is like having that extra metadata that you could just, cause you can, you can just add attributes to a class, right.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
There's no vendor you could just like pay money to and like you get 100% observability.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And say, this error has these attributes, like it, it has meaning associated with the error. I think more people doing that is definitely going to be making that easier to do, first of all. But yeah, and then also getting more people to take on that convention. I completely agree with you there. Yeah, I mean, we are getting at time here.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Is there any last pieces you wanted to quickly highlight or mention before we move into picks?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
That's awesome. Yeah, I also echo that sentiment of, you know, tooling is so important. And, you know, OpenTracing definitely is a great, great framework. And if we can improve that in the Ruby space, that'll definitely, uh, we'll, we'll be reaping the rewards as well. Uh, so let's move into picks. Uh, John, do you have anything that you want to, uh, share first or you want me to go?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, thanks. I'll definitely be digging into some of those. Yeah, I was in New York City the other day for the Ruby AI happy hour that they've been doing every couple months. This time they did demos, and I demoed this real-time podcast demo
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
buddy that i've made uh it's called podcast buddy uh and it just kind of like listens in the background and in real time like keeps track of the topics and the discussions and some example questions uh worth mentioning or maybe some you know topics to transition to uh and it's a lot of fun i just did it for fun but i recently refactored it uh to use the async framework
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
and shout out to samuel williams just phenomenal like so well put together uh the documentation is coming along it is uh lacking in some areas but i was able to just completely refactor the code so that it works with async and runs things uh you know as they come in uh and it's streaming the the whisper you know transcripts uh it performs actions in the background just
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
like in the same thread, all managed with async. Just, I love it. So check out podcast buddy and check out async. You can't go wrong. Async WebSocket. Now you can handle even WebSockets asynchronously, just like completely seamless HTTP two and one compatible. Love it. So check those out.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And John, if people want to reach out to you on the web or just in general, how can they how can they reach you?
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Awesome. I love it. Keep up the great work and keep growing. you know, shouting from the mountaintop about observability, pulling those pillars down and just focusing on the important stuff, right? I love it. So until next time, everybody, I'm Valentino. Thanks, John, for coming on and I look forward to next time.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Awesome.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, and thank you for all the joy you're bringing to people, I hope. You definitely picked the right language, Ruby. If you're not familiar with this podcast, Ruby is a very joyful experience personally. So it's very cool. I love... I've loved been digging into all of the observability talk that you have on joyful programming.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
And it's kind of a very important topic that I feel is definitely kind of... overlooked if you're starting up um maybe you get some like you know bug alerting or something like that in place as like a standard but kind of anything performance monitoring wise is kind of like a oh no like something happened let's look into it now i feel like it's like the the typical uh
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
Yeah, I love that. I love that analogy of identifying the use case in order to expose what to observe and where to insert, you know, all of these pieces that are missing or identify them really, right? Not to just insert them, but to identify them. I think that's very important.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
I think in general is like trying to identify the actual use cases in order to know what you even want to capture to begin with, right? Like, yeah, we get to throw a wall of logs, right? at a resource like Kibana, and it's not very useful.
Ruby Rogues
Practical Observability: Logging, Tracing, and Metrics for Better Debugging - RUBY 656
But once you start to abstract the ideas and use cases and how people are actually using the thing that you've built, you can definitely isolate what it is that you actually care about. And I think you're right. That is kind of the whole importance of observability.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And you could pull all that information to open up a new, you know, i use vim as my command or as my editor so i i often well i'll have a special you know method in my irbrc that allows me to open a vim you know editor with whatever the source location is for the method that i'm interested in in the context of an irb session so it ends up you know being a You can open up any editor.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
It can be, it doesn't have to be Vim. Yeah. Right. But no, that makes sense. That, that sounds really handy.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I don't know if anybody else has looked in, and not to plug Pry again, but there's actually a project called Ruby Jard that combines Pry with Bybug, and it's pretty incredible. You basically can do just like you can binding the IRB in your source code or pry in your source code. You can do a jarred in your source code.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And when it stops the execution, it has this really beautiful kind of split pane debugging session. where it shows you the current line in context, but also shows you some lower level definitions within that context. And it's pretty wild. I definitely recommend people check that out. I've been using that on a couple projects as well.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
But IRB is still my go-to for just testing out random Ruby files.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. Yeah. Let's see from, from pry itself. I'm not sure. I do know that IRB itself has introduced some tracing mechanisms and measure utility to make it easy to trace the execution of specific method calls while you're going through, as well as processing time.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So I actually do that for a lot of just quick performance testing of, will this array method lookup work faster than this one in this context? You know, just turn on the measuring processor and just check how fast it runs with each case.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, and it's line-by-line measuring, too. So whatever you enter, every single thing will show you the processing time for it, which is really nice.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
That's actually in 2.7. So if you're already on 2.7, you should have colors.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Okay. But one other thing I will note, at least with Ruby 3, actually it's 2.7, was the inline documentation. So if you just double tab while you're on a particular method name, it'll give you the documentation and the context, kind of like a man page. Oh, nice. And it does that through our docs.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So I don't know if anybody else here has a gem RC that doesn't include documentation when you install gems because it takes longer. I used to have that. Dash, dash, dash. Yeah. So I have turned that back on now because it's so great to see, you know, tab, tab. How does this method work? I use that all the time now.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, it's also, you know, if you use a higher level, like, documentation app, right, which has some nice things as well. Like, I use Dash as an example. But it has some drawbacks in that you have to know what you're looking up. And so it's nice having it in the direct context that you're in without having to go, okay, let me go to this other app, you know, look up this context, this method.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Right. I don't pay for the Dash. I just wait for it to load.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I have a thing with lightning bolts. My starting prompt is a lightning bolt. It tells me I'm in IRB. That's kind of nice. I used to, for the longest time, use... There's a Oh My Zosh theme that has a cloud.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And when you have changes in your Git repository or in whatever repository you're working with, it'll show a lightning bolt to tell you that there's changes made so you know whether you're in a clean state or not. So it's just fun. That's cool. It was kind of interesting making the custom prompt because I was just, you know, playing with it, seeing what you could do.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And so I had actually picked up the quoting. So when you're in different modes in IRB, so example, like in a string and you have a string open in line that basically has a signal to IRB to style it differently. And so, you know, I wrapped it in the quotes icon So that like an emoji quotes, which was kind of interesting to use on a regular basis for a while.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I definitely will be using some emojis in my prompt for a while now. Nice. I was trying to figure out how to get an X wing on there.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. I had dealt with IRB customizations for a long time. So I was familiar at least with the notion of IRB RC and being able to kind of customize small things. But I didn't know the extent at which you can do it. Like probably another topic of conversation or blog post is that the history itself of IRB and even kind of save those histories as files.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So you could, in essence, and that's kind of where I'm going to go next with some of our servers, is to customize the IRB session per user so they all have their own history, especially when you deal with a shared server setting. You run into a lot of, oh, you hit up a few times and You're scrolling through somebody else's history that's sharing the session with you.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And so that's an easy fix, scoping to a particular file. And so it started, you know, just small realizations over time of, oh, hey, you can do this, you can do this. And then finding the actual need was we have these hack days at Doximity where the whole team will split up and work on anything in particular that could help be useful for the team.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And one of the problems we had was this auditing in that our auditing had to be explicitly set anytime possible. any user logged into a IRB session or Rails console. And so sometimes it would be forgotten, the auditing would get lost, and we'd have to go back and readdress those data concerns. And so somebody was like, hey, it would be nice if we can just automatically do this.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And that basically is what started me down this rabbit hole to begin with. Is that possible? And there were some prerequisites to that in that, you know, how do you know what user in the system is related to the user that logged into the server? We happen to have some, you know, formalities in place that lined up those user names.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So it ended up working out really well and being easier than was expected. And then, so as you go through and once you have a custom Rails system, console, it makes you think, oh, well, what else can we put in here? What other, you know, Doximity-specific customizations can we inject inside the Rails console? Limitations, you know, how can we add restrictions? Things like that.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And it becomes very easy once you have that place, that source of truth to kind of make those customizations. And I work in the terminal almost exclusively. That's kind of why I... Because Vim, right? Yeah, because Vim. But more so, I have a very elaborate Tmux setup as well that I've just grown comfortable with. And so I try and do as much as possible. I don't like leaving the console at all.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I've been looking at a couple of projects to do even code reviews from the terminal. They're not quite there yet. But that would be my dream to just never leave. I used to use, what was it? There was a chat service for a while when Campfire was around that allowed you to do that from the terminal as well. Maybe it was WeChat, but that would be my ideal environment.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So, you know, playing around with IRB and being able to do as much as possible there, you know, open up any files, you know, send things to the background when I don't need to use them kind of thing. It's just a very nice workflow. So that's kind of my foray into the IRB space was, you know, what is possible? What can you do with it? And how can you make things easier to develop? Right.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. Yeah, I mean... IRB is basically just a REPL. You give it input and it'll evaluate the Ruby that you give it, analyze the syntax of it, and then directly show you the output for whatever that it is that you give it. So people work in REPLs all the time. If you open up any console, that's a REPL in a bash shell, basically. But Ruby's IRB kind of has a hierarchy to it.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So mostly it's for analyzing memory usage. So with the instruction sequence compiler, you can then use it to see how Ruby is making those instructions on the low level. And it's a helpful way to debug how it's compiling those instructions.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And sometimes when you're debugging a particular memory issue, you can elaborate on that using the lexical analyzer to see how it's constructing it on the back end.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, something like that. It's mostly useful for really cross-compiling What do they call it? Transpiling. I haven't used it for that, but I know, what is it? Opal or Ruby Opal. There was some kind of project where they're translating the Ruby code to JavaScript as an example. So that's primarily the value of Ripper is its AST kind of generalization.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So I don't know if anyone's familiar with TreeSitter, which is what GitHub uses as their code hinting. So anytime you've been... on GitHub in a code review and you've hovered over a method name and it shows, hey, this is defined in this file. They actually use an AST called TreeSitter that they've made with Rust. It's pretty wild stuff.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I don't know. Unfortunately, I haven't joined the Ruby forums themselves yet. I imagine that will come soon when I want to add a feature to IRB or something like that. So I don't know what they have plans for it at this moment from just the master branch of the repository. Or have they moved the main branch? I'm not sure. But they haven't removed it. It's still there.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So they at least have it backwards compatible. But yeah, I mean, the realign is really cool because mostly for the multi-line support. So if you paste it in, I don't know, 15, 20 lines of Ruby code, you can actually just scroll up and edit it right in place. You don't have to go and, you know, line by line edit and... hit up again. It's really nice to work with.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
But yeah, now that you're... Yeah, go ahead. I was going to say... There was a few years back where I was looking at... Somebody had pasted just the lib directory of Ruby's repo. And there's a ton of Ruby files in there. And at first, it's just like delegate class or something like that. Some simple ones that I could recognize.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And then you realize, well, there's a bunch of other gems in here that are... I guess this is the core library, right? That's what's included. And that's kind of what got me to... to IRB eventually is that, you know, there are all these cool things included in Ruby. And I imagine the same with Rails, right? Where there's just way too many features for you to know all of them, right?
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
But if you just spend a day and poke around, you're like really surprising how much stuff is in there. And I'm kind of hoping to turn this into kind of a more longer form series on what's included in Ruby's, you know, core library. Because there is just so much information Like you were saying, you don't even know, you take it for granted that all this stuff is there.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
that breaks all the different pieces of it into little modules that then pipe it through as it's going through and evaluating just the strings that you're giving it. And it does that in real time. And it does that basically in what they call a session and wraps that in a context and then evaluates it inside of a binding, which is really the underpinnings of Ruby code
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
You just open up an IRB session and do what you're trying to do in the moment and don't realize kind of what's all available to you. Yeah.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
What do you wish it had that it doesn't? That's a good question. I guess I wish it had more... native integrations. Like as an example, you know, being able to use VS code or something like that and, you know, hooking up IRB to the editor. So you can evaluate various things live from within the editor, which I know are kind of external to the Ruby source itself.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
But it would be nice to have kind of some more native things, even like a mechanism that would make it easier to make more extensions to IRB. Like say, for example, this jarred project, which I know is built on something that's kind of a competitor to IRB.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
But they're basically, they have a ton of modules that make it easy to do, you know, X, Y, Z. It would be nice if there were support from the, you know, Ruby core team or something like that, that could help. expose what's available and make it easier to extend and say, hey, this is how you do it kind of thing. Right.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I know. It's hard to poke any holes. I mean, they already add extra features that I wouldn't have thought about. Yeah.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Ruby's own core evaluation is the binding object. And then through the binding, it can basically compile Ruby on the fly into low-level code and do whatever it is that you tell it to do. You know, IRB, it's kind of like what gets you really into Ruby, right? You go and you're trying to learn a new, like try and learn any new language, even JavaScript as an example.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
You'll go and what do you do is you open up the JavaScript console and you try and play around and move elements around or, you know. try and be the first to purchase a pair of sneakers or something like that. But, you know, learning Ruby is so easy. You don't do the same thing. You open up an IRB session and they just type anything that you want and you can play around with the language.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. The first one I'd definitely recommend any developer out there is called Git Reflow. It's a tool I actually built a long time ago now. It helps automate your Git workflow. So it creates pull requests automatically for you. It makes sure to close out all your branches when you've merged down to your main branch.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
It does a lot of things that just save a lot of time when you do over and over again. So I highly recommend check that out. Another pick I have is for an app called BitBar. If you're using the Mac OS, it's a nice little kind of menu bar generator. So you can run scripts and show icons and various things on a periodic timer, which is kind of nice.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So I use it as an example to see how many Docker containers I have up and how much CPU it's consuming because Docker is painful at that. And a... Let's see. I had one that just escaped me. Oh, yes. Twilio. Twilio is incredible. I used it not too long to... Not to shout out to Python, but I used it to... automatically orchestrate a AWS server for my kids to play Minecraft with their neighbors.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So all I had to do was send some commands to a specific Twilio number, and it would start firing off commands on AWS, which was really cool. So that was kind of impressive how seamlessly that worked. And their documentation is really well really well worded and mapped out. Nice.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yep, that's the one. Awesome. Yeah, it was a little painstaking to get set up and configured it. I kind of hoped at some point to find some time to automate this so other people could just spin up their own AWS server that you can whitelist IP addresses on the fly using Twilio app. Cool. Maybe I get to it. Otherwise, you can go through the setup I went through.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
to get it all configured on your own AWS account. Looks good to me. It was really fun playing with Lambda server and things like that to kind of just spin up EC2 instances on the fly. And my goal was to just drive the price down as much as possible per minute, which is where I got to a nice comfortable spot with spot instances.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So hopefully I can get back to it to make it easier for other people to kind of do the same thing. But right now it's just a series of Lambda scripts that just make it easier to spin up stuff. And how much does it cost you to actually run this? My monthly bill is maybe $3 to $5 a month. Oh, okay. I feel like, yeah, on average, it's around $3. So, I mean, they use it regularly.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
It's definitely been the cheapest I've found, just not time-wise.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, it's pretty great. So when I... What I ultimately did is made a way for just some environment variables as, you know, the allowed admins to whitelist IPs, which basically just become the parents, right? Right.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So then any parent that wants to be able to get their kid to join or, you know, to stop their kid from playing or anything like that, they could just text this number and say, hey, like, you know, remove this whitelisted IP for now. And then it cuts them out of the server, right? Yeah. No, that makes sense. Yeah. So it's been really helpful, you know, just to help.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. I'm a software engineer at Doximity. I've been working there for...
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I mean, it's hard because like you said, like, how do you trust any one of these servers outside of Minecraft's, you know, realms or whatever it is. And, you know, that that is great, too. But then like any of their friends have to be in the realms also. And it becomes this thing of, OK, well, who's paying for what? Right.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I have all that backed up to S3. Right. That's how that works. So then, you know, when they turn it back on, all their stuff's still there.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Well, I'll tell you what, Minecraft servers are not that hard to get configured and spin up. So at least there's that for you.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So coming into this, definitely the customization part.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah. Yeah, luckily I haven't hit that wall yet. My kids aren't as demanding with the mods.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
of the prompt itself so i believe it was matt swanson that i discovered the uh you know customization of the prompt for when you're in a production server that you could just signal hey this is a different server than your development console you might want to be careful what you write in here and from there it kind of just exploded into okay well what else is in this
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, I'm on Twitter. T-H-E, code name V, the code name V. Find me on GitHub at Codename V. I have a blog where I post about my experiments with embedded systems and Ruby. That's at least been what I've been writing about currently. And that's blog.codenamev.com. So that's where you can find me. Awesome.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
You're welcome. All right. Honestly, let me know how that goes because I've been the only one that's used it so far. Will do.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
quite some time now i've been working on ruby quite a long time and it's kind of my go-to crutch of a language if you will but i really enjoy uh hacking away on embedded systems with ruby that's been my my latest craze and you know i i've really been digging deep into the ruby core library and kind of just exploring it and uh it's really not that scary so i'm hoping to kind of
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
customization and you know you open up your you find out you start you start with the irbrc as like your starting point and it kind of leads you into the rabbit hole of customization and what i realize is that you can basically make this file that will evaluate anytime you open up irb and do whatever you want with it so anytime you're trying to you know open up
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
specific set of code in a specific context, you can make a custom IRB file for whatever that context might be. So that was probably my biggest, you know, aha moment. And as an example, what we eventually ended up doing at Doximity was making a special Rails console that tagged the system internally
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
to say, hey, any changes made to the database, you know, make sure they're attributed to whoever the current user is. So we implemented that and then allowed, you know, full auditing for whatever user was logged into the system, you know, with just a simple little Rails customization. Gotcha.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, more for accountability than anything else. You say, hey, what were you doing during this change? Sometimes you just need to audit the specific scenario of a change so that you can go and make sure it didn't affect anything else as a side effect.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Short answer, no. I mean, there's a kind of a discrepancy here. And it's two worlds colliding where somebody made a better IRB at one point. And now kind of the features of Pry are sneaking into the native Ruby IRB. Which is awesome. Yeah. So, I mean, they're very... They're completely different things at this point.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Gotcha. Yeah. So as far as like what Rails is doing, it's probably just an elaborate IRB RC thing. Because anything you have in your IRB-C will be in the context of whatever ends up being the IRB session you're in. So when you do Rails C, I imagine it just loads the application and makes a few things available to the terminal, like the reload command or something like that.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
That's kind of the value of the IRB-C2 is like you can define methods in there that do whatever you want. So, you know, Rails has the customizations with a bunch of methods that it'll inject into the session and, you know, give you that available. So I have some myself, which will give me me. as an example.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Make it a little more approachable for people and hopefully get some more contributors out of it, including myself.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So then I have a who am I, basically, that gives you access to your current user's name and a bunch of related ones to that.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
I mean, what you could do is you can make your own input method that then remaps all of the characters. So as you're typing, it'll output a different character. Yeah, yeah.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Not technically the IRBRC. We have a custom initializer for Rails itself that will just make some modifications to the Rails console itself and then start up kind of call super on it.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, that's right. And I mean, the customization of the prompt, too, is just hugely helpful, especially when you have to jump context through many servers. So we have at Doximity a series of staging servers that are separate from development, right, so that we can add quality control and test out a lot of our changes. And then we have several production servers that are all different.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And it's nice to see them labeled so you know instantly, especially if you have a bunch of different terminal windows open that all have an IRB session in it. You don't want to get confused about... which one you're in. Right.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah. And I mean, we don't all have access and it's certainly limited.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
For some projects I have, primarily I've been working on a Raspberry Pi. I'm no expert, so... I picked up one of those starter kits that has a bajillion tiny little components to work with and slowly chipping away at converting some Python examples.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Sure. I know a couple. I mean, a lot of these are brand new, like in Rails 3. But there was just merged a pry-like ls command. So you can basically list all the methods on a particular object. as an example. I imagine the next step to that would be the cd command to pry, where you can basically move into the object.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
And you can kind of already do that with IRB, because you can run IRB on any Ruby object and enter inside of the context of it. So if you make an instance of something and you IRB that instance, then you're in the context of the instance. And you could do the same with the class and pretty much any, you know, object in Ruby. How do you do that? How do you go inside the objects? Sure.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So when you're in the IRB console itself, you just run IRB and then the object. So if you did, you know, string new and you just said IRB string new, you can enter inside the instance of a string and play with all the methods. You don't have to do the string's object name as a variable and then dot whatever. You just enter the method.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
So it's kind of a fun way to explore the object without having to run a bunch of chained methods.
Ruby Rogues
The Hidden Gems of Ruby - RUBY 651
Yeah, and I mean, another cool thing which Pry gives that maybe you just don't know about IRB is you get a lot of context from the source code just using the method method, right? So when you say, you know, method and then... colon some, the name of some method, it returns a special Ruby object that describes what the method is, what it does, the source location.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
like a domain key or some kind of identifier that can be like, you know, securely matched when the handshake is made using their service from whatever server that you end up using. In my experience, it's honestly very rare that that actually happens.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
That makes a lot of sense, you saying that your customers mostly store access tokens because most vendors don't give you that whitelist ability and handshake process, which is very important. I think it causes a lot of the breaches when it's not there.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Is there an open standard that is following this process or no?
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
So I love this. You have this great secrets for all page on Doppler. I link to and it's really great. Kind of helps you quickly assess your risk exposure based on your team size. You go through kind of like a quick calculation. Oh, we have like this number of projects, estimate number of secrets per project. Then you have a certain number of environments, right? So it's a multiplier.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
And then you have, you know, a multiplier over the number of team members too. And so those quickly add up and you make a great point, like, you know, the malicious actor, they only need one, right, of the thousands that adds up to. And so I'm curious, like, you know, from the, like the whole point kind of is like risk assessment and remediation, right? And like, do you find that, you know,
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
focusing on the that risk aspect is just as important as like kind of the secret storage management mechanisms yeah they go they go hand in hand for sure you need something that developers are going to want to use that is secure when they do use it and you want to think about that risk like
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
So I'm curious, like, if you have any tools or, like, what would you do to kind of, like, visualize the, like,
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
know organizational structure in the in combination like it's more than just like secrets management it seems right uh like how do you how do you personally visualize like the security aspects surrounding the secrets and who accesses them and things like that uh to understand kind of what is happening and where the access points are yeah great question uh truly a great question um
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
What inspired you to start Dropler? Where does this story start? I'm curious where your background is and how you're like, oh, we need a better secrets manager.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
So I'm curious, like, what are some common, like, preventable breaches that you've encountered? And like, How can developers avoid them, right?
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, I think you make a great point. I mean, being able to respond quickly is definitely like high up on that list and being able to remediate that as fast as possible because it will happen. Like you kind of just like have to go with eventually something will happen and you have to like just stop it as soon as possible.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
And in my experience, just having that ability to move quickly to rotate things around has been like the best thing defense in the long run, at least from minimizing damage. Right.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, this just reminds me to a story. I forget what the company was, but some some like, you know, software engineer at a big company had a home Plex server and the Plex server was outdated and it gave like, uh, you know, access to their home network and on their home network was a work laptop that they then were able to gain access to because it was on a shared network.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Uh, and then from there they then hopped to remote systems. Uh, and so it's like, uh, you know, the, you're right. It's getting much more like, uh,
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
We use a lot of AWS stuff to handle a lot of the... They have a secrets management deal in there. Yeah, and I think it may even be isolated from the main environments too and handled that way in an isolated environment. We use Docker as well, so It could be like an isolated container that then feeds back into the other container.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Is Doppler part of the GitHub secret scanning part of the program? Yeah.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, I'm curious on that. as far as the observability goes, what are the latest trends happening now for observing secret use and maybe detecting bad actors ahead of the breach?
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, I think so. Something like that. It may even be one step further where it's in AWS and then at like run run time. It's like the secrets are loaded into the app's memory for the particular use case. I don't really know all of the details, to be honest. I'm not on the infrastructure team. Everyone's like, well, we have to rotate keys. And that's definitely an easy process for us.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
I'm going to have to go back and listen to this and then go through all my stuff. Run your checklist. Yeah. Do you have a checklist, Brian, of like, you know, at least run through this for your projects or your team or do you publish anything around that?
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
But yeah, we have some command line that does it. It's not just like changing the environment variable.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Sure. Uh, yeah. I mean, the first thing that comes to mind is the dark net diaries podcast, which is just like an incredible resource of deep diving, uh, exploits.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Uh, and just like people are just so creative out there and, uh, nefarious or not, it's just like wild to see what, uh, what kind of attack vectors there are and how people are using, uh, and exploiting your behavior, uh, which can be patterned. Right. Uh, So I'd recommend if you're interested in any of that kind of stuff, it's, it's an awesome show.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Next to that, I've been following a lot of the rails world fallout, which is just like, I definitely missed out. I don't want it to go to conference. Yeah. There's so much, so much great stuff that I'm just watching from afar come out of that. And it's really exciting. Uh, so I guess just watch the, uh, YouTube channel for updates of, uh, new talks that are coming out of there.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Um, and then the, the last pick I have is, uh, Landon Gray. Uh, he's in the Ruby AI space and, uh, he basically made Streamlit, uh, for Ruby, uh, which I'm really excited to, uh, mess around with. And if you're not familiar with Streamlit, it's kind of like the, uh, you know,
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
I don't know if it's JavaScript or it's some other language, but it's what a lot of the, you know, machine learning enthusiasts will use to just quickly get up a chat and, you know, fine tune or use LLMs in creative ways. And Langchain has kind of like promoted it for a long time for just quickly iterating through AI products development.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
And it's been really incredible just to like quickly get up and running on something new. And so I'm excited to see that come to Ruby in a very like Ruby way. So it looks very much like a, you know, a rack app or something like that, where you can just run it and it has a chat that you can use. And I'm really excited to see that develop more.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, that makes me curious because I think at one time we were using... I forget what HashRocket's product is. We ended up moving away from that. Yeah, I don't know. We were using some vendor for doing the secrets management. But yeah, having a command line or some kind of central place, a command line doesn't even need to...
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
be your UX of choice, but just having the centralized place where all of that access points happen, it definitely helps isolate and track, to be honest, who's touching what and changing it. I don't know if Doppler has those kind of features as far as tracking changes and getting the full logs and things like that, but that's definitely been super valuable.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah. That's always makes me wonder, like, cause there's two parts of this, right? Like we have the secrets and then there's like the whole encryption aspect of it, which is his own separate beast of the discussion.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Well, what you're, I mean, ultimately what you're using a lot of the secrets for, I would imagine is to encrypt something or, or even to, yeah, I mean, to encrypt stuff.
Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Yeah, that's all. I always want to, one of the biggest things that, uh, I always hope for when I'm like getting a new vendor, like access token or whatever it may be, is that they like have some kind of like, you know, whitelist stability with like either their domain or
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
I feel like, you know, like a lot of people don't like they like to draw parallels of like front end coding to back end coding. And like, you know, if somebody wants to switch to Rust, like, you know, that's a much steeper learning curve than just switching from jQuery to React or something like that.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
So how do you assess switching to new technologies or adopting new things? What is your thought process on doing that?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
I'm curious on your thoughts about this idea, because I have a total agreement, fewer dependencies the better, but at the same time, some dependencies are like, it's better to have a community building and identifying bugs and
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
resolving features like what are your thoughts on that like how do you gauge like whether or not like community support around a certain feature set or technology or gem is like worth it uh over building it yourself yeah i mean for a start i suppose you have to have to look at the activity on it don't you if it's an active gem then
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
At least you're not someone like ThoughtBot that has like all of their clients using their thing and that they now have abandoned and upgrade everybody and worry about that. But I'm curious, like, so let's take a look at the dependency, like, aspect of things. Like, do you ever look at Rails as, like, do I need Rails, like, kind of thing?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Because one thing I... I've been to a lot of, like, you know, non-US-based or European-based Ruby conferences. It's, like, very much, like, absent in those community Rails. It's, like, not kind of, like, the preferred choice.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Yeah, for like, you know, just Sinatra or like, you know, some other web framework or just like Ruby specific app. Like they're just running Ruby itself. Like, do you ever like think about whether or not like you need, you know, Rails for something new you're building? Like, can this work as a spreadsheet or like, is this better as a command line tool?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Like, do you ever look to other things or is it just like default at this point?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Yeah. Dave is action off too. That's pretty great.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Ali, I'm curious, like, you have a lot of experience in, like, product development and, like, the business-focused aspect of, like, building things, right? So I'm curious, like, what your thoughts are on, like, you know, where... the technology is most helpful in the process, in the business side or developing the product?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
And why are you still sticking with Rails at this point with all of the other stuff that's available? Is it familiarity? Or where do you see the technology really aligning with that aspect?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Is there an example in Rails where you found that feature being there just saved you a ton of effort if you had gone with something else in the moment?
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
It's funny because we talk about your PDFs example as being a great use case for Rails. I feel like files in general, if you want to just get a file upload working, Rails is great for that. But, like, if you want to cache it the right way, it's very complicated. But I feel like that's also true of anything, right? Like, getting CloudFront hooked up to any app in any language is a complex process.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
Yeah. And then how do you, like, you know, what is the famous saying? Cache and validation is, like, one of the hardest, you know, naming and cache and validation. Oh, yeah. Absolutely. Is there even a way to simplify this? Like...
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
I've been working on this fun project called Podcast Buddy. He's actually listening right now. It's an AI companion that just lives in the terminal. And I can ask him questions right now, but I don't know what he'll respond with. So I'm gonna...
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
It's not polished, but at the end of the episode here, he'll create some show notes for us on what everybody's been talking about in a nice organized format with links. So it's really fun. I use it for meetings too. Another version of it, I have a meeting buddy. And it's just so much fun playing with Whisper and doing things locally with all these LLMs and audio. It's a lot of fun.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
So check that out, Podcast Buddy. And then I've been... I found this... Somebody has this project called LeRobot where they're building a robot arm that... has like a trainable robot arm that comes with that you can build with it to train it to do different things. And so somebody created a tutorial on how to do it all. And so I printed, downloaded all the files and printed out all the parts.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
And I'll be building that just for kind of for fun, train a robot arm to do different things in my office. So we'll see how it goes.
Ruby Rogues
Cloud Migration, Server Costs, and CDN Challenges - RUBY 650
This looks incredible. Thank you.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I hope they borrow from Chris Oliver's Notice Gem. I've used that in the past, and it's very straightforward and doable.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It does add to the list of gems that people will have to migrate away from. Yeah. Yeah, that's kind of frustrating.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I'll wire codecs. Check it out.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But we're just watching the stream come through of all of these incredible updates that are just getting pushed out and released and announced today. Some of them we already knew were coming, right? Some of them we didn't. Ayush, do you want to like maybe mention your top highlights so far?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, on the topic of books, I saw Obi Fernandez posting an update to the Rails way, now the Rails 8 way.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I'm excited. To be honest, I'll probably learn all the new Rails 8 features by reading that book.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I'm interested in Kamal. I'm kind of waiting for it to just mature a little more. All the transitions of traffic, as an example. There's a lot of shifting sands still. I don't personally use it every day. Yeah. Just from what I see, it seems to be like a lot of the infrastructure is changing around as they start to learn more and more the edge cases and configuration options and things like that.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
So I do have a couple of like, you know, Doku apps that I would like to migrate eventually. But I'll probably wait till next year, to be honest, just to like let Rails 8 like settle and have everything more firmed up.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah. You make a great point, like, why have Docker if you have one server?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I mean, I feel like it's definitely, like, a foundational choice, right? Like, I think of it as, like, Legos, right? Like, where you have, like, you know, if you just build Legos on a table, like, yeah, that's fine, but you have, like, a sheet where you're, like, sticking the Legos to the build your, you know, thing. It's a lot easier to, to build it as it doesn't move around.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
And I don't know, I feel like it's kind of like that as it's like laying the foundation for you to add more stuff that, you know, eventually you're going to need to add it.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
You know, I feel like the, the probability of not extending what you have if you actually make something that, you know, you use every day, it's like very low chance that you're not just going to add something new to your stack. And so I like that it's there, right? Like it just, it is like the modular framework for that aspect of things. Yeah.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But at the same time, you know, Docker development is like, it definitely slows you down. Like there are edge cases that you can't even imagine from using platforms, right? Cross-platform use of like a single interface is like, it never works out like smoothly.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, that's a good point. I mean... distribution of an application that's bundled up. Like if you're not like creating an executable or something, right. Yeah. Like how do you do that? I do like, we had Andy on about, uh, the glimmer project. Right. And I did like, I like that kind of idea of like literally packaging something up as like a binary.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
And like, that's how you, I mean, cause that's a great way to ship things. Right. It's like, okay, those cross platform, like distribution is like already set, established and pretty straightforward. And glimmer is one of those frameworks that, uh, makes that process easy. Right. And like the whole, like, uh, you know, Dragon Ruby toolkit for game distribution.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I feel like all that's really missing. And I know that like Andy was mentioning that he's trying to work on that, you know, front end aspect of the Glimmer project. But yeah, that's what's missing is kind of like the web side of that distribution where we have like the browsers now, which I think the... you know, I thought the goal of the browser was to be that distribution platform.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But it's like the competition between the browsers has just like stifled progress, like so much, like it's kind of remarkable. People are just like, okay with that. Like, yeah, we're just going to like, you know, no, no problem. Like all these browsers are competing. So like, we're just not going to have a distribution platform for, you know, web.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I was hopeful with Travel Ruby or something like that that we'd see maybe something a little more progress, but I guess it's hard to sell that, right? If your end users are all distributed, how do you deliver the best thing, right?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
That does bring me to another announcement with the Turbo, what is it?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Hotwire Native? Yeah. Yeah, because we did, we had, I'm blanking on his name now.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, Joe, we had Joe on before a few times, I think. Oh, okay. He was talking about Turbo Native and the progress that he was making there and apparently has been collaborating, right, with 37signals. Yeah. Which is really exciting because I know the last time I was messing around with that, it's, like, pretty decent.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I mean, they're still, like, still got to write some Objective-C or not Objective-C, but, like, Swift and Android. Like, a small amount of code now.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
yeah and it it's it's gonna be hard to stay away from it with all this apple intelligence stuff uh now even increasing the hype uh and i imagine you know there's a google version of that out there too uh you know drawing more and more people to their mobile devices yeah quite possibly yeah but i don't know i think
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Why?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I will say, like, just taking a step back to the conference again, Rails world. I mean, it is packed. You see the audience in a lot of these photos. And it's kind of exciting to see, you know, people all over the world coming together, making this stuff happen and shipping stuff. It's, you know... There's no way Rails can be dead with that crowd.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, that's fair. You always prefer your own tools in the end.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah. I mean, it's hard to, you know, it's hard to sell somebody focused on front end, like a framework that they don't understand, uh, And it's, you know, likewise the same way, right? Like I know a lot of front-end people that are like, you know, very happy with, you know, Next.js or something like that. And they're very efficient in it and it makes them productive.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Like, you know, why would they switch to Rails? And maybe until they need like file upload or something. Yeah. No, I don't know. There are some things in Rails that do just work, and they make things very easy. And so I feel like the more we can expose what those things are and how easy it is, the more people will adapt to it, for sure.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I'm with you. I feel like I've seen, you know, we've all kind of like been preparing for this, I guess, solid trifecta that they're calling it now. But yeah, I mean, it definitely makes makes me happy to see, you know, more and more not have to get set up when you first start up a new app. There's nothing worse than configuring something when you just want to get going.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
So what's something I'm curious, because you're kind of all over the place in the stack. What's something from Rails that you use that you've used in other frameworks that is just unparalleled to using Rails with?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I agree there. I mean, it's a little tricky because like I'm still trying to find the right like, front end magic, right? Like if I want to like, I don't know, add some like UX flourishes using some, you know, MPM package or something, uh, there's like kind of eight different ways to integrate that into the real stuff.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Uh, and so, I mean, I, I know that like, you know, there, there is some hope in the, in the pipeline coming. Um, but it's still very much divided on how the best approach is, like the standard is kind of still not firmed yet. I don't know, what's your impression there on like, you know, integrating front-end components that are external to the ecosystem?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah. It's funny. You mentioned Joel Draper.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Flex guy. It made me think of the flex guy.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah. The view component stuff that Joel Hawksley is working on is, is really impressive. I mean, there's only, there's always so much like coming out there too. And I, and I, It makes me think of Joel Draper, who is funny. They're both Joel working on similar things.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
With the Flex repo. I mean, I just saw... I've been following the... F L E C K S. Uh, which basically makes like a, uh, bi-directional, you know, data coupled view component basically with flex, uh, that you can like serve asynchronously over web sockets. So like get updates, really cool stuff, uh, where you get kind of like the data coupled, uh, backend to the front end in a single component.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It's like really neat. Uh, To be honest, the whole Phoenix live view, which has been out a long time, right? Yeah. I've been waiting for something like that in Reels for the longest time because we're close with Hotwire. I know that was kind of supposed to be
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
uh the driver for that it is still a little bit clunky i think with all the ids and trying to manage what streams to what and what what file holds what update right and what gets executed where it's still a little bit hard to follow uh yeah it is i've not used live view but uh live view is obviously purpose built for one thing and stuff like action cable and and uh the
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It's a, it's funny that like, you know, Vue component as an example, hasn't like kind of made its way into the Rails ecosystem with how, with its longevity, right?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Obviously there's some trepidation for a reason, right? Like it, it does introduce kind of some, you know, DSL that you have to be familiar with and it's not quite as realcy as it, It could be. I guess it's more the Ruby way than the Rails way, which is kind of funny.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, it's funny because I remember, you know, I haven't done view components in a while, but the last I did, it was like great encapsulation. You know, you could test the changes that get made to your component. It's encapsulated perfectly. And you know, when you mutate the props, the actual HTML gets rendered, gets changed in specific ways and you don't have to worry about it. It's all Ruby.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I mean, there's a lot of appealing qualities of it. Um, But yeah, I feel like it becomes the same like front end issue of, okay, well, how do you extend it? How do you like add these custom components or custom features? And then you end up tied into the DSL of the framework and because it's its own framework. And I feel like Flex kind of has the same issues there too, right?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
If you wanted to create your own, you know, element or something like that or component. It's not exactly straightforward because you have to follow however the framework has it set up. And all of these things go against what most front-end people do. So I feel like the Rails and Ruby developer ecosystem that's full stack slowly gets narrowed in as you get to the front-end.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It's been back-end heavy for a long time. It's been shared. It's getting wider, right? But I feel like even still that... your audience narrows quite a bit when you get closer to the front end side of things.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Well, I think it comes in, I'm torn, right? Like I've been at a small organization where having full stack people is, you know, very beneficial. And like when you have fewer people, it's just easier to move faster if everybody kind of touches on all the same things.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But in a bigger organization, too, it's like kind of nice having people that just devote themselves to like making sure front end components work smoothly. Right. Or like once you get a design system in play, making sure that all the components are uniform across all of your applications and making sure that like things is like it's a smooth experience for the user.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Right. Yeah, I mean, the last leg of this is wrapping everything in WebAssembly so you could just deploy to anywhere.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
You know, UX is like on its own is amazing. probably its own, you know, field. And so like, if you have a team devoted to just UX, like the number of backend things they'd have to work on is going to get smaller and smaller as they start to, you know, work on more and more of that system that they're building, to be honest. And so it's like, it's a double-edged sword really.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Cause like maybe for like, maybe for most people working in Rails, right? Like you want that full feature set and full stack mentality. Yeah, as a larger entity, it just like becomes less and less attractive or desire, like your need for it starts to thin out, right? After a certain point. So I don't know. The problem is like we need both.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
yep I don't know the desire for specialists is like kind of still important right like yeah yeah it is you're still gonna need somebody to work specifically on security at some point if you if that's part of your core business right and or if you have regulatory aspects of your business you know you're gonna have these specialists that are in demand no matter what so I don't know the
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It's hard because as a perfect example of security, active record encryption is awesome. When they were first releasing that, they had a third party auditor come in and make sure that all of the encryption stuff, because nobody's working on encryption stuff specifically on the Rails core team. I mean, there are a handful of people that have knowledge of it, right? Yeah.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
yeah which i don't know will happen in our uh near term but uh you know what one thing i noticed from the feed i was curious uh what you thought about uh it's kind of what's coming in rails 8.1 which are like the three bigger features that i feel like have been missing from rails a lot which is the action notifier the search and uh house md which i thought was funny is a markdown editor
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But they're not, like, working on the new algorithms, you know?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Right. Yeah, like, what are they sneaking in, right? Yeah. Yeah, it just reminds me of that. And because Adam Gordon Bell, he has this great podcast, The Co Recursive Podcast, and he had somebody on. They did this whole like dialog, like reenacting that security incident recently.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
that made it into the compiler kernels, um, from some like, you know, Chinese co-conspirator supposedly like, you know, they don't really know like too much of the details, but just like, you know, part of the, I forget, was it the GNU compiler? It was some, something tangentially related to the assembly aspects of compiling, uh, where they were able to get like, uh, you know, a, uh,
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
I don't know, some kind of permutation to the compiling that made it inject code with anything that was compiled with it. And that spread like crazy. It was just a very interesting dialogue. but eventually think of this stuff, right? Like, you know, what else is just like in there?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
There's no, I mean, you'd be selective of your contributors, but I don't know that that's a, like a long winded thing about, you know, specialists really, but like, you know, I don't think we should shy away from them. And you know, the more we can keep things modular and accessible, the better that the framework will be. But,
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I don't disagree with that. I think having the tools and the framework that makes that easier to do the better, like all these generators are great. I mean, to be honest, I would like to see some improvements there to the whole generator aspect of things and customization, uh, which I know you already can do, but, uh, I don't know.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It seems like, uh, not straightforward as a first time user on like what you can generate, what's available, like the, you know, that is definitely discoverability is definitely still a problem yeah which the the guides are great i'm so happy to see all the documentation you know getting the tender loving care that it needs
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But, you know, it's still like discoverability problem is, you know, even on the development side is still an issue. I don't know. What do you what do you point people to that? Like, let's say you're talking with somebody on the JavaScript side and you're like trying to convince them, you know, hey, like, it's not so hard. Like, what do you point them at?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
That makes, somebody should go create a Ruby toolbox for Rails tutorials, right? I feel like there's value, so much value there.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Or buy Ayush's book. Go ahead.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Honestly, that book is so impressively, like, large and, like, covers all the topics you could possibly need. Like, we should be pumping it out there because, like, honestly, hey, if you have questions about that Hotwire framework, like, it's in there. The answer is in there.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
So what else do you feel like you're missing out on in Rails world?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, you know, you're in the European region too, which has so many great conferences. Yeah, I understand totally. I actually have FOMO myself about all those great conferences that are there that I just probably won't ever get to.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, Edinburgh is beautiful too.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Well, we've talked about so much here.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
We're going to have to have some follow-up talks with some of the co-creators here.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, got a couple of names. So many great insights there, you know, what's coming out. You know, it's hard to use it all, you know, right away. So it'd be good to expose kind of how it all works and how you can benefit from it because I want to know.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
All right, well, is there anything else you wanted to talk about today, Ish?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Awesome. Well, let's move into our picks. All right.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
You just released another version of the book, didn't you?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Awesome. Yeah, I'm going to have to check these out. So I have just a couple of picks here. The Ruby AI happy hour is happening in New York City. This time they're doing a demo night. So I'm excited to go to that. Actually giving a demo of a project I started called Podcast Buddy, which I hope to have on the show soon.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
But a little AI companion that can join and answer questions, describes the whole thing and summarizes events and things. So I'm pretty excited about demoing that. And I was hoping to get a fully offline version of it working. But the, you know, the talkback aspect of it is like very much just like a speak command at this point to OSX or Mac. Yeah.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Otherwise, there's, like, servers involved and, you know, way too many dependencies to get the text-to-speech working just right.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yep. So check it out, Podcast Buddy. You can run it. just in the command line, and it'll transcribe your conversation. I use it for meetings, too. It's great. Fully offline transcription using Whisper CPP. And next to that, I was revisiting something, one of our projects at Doximity called Simple Kick. It's a job orchestration for Sidekick. And it's fantastic.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
It gives you like ways to run jobs in parallel and orchestrate many things at once and get callbacks when things are complete or if there's failures. It's super useful. And I would definitely recommend checking that out as well.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Simple Kick. So simple and then K-I-Q.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
And we build it right on top of Sidekick itself. And it does require Sidekick Pro, but
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Oh, yeah. I mean, I have a few things working with this and it just it does. It makes the whole process just like so streamlined. Nice. Easy to reason about. Well, that's it for me. I hope everybody out there is enjoying Rails world feed as much as we are. And hopefully we can get some of these, you know, some of these speakers lined up here and dig in some more on the details coming soon.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yep. Until next time, folks. Valentino out.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
You bring up a great point. That's actually one thing I've been a little bit concerned about with Rails in that it's As things grow and get some solid foundation framework-wise, the need for reducing bloat becomes ever greater, especially as the number of maintainers doesn't really increase too much in proportionality, at least. Uh, so I do worry like, right.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Well, welcome back to another episode of the Ruby Rogues podcast. I'm one of your co-hosts today, Valentino Stoll, and I'm joined by Ayush. Ayush, do you want to introduce yourself?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Like I've noticed not just with, uh, tricks, but other, you know, pieces of the framework that very similar feedback, right? Like it's very long churn process for changes that really don't affect anything.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
That book is so huge. I just imagine a minor update is really like a book in its own capacity.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Uh, and so I, you know, hopefully, uh, you know, with the rails foundation and everything like that, that is on the radar. Uh, You can make sure that the maintainership at least stays up to date with the progress of the rest of the framework?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I mean, I don't know that they have to throw funding at it. More just like organizational, like, hey, we have this increase in the code base, and we need maintainers. The organizational stuff, I feel like that's where I was hoping that the foundation would add to, right?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
so that you know cases like this where you know we we have like only so many limited contributors uh that have like you know approval access to just merge something right uh which is good you know both good and bad but it's like definitely adds a bottleneck um and so i i would like to see something where like i don't know people can vote people in to contributorship right like where
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
uh, we can create a pipeline that just like makes this process easier. Cause like, to be honest, like somebody going through and just like approving a bunch of the documentation stuff, like that would be huge help, you know? And I know that, I know that's somebody who's probably already like working on that, but like every one of the rails repos, like,
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Well, you know, I got to hand it to Shopify. They seem to have, like, at least solved that issue with Ruby itself, right? Like, they had their own fork of Ruby for a while, like, handling all of this stuff that they've been upstreaming over the years for, like, copy on write and things like that.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
And I feel like, you know, they have had lots of, you know, repos that were basically versions of that that, like, made their way into the official... right? Like realm. Um, so it's possible, right? Like 37 singles is just another company, right? Like, yep.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
That is the funniest thing, right? Because the whole Rails...
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
hype started off of a blog which is like search is like kind of something you add to a blog right as like one of your primary features honestly it's what you had almost any any site that you make with reels uh so yeah i mean it's super i'm super excited about that i hope it's i mean if it's anything like all the other reels uh you know interfaces it should be very straightforward uh are you hoping that it aligns with any particular uh
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
you know, search gem that you've used in the past?
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
yeah yeah it's really why don't we have a reader bot and it's just like reads your book for you and it's like okay yeah based on this latest stuff you know you should update these things right that would that would be very useful indeed so i we were talking before the show kind of like Rails 8 is on the way here. Everybody's at Rails World and Ayush and I are feeling major FOMO right now.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Is there full-text search in SQLite? yes there is yeah oh nice yeah i feel like that's something that you know once you realize it's there you're like why do i need other things you know i mean until you start using it heavily but if you just want to like expose a text column like to search on it's like pretty great to be honest yeah like i think again for the vast majority of use cases
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Yeah, I agree with you there. I mean, I feel like, you know, most Rails apps are like business related, like where you'll have a CRM or like some classic, you know, solution that you're just trying to solve with like your custom data or things like that. And that, you know, having a just quick full-text search or I imagine what active search will become will just be so great.
Ruby Rogues
Navigating Rails for Front-End Developers: A Comprehensive Guide to Integration and Transition - RUBY 654
Just hook it up to a model or whatever it may be, a series of models. I could see it being pretty huge.