HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
grych
drab
Elixir2017–2023
grych / drab

drab

Remote controlled frontend framework for Phoenix.

7Distinct people
9Mentions
0Explicit recommenders
879GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Remote controlled frontend framework for Phoenix.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2017-02-26 18:34:16 UTC to 2023-09-24 13:49:42 UTC.

0123452017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC523
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

9 sources
All I would say to Zach, other than appreciating his efforts on this, is to not give up, and to be in it for the long haul. The Elixir community needs a different flavour of making webapps other than Phoenix. It was a bit dishearting to see drab[1] development stop once Phoenix Liveview took over the mindshare. [1] - https://github.com/grych/drab EDIT -- Sorry - adding in that drab's author suffered a major health issue - https://github.com/grych/drab/issues/205#issuecomment-795137...
In Ash Framework
I generally agree with you, and as a front-ender-first that feels kind of uncomfortable to say. In my personal projects I do often go for a more conservative server-side first approach. That said, it really feels like a chasm that quite often I choose to cross simply because it'll be easier down the line. I've been bitten more than once by server-side-first projects where going full-on client-side with the server-side as an API would've probably been better. Whether it was because I needed a mobile app to communicate with said API, or whether the complexity ended up being more of a client-side thing, the result was often that I had to focus on the back-end as as API and go for the full complexity of a front-end app anyways. I'm enough of a fan of my preferred back-end languages (Ruby, but mostly Elixir these days) that I try to find ways
Read the rest
to keep the complexity there, but truthfully I often opt for going for the full complexity of a client-side JS/TS stack because I'm likely to end up needing it eventually anyways. I've looked into things like Drab (https://github.com/grych/drab), but ultimately there are many reasons why 'going with the flow' seems like the better solution (even if just because it's so much easier to find JS devs than Elixir ones). So far I'm not confident enough to make any sweeping statements, but from that lack of confidence I tend to opt for the 'safer' option, which seems to be the SPA route much of the time.
In Escaping the SPA rabbit hole with modern Rails
These are random thought I just wrote on twitter in the morning(UTC+7): "I kinda think that there were no front-end languages actually. It's kinda all about web platform & browsers can't do things out of the box." "Graphic interface shouldn't execute program on its own rather than rendering string on _platform_ which won't bother more." "This is partly why people delegate js rendering to server. At the end of the day all script should be just WebAssembly bytecodes sent down." "Browser should act as physical rendering object like pure monitor screen. User shouldn't have to inspect photon or write photon generators." "SPA or PWA is just that about network request reduction, and how much string wanted to send at a time & today http/2 can help that a lot." "Project like Drab https://github.com/grych/drab 's been doing quite well to move compu
Read the rest
tation back to "server" (opposite to self-service client)" "WebAssembly compromise (to complement js) to implement the platform. JS api and WebAssembly should be merged or united." "VirtualDom as if it is a right way should be built-in just like DOM get constructed from html _string_ from server. All JS works must die." "That's how WebComponent went almost a half way of fulfilling web platform. It is unfortunate js has gone far, tools are actively building on" "I'd end this now before some thought of individualism-ruining-the-platform take over. That's not gonna be something i'd like to write (now)" ----- Not a complete version though. Kind of general speaking but I've been thinking in detail a bit. Then hours later I found this thread.
In Towards a JavaScript Binary AST

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.