Andy Maleh

So I was able to run Tetris, for example, that way I built it for the desktop and it ran on the web with the same exact code, which was pretty impressive. But in my however, practically speaking, from like a business web development point of view, I don't think it's a very practical idea. I think most developers want to know about HTML and CSS and they want to do things following more the web way.

So I was able to run Tetris, for example, that way I built it for the desktop and it ran on the web with the same exact code, which was pretty impressive. But in my however, practically speaking, from like a business web development point of view, I don't think it's a very practical idea. I think most developers want to know about HTML and CSS and they want to do things following more the web way.

And if I hide HTML, CSS from them, I don't think they'd be pleased. But also, if I were to take the other approach, which is use HTML, CSS on the desktop, that causes the other issue, which is desktop developers write a lot less code because they don't have to muck with HTML, CSS. Desktop GUI libraries are usually simpler than web stuff.

And if I hide HTML, CSS from them, I don't think they'd be pleased. But also, if I were to take the other approach, which is use HTML, CSS on the desktop, that causes the other issue, which is desktop developers write a lot less code because they don't have to muck with HTML, CSS. Desktop GUI libraries are usually simpler than web stuff.

So I think it's better to just keep the two technologies in a way separate with their DSLs. because I believe web requirements are different from desktop requirements.

So I think it's better to just keep the two technologies in a way separate with their DSLs. because I believe web requirements are different from desktop requirements.

Um, yeah, this is one of those ideas that sound good on paper, but when you start actually following them in practice, they're not very practical. Like I know people. Yeah. I mean, so yeah, I guess that's my answer.

Um, yeah, this is one of those ideas that sound good on paper, but when you start actually following them in practice, they're not very practical. Like I know people. Yeah. I mean, so yeah, I guess that's my answer.

Yeah, sure. This year, so I'll be presenting a newer version of the same workshop I conducted last year. It was a two-hour workshop called How to Build Desktop Applications in Ruby in 2023. In 2024, it's going to be How to Build Basic Desktop Applications in Ruby. This one is going to be limiting the workshop content

Yeah, sure. This year, so I'll be presenting a newer version of the same workshop I conducted last year. It was a two-hour workshop called How to Build Desktop Applications in Ruby in 2023. In 2024, it's going to be How to Build Basic Desktop Applications in Ruby. This one is going to be limiting the workshop content

to the basics of desktop development so that it gives people more time to breathe and also digest the ideas related to MVC pattern, MVP, and bidirectional and unidirectional data binding. So it will give people a lot more time to be able to play around and learn a desktop version of Glimmer. So the version used is going to be the Fukuoka Ruby Award.

to the basics of desktop development so that it gives people more time to breathe and also digest the ideas related to MVC pattern, MVP, and bidirectional and unidirectional data binding. So it will give people a lot more time to be able to play around and learn a desktop version of Glimmer. So the version used is going to be the Fukuoka Ruby Award.

The one, sorry, the one that won the Fukuoka Ruby Award. It'll be Glimmer DSL for LibUI. This library actually, the nice thing about it is that you just installed the Ruby gem and you're good to go. So I actually do include in the workshop description the instructions. Like I tell people just install the Ruby gem and then run a sample to make sure it works and you're good to go.

The one, sorry, the one that won the Fukuoka Ruby Award. It'll be Glimmer DSL for LibUI. This library actually, the nice thing about it is that you just installed the Ruby gem and you're good to go. So I actually do include in the workshop description the instructions. Like I tell people just install the Ruby gem and then run a sample to make sure it works and you're good to go.

So I'll be basically using that library as an educational library for building very small desktop app. So Glimmer DSL for LibUI, what's good about it is it's very good for very simple apps. You can build them very quickly. And also it's good for apps that are mostly tools or productivity tools.

So I'll be basically using that library as an educational library for building very small desktop app. So Glimmer DSL for LibUI, what's good about it is it's very good for very simple apps. You can build them very quickly. And also it's good for apps that are mostly tools or productivity tools.

or development-related tools that can help with your day-to-day work, because it's a very good library for packaging apps as gems.

or development-related tools that can help with your day-to-day work, because it's a very good library for packaging apps as gems.

So you can package anything, like you can scaffold an app with it, support scaffolding features similar to Rails, but for desktop apps, and then you can package your scaffolded app as a gem very quickly, and then you can give it to others, and people will just install the gem and use it. So I would recommend this library the most for people that want to build productivity tools for day-to-day work.

So you can package anything, like you can scaffold an app with it, support scaffolding features similar to Rails, but for desktop apps, and then you can package your scaffolded app as a gem very quickly, and then you can give it to others, and people will just install the gem and use it. So I would recommend this library the most for people that want to build productivity tools for day-to-day work.