Valentino Stoll

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?

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?

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.

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.

That's really cool.

That's really cool.

No, I'm not familiar.

No, I'm not familiar.

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

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

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.

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.

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.

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.

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?

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?

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

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

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.

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.