Andy Maleh

And in my opinion, I succeeded at that. So yeah. I think part of it is passion. I'm very passionate about Ruby open source projects. The other part of it is also thinking seriously about how to improve our development productivity for customers, because this is a game changer.

And in my opinion, I succeeded at that. So yeah. I think part of it is passion. I'm very passionate about Ruby open source projects. The other part of it is also thinking seriously about how to improve our development productivity for customers, because this is a game changer.

If you can save six months a year of development work because you're using front end Ruby instead of JavaScript, that's an absolute game changer. And that code is also going to be more maintainable for years to come. So it'll be cheaper to maintain for years to come as well. on top of it, like basically it pays for itself. So like,

If you can save six months a year of development work because you're using front end Ruby instead of JavaScript, that's an absolute game changer. And that code is also going to be more maintainable for years to come. So it'll be cheaper to maintain for years to come as well. on top of it, like basically it pays for itself. So like,

like if people try to say, give you an excuse of, oh, I don't have time to check out this library or try it out. I'd be like, no, you don't have time not to check it out because right now you're spending six months more every year using another library. If you spend only two or three weeks learning this library, you're going to save like five weeks and a half or so.

like if people try to say, give you an excuse of, oh, I don't have time to check out this library or try it out. I'd be like, no, you don't have time not to check it out because right now you're spending six months more every year using another library. If you spend only two or three weeks learning this library, you're going to save like five weeks and a half or so.

So it's actually paying for its own investment automatically, like just by exploring this library. So in my opinion, so that's another reason why I'm into it. Like, I believe it's going to,

So it's actually paying for its own investment automatically, like just by exploring this library. So in my opinion, so that's another reason why I'm into it. Like, I believe it's going to,

Not in Glimmer DSL for web as much because it intentionally honors the HTML markup language almost exactly as is. So for example, if you want to use an on-click listener, any on-click attributes or on change or on anything, They're all supported automatically in Glimmer. So all your knowledge, you'll be able to transfer it to Glimmer.

Not in Glimmer DSL for web as much because it intentionally honors the HTML markup language almost exactly as is. So for example, if you want to use an on-click listener, any on-click attributes or on change or on anything, They're all supported automatically in Glimmer. So all your knowledge, you'll be able to transfer it to Glimmer.

But following a different way, you just have to write the code with less code. Instead of opening and closing every tag, you don't have to open and close the tags anymore. You can just put the tag name and then open a block with curly braces and then close up curly braces and you're done. So it's more dry. People who write HTML don't write dry code. because HTML itself is not dry.

But following a different way, you just have to write the code with less code. Instead of opening and closing every tag, you don't have to open and close the tags anymore. You can just put the tag name and then open a block with curly braces and then close up curly braces and you're done. So it's more dry. People who write HTML don't write dry code. because HTML itself is not dry.

I mean, that's part of the reason why XML became obsolete and people started using JSON, because JSON is a lot drier than XML. But unfortunately in web view development, like people haven't made that transition yet. So this approach is like one key reason for the design of Glimmer DSL for web being different from Glimmer DSL for Opal was to enable people to not have much of a learning curve.

I mean, that's part of the reason why XML became obsolete and people started using JSON, because JSON is a lot drier than XML. But unfortunately in web view development, like people haven't made that transition yet. So this approach is like one key reason for the design of Glimmer DSL for web being different from Glimmer DSL for Opal was to enable people to not have much of a learning curve.

They can just transfer their HTML skills uh, as is. So like any attributes, you know, on any, uh, elements are supported by Glimmer DSL for web and any listeners are supported in any, um, and, and then all the same tags are supported by their same name. It's just with a slightly different syntax. That's actually less code than HTML.

They can just transfer their HTML skills uh, as is. So like any attributes, you know, on any, uh, elements are supported by Glimmer DSL for web and any listeners are supported in any, um, and, and then all the same tags are supported by their same name. It's just with a slightly different syntax. That's actually less code than HTML.

I don't think so. I think we covered everything.

I don't think so. I think we covered everything.

I don't think I have anything, to be honest. I think the topic of this podcast will give people a lot of stuff to check out already. So I would recommend checking out the Glimmer DSL for web GitHub project. run like the online hosted sample and play around with it. It has a bunch of samples written in Ruby.

I don't think I have anything, to be honest. I think the topic of this podcast will give people a lot of stuff to check out already. So I would recommend checking out the Glimmer DSL for web GitHub project. run like the online hosted sample and play around with it. It has a bunch of samples written in Ruby.