I’ve been using Drab for a few months (in the “React on the server” manner that José described) and I love the dynamism it gives my pages without any JS on my part. So, thank you @grych for your hard work with Drab — I really appreciate it 
metabren
5
gon782
I understand it must feel demoralizing, but please keep the project alive until this functionality actually exists and is as good or better than Drab. We already have something that works and is good and I’d hate to see it die even before LiveView has actually proven itself.
I can’t help but feel like LiveView seems to have been started because people aren’t in touch with what’s going on, so they’re just plowing through. Did people even take a good look at what Drab can do before doing this?
7
grych
Creator of Drab
After a reconsideration, I will not stop completely, but rather hold on on the new features, see my other post:
9
grych
Creator of Drab
Actually I had never so many visitors on the Demo page, see presence list. Probably Drab is now better announced than ever…
9
Zesky665
I hope you keep in mind that some of us actually rely on drab and we can’t just switch to LiveView since it isn’t out yet.
1
grych
Creator of Drab
This is exactly what I’ve said in the other thread: Drab is going to be supported, I will just hold on with new stuff until LiveView is released.
9
hilko
I can definitely imagine a situation where LiveView will be the sort-of-built-in tool for dynamic pages, and Drab continues as the powerful alternative for those who want/need more.
Furthermore, Drab could be (or is?) a bit more experimental, and over time the stuff that shakes out as stable could be integrated into LiveView.
2
grych
Creator of Drab
Drab is almost stable now, the existing version may be treated as pre-1.0.
The only thing it is missing, and I am working on, is the testing framework.
3
josevalim
Creator of Elixir
I am sorry but this irks me way too much.
Maybe people were actually familiar with Drab and decided to try different approaches? Or maybe, based on Chris talk, this is a problem that he wanted to tackle since 2013, but first he had to create and maintain Phoenix before he could take a stab at it? And even if they had no clue about Drab, how is that even a problem?
I got a lot of flak over the years (and still do) for creating a new programming language. Some called me out of touch, others called me borderline irresponsible, etc. But you know what? “because I wanted to” is a completely valid and enough answer to starting a project. There are some projects in the Elixir community that I don’t agree with but that’s totally fine (hey, they wanted to!). As long as people can discuss the trade-offs clearly, people are not being mislead, etc, I am not going to lose sleep over it.
I know this sounds counter-intuitive, as we do need a community to push those ideas forward, but that should be conciliated with everyone’s “right” to tinker and experiment.
So let people experiment, prototype and try things out. Once the ideas have consolidated, the proof of concept is ready, etc, then everybody can sit together and have a reasonable discussion about trade-offs. For all we know, LiveView could be dead in 2 months, because all of Chris’ choices turned out to be bad.
So let’s not make any rash decisions on a proof of concept that isn’t even released yet.
26
Zesky665
I’m sorry if this sounds a bit condescending. But why didn’t you guys wait until LiveView was “done”(beta stage) to announce it?
0