Andy Maleh

Uh, what we're going to do is basically, uh, only internal facing web pages that are in the admin UI, uh, are going to start using Glimmer, uh, Glimmer DSL for web is like the idea I'm going to be proposing at the next meeting. Uh, And that way we can gradually play around with it in a few admin pages first.

Uh, what we're going to do is basically, uh, only internal facing web pages that are in the admin UI, uh, are going to start using Glimmer, uh, Glimmer DSL for web is like the idea I'm going to be proposing at the next meeting. Uh, And that way we can gradually play around with it in a few admin pages first.

I just want to make sure there aren't any gotchas that I haven't discovered on my own from building my own sample apps. And after we do that for about four months or six months, then we can start maybe rewriting some admin pages that were in React in Glimmer instead of just adding new pages in Glimmer.

I just want to make sure there aren't any gotchas that I haven't discovered on my own from building my own sample apps. And after we do that for about four months or six months, then we can start maybe rewriting some admin pages that were in React in Glimmer instead of just adding new pages in Glimmer.

And then after that, the phase after that, phase three would be start writing new pages on the public-facing website with Glimmer. And then finally, the last phase would be to rewrite React components with Glimmer if we feel like it is needed. It's completely optional, but it could be useful because Glimmer Ruby code is a lot more maintainable than React.js code, way more.

And then after that, the phase after that, phase three would be start writing new pages on the public-facing website with Glimmer. And then finally, the last phase would be to rewrite React components with Glimmer if we feel like it is needed. It's completely optional, but it could be useful because Glimmer Ruby code is a lot more maintainable than React.js code, way more.

Like in my experience, at least double as maintainable.

Like in my experience, at least double as maintainable.

That I've developed in Rails? What do you mean? Sorry. Like, you've used Rails before? 2008 or 2007. Yeah. Okay.

That I've developed in Rails? What do you mean? Sorry. Like, you've used Rails before? 2008 or 2007. Yeah. Okay.

There might be a slight misunderstanding. Glimmer is only the front-end part. Glimmer integrates with Rails. Glimmer is a Rails library, by the way. It's not just an open Ruby library. It's also a Rails gem. It integrates with Rails apps and enables you to suddenly, in any Rails app, be able to write the front end in Ruby. That's it.

There might be a slight misunderstanding. Glimmer is only the front-end part. Glimmer integrates with Rails. Glimmer is a Rails library, by the way. It's not just an open Ruby library. It's also a Rails gem. It integrates with Rails apps and enables you to suddenly, in any Rails app, be able to write the front end in Ruby. That's it.

Except it lets you write the front end in Ruby using a nice Glimmer DSL. Without Glimmer, if I use Opal Ruby alone, you can just write Ruby code in the front end. That's it. But you don't have any support for building frameworks or components or data binding or any of that. Glimmer adds the extra layer that is missing that enables you to do anything you can do with data binding, for example.

Except it lets you write the front end in Ruby using a nice Glimmer DSL. Without Glimmer, if I use Opal Ruby alone, you can just write Ruby code in the front end. That's it. But you don't have any support for building frameworks or components or data binding or any of that. Glimmer adds the extra layer that is missing that enables you to do anything you can do with data binding, for example.

It has the same data binding features as Glimmer desktop libraries, but all of those data binding features are actually predate Glimmer. They come from Microsoft technologies that were used in Visual Basic, I believe. and other Microsoft products. They were also used by some Mac GUI building products as well. So those same ideas got adopted by Vue.js and Svelte.

It has the same data binding features as Glimmer desktop libraries, but all of those data binding features are actually predate Glimmer. They come from Microsoft technologies that were used in Visual Basic, I believe. and other Microsoft products. They were also used by some Mac GUI building products as well. So those same ideas got adopted by Vue.js and Svelte.

So the same old sort of data binding features that people know from Svelte and Vue.js are available in Plumber. Except in Glimmer, it's a lot nicer because you write Ruby code instead of JS code. And it also doesn't have the separation between markup as in HTML and logic as in JavaScript. In Ruby, everything is Ruby. The nice thing is for HTML, you have an HTML DSL. For CSS, there's a CSS DSL.

So the same old sort of data binding features that people know from Svelte and Vue.js are available in Plumber. Except in Glimmer, it's a lot nicer because you write Ruby code instead of JS code. And it also doesn't have the separation between markup as in HTML and logic as in JavaScript. In Ruby, everything is Ruby. The nice thing is for HTML, you have an HTML DSL. For CSS, there's a CSS DSL.

And for logic, there's just Ruby DSL. So everything is in one language. So it fits in a lot. So that eliminates the friction between multiple languages, which actually creates a drag on productivity. A lot of people are kind of like the pragmatic book metaphor of the boiled frogs. Have you heard of the boiled frog story from the pragmatic programmer book?

And for logic, there's just Ruby DSL. So everything is in one language. So it fits in a lot. So that eliminates the friction between multiple languages, which actually creates a drag on productivity. A lot of people are kind of like the pragmatic book metaphor of the boiled frogs. Have you heard of the boiled frog story from the pragmatic programmer book?