Andy Maleh

Another idea I had in mind was to actually replace ERP files with a simpler solution called GRB. So GRB would be Glimmer RB, which is basically files that look like ERB, except instead of using templates style like scriptlet syntax, you would use the Glimmer DSL directly in them. So that's another idea I have.

Another idea I had in mind was to actually replace ERP files with a simpler solution called GRB. So GRB would be Glimmer RB, which is basically files that look like ERB, except instead of using templates style like scriptlet syntax, you would use the Glimmer DSL directly in them. So that's another idea I have.

So I have a few ideas on the horizon to enable people to more and more like improve their Rails wave rendering views and componentizing their views. And it And hopefully, eventually, once I add more and more of those ideas, I guess the fourth idea would be to do what Vault was doing, which is to have front-end models act as proxies for back-end models.

So I have a few ideas on the horizon to enable people to more and more like improve their Rails wave rendering views and componentizing their views. And it And hopefully, eventually, once I add more and more of those ideas, I guess the fourth idea would be to do what Vault was doing, which is to have front-end models act as proxies for back-end models.

If you do that, then Rails developers don't even have to write controllers anymore. You don't have to worry about... I can remove all of the boilerplate code of writing controllers out, and then I can remove all the boilerplate code of writing JavaScript services out, like REST services.

If you do that, then Rails developers don't even have to write controllers anymore. You don't have to worry about... I can remove all of the boilerplate code of writing controllers out, and then I can remove all the boilerplate code of writing JavaScript services out, like REST services.

And that way I can connect JavaScript front-end models directly to ActiveRecord or back-end models in Rails, which is kind of like what Vault and also HyperStack, which is another Opal Ruby library, does. Unfortunately, both of them are no longer maintained, or at least HyperStack hasn't had a release in three years.

And that way I can connect JavaScript front-end models directly to ActiveRecord or back-end models in Rails, which is kind of like what Vault and also HyperStack, which is another Opal Ruby library, does. Unfortunately, both of them are no longer maintained, or at least HyperStack hasn't had a release in three years.

I don't know if it is maintained still, but either way, I think that's a very important thing in software engineering, is incremental development, like iterative incremental development.

I don't know if it is maintained still, but either way, I think that's a very important thing in software engineering, is incremental development, like iterative incremental development.

And in a way, Glimmer is adopting that approach for rolling out its features where people can start with a drop-in replacement for their JavaScript front-end library, then move on to a backend technology like either GRB or rendering front-end components on the backend directly.

And in a way, Glimmer is adopting that approach for rolling out its features where people can start with a drop-in replacement for their JavaScript front-end library, then move on to a backend technology like either GRB or rendering front-end components on the backend directly.

And finally, it would be like replacing their controller layer completely with like a model proxy layer that would bypass the whole REST API thing. It would basically automate it so that I don't have to write REST code myself directly. So yeah, these are some of the ideas in the pipeline for Glimmer DSL for web.

And finally, it would be like replacing their controller layer completely with like a model proxy layer that would bypass the whole REST API thing. It would basically automate it so that I don't have to write REST code myself directly. So yeah, these are some of the ideas in the pipeline for Glimmer DSL for web.

So I explored that idea with my older Glimmer web library. It was called Glimmer DSL for Opal. It was just a library that was exploring using Opal to render user interfaces. And the approach of that library actually was very different from Glimmer DSL for web. Its approach was actually to hide HTML and CSS files.

So I explored that idea with my older Glimmer web library. It was called Glimmer DSL for Opal. It was just a library that was exploring using Opal to render user interfaces. And the approach of that library actually was very different from Glimmer DSL for web. Its approach was actually to hide HTML and CSS files.

completely from developers so that they actually work with a GUI mental model that was similar to the desktop. It even used the same widget or control names, like you could say tag names, that were used for building the Eclipse SWT library. So I was trying to match the syntax of Glimmer DSL for SWT.

completely from developers so that they actually work with a GUI mental model that was similar to the desktop. It even used the same widget or control names, like you could say tag names, that were used for building the Eclipse SWT library. So I was trying to match the syntax of Glimmer DSL for SWT.

What that enabled is basically I could take any desktop game or app that was built with Glimmer DSL for SWT and run its code in Glimmer DSL for web without writing HTML or CSS. I would just keep the same exact desktop code in Ruby and it would run the app in the browser.

What that enabled is basically I could take any desktop game or app that was built with Glimmer DSL for SWT and run its code in Glimmer DSL for web without writing HTML or CSS. I would just keep the same exact desktop code in Ruby and it would run the app in the browser.