Well I’m using it and have built up modules to automate some of my custom stuff. ^.^;

If you want, you can move it to a drab organization or just keep it in yourself, feel free to add me and I’ll try to keep it updated and working and fixed, in addition to whoever else wants to?

It has a LOT more functionality than LiveView, LiveView focuses on just the Drab.Live part of functionality but it lacks a lot more functionality at present, so Drab is currently still unreplaceable in my projects, so…

The big thing about Drab is it can integrate and control not just the DOM (which is what LiveView controls), but quite literally anything on the client side, which is significantly more powerful, and it’s all very easy to do.

Honestly Drab could still become very big if it gets a lot more add-on modules for controlling client-side frameworks.

This is really nice from you!
Let’s do it.

Hello Tomek, I’m very glad to see you around again, I hope you are recovering well !!

It is certainly a big question to imagine which could be the future for Drab. Drab is a really great library but, as you pointed out in your old post, LiveView have now stole the scene, since it is well integrated in Phoenix, have many contributors and assure a dependable future to its adopters.

To have a future, I think that Drab needs to become something non competitive to LV (like it is now, but that he cannot compete with), I mean something that adds a big value for developers that can’t be found in LV.

I remember that you had proposed the Drut project (here, and here), that could be an interesting approach, especially if it evolves as the enabler for directly and easily supporting the standard interactive frameworks like React, Vue, etc. in a Phoenix app with specific declination, as DrabReact, DrabVue, …