Andy Maleh

Because companies that have backend developers, they don't even need, like if there's a startup that wants to be as efficient as possible, as productive as possible, they don't even have to hire front-end developers anymore if they have solid backend Ruby developers. So that's a very big win. But on the other hand, if there are companies that have backend front-end developers,

Because companies that have backend developers, they don't even need, like if there's a startup that wants to be as efficient as possible, as productive as possible, they don't even have to hire front-end developers anymore if they have solid backend Ruby developers. So that's a very big win. But on the other hand, if there are companies that have backend front-end developers,

front-end developers would learn this just like learning any other front-end library. Because for example, React definitely had a very large, like a big learning curve in a sense, because they had JSX, which was not a normal, it's not a standard technology. JSX is actually not standard HTML, not standard CSS, not even standard JavaScript. So it's very weird.

front-end developers would learn this just like learning any other front-end library. Because for example, React definitely had a very large, like a big learning curve in a sense, because they had JSX, which was not a normal, it's not a standard technology. JSX is actually not standard HTML, not standard CSS, not even standard JavaScript. So it's very weird.

And like React has a lot of weird things that in my opinion, like waste a lot of productivity to learn. Like, Why are we working with low-level states when we actually have object-oriented programming languages that are way more advanced? They have the same idea. So in my mind, React reinvents OOP in a different way and gives it a different name.

And like React has a lot of weird things that in my opinion, like waste a lot of productivity to learn. Like, Why are we working with low-level states when we actually have object-oriented programming languages that are way more advanced? They have the same idea. So in my mind, React reinvents OOP in a different way and gives it a different name.

Basically, object attributes are called states, hooks in React. And object observers, they call them effects in React. And that's it. React is not really... It's just reinventing things. It's not really as modern and new as people think it is. For people that have been software engineering for a long time, they could tell that React's ideas have been around since the 90s at least.

Basically, object attributes are called states, hooks in React. And object observers, they call them effects in React. And that's it. React is not really... It's just reinventing things. It's not really as modern and new as people think it is. For people that have been software engineering for a long time, they could tell that React's ideas have been around since the 90s at least.

The idea of components has been around since the 90s from Visual Basic, for example. So anyways... So in the end, I found it more productive to like, and we actually have to open weird curly braces to mix logic with view concerns. So if I want to say this, do this, if that, do that, it's a bit weird opening the curly braces thing. it's very hard to integrate the logic with the view.

The idea of components has been around since the 90s from Visual Basic, for example. So anyways... So in the end, I found it more productive to like, and we actually have to open weird curly braces to mix logic with view concerns. So if I want to say this, do this, if that, do that, it's a bit weird opening the curly braces thing. it's very hard to integrate the logic with the view.

Whereas in Ruby and Glimmer DSL for web, you are in Ruby already. You're just using a Ruby DSL. You can actually write if and that immediately in the same language. Also, it's even better than ERB as well because ERB requires that developers open scriptlets to mix logic with view concerns. Sorry, not the concerns, but it's actually presentation logic. It is view logic.

Whereas in Ruby and Glimmer DSL for web, you are in Ruby already. You're just using a Ruby DSL. You can actually write if and that immediately in the same language. Also, it's even better than ERB as well because ERB requires that developers open scriptlets to mix logic with view concerns. Sorry, not the concerns, but it's actually presentation logic. It is view logic.

But to mix it with view structure, you have to open scriptlets, which can get really annoying after a while. And over a year adds up so much that it would actually... present a drag on productivity, which goes back to that boiled frog metaphor that I spoke of earlier.

But to mix it with view structure, you have to open scriptlets, which can get really annoying after a while. And over a year adds up so much that it would actually... present a drag on productivity, which goes back to that boiled frog metaphor that I spoke of earlier.

So in a way, I would say JavaScript developers that are worth their salt, that are actually smart, solid software engineers, should be able to pick up Glimmer DSL for web in no time and then be more productive in it than using JavaScript.

So in a way, I would say JavaScript developers that are worth their salt, that are actually smart, solid software engineers, should be able to pick up Glimmer DSL for web in no time and then be more productive in it than using JavaScript.

So I'm using the Opal Rails gem, which is 100% compliant with the Rails classic asset pipeline. So it runs on top of Sprockets. So it's actually very simple. It brings us back to the old simple days of CoffeeScript and older JavaScript before we had to start using crazy bundlers like Webpack. I mean, in my opinion, that's a benefit because

So I'm using the Opal Rails gem, which is 100% compliant with the Rails classic asset pipeline. So it runs on top of Sprockets. So it's actually very simple. It brings us back to the old simple days of CoffeeScript and older JavaScript before we had to start using crazy bundlers like Webpack. I mean, in my opinion, that's a benefit because

At my job, maintaining Webpack is such a monstrosity with all its options and configuration settings that upgrading it is a very difficult process. I recently upgraded it from an old version to a newer one, and it was absolute hell. It took more than a month. to finish the work. So this just, whereas this just runs on top of sprockets.

At my job, maintaining Webpack is such a monstrosity with all its options and configuration settings that upgrading it is a very difficult process. I recently upgraded it from an old version to a newer one, and it was absolute hell. It took more than a month. to finish the work. So this just, whereas this just runs on top of sprockets.