-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Have a list that show who is using reflex/reflex-dom #161
Comments
Yes, please! iirc, @ElvishJerricco, @mightybyte, and obviously @ryantrinkle have used it professionally, and I remember several other commenters mentioning reflex in production on r/haskell. |
The reflex community have been helping me a lot, so I can curate such a list myself, if the devs dont want to do it. |
What about doing this kinda like a list of reverse dependencies?
and in reflex-dom
|
That sounds useful :) perhaps we can use the reverse package tool that
exists somewhere already. It would also be useful to know about commercial
users
…On Jan 27, 2018 11:22 PM, "Alexandre Esteves" ***@***.***> wrote:
What about doing this kinda like a list of reverse dependencies?
So, for this repo, something like
* reflex-frp
* reflex-dom
* reflex-sdl2
* some-org
* some-opensource-repo-link
* some-proprietary-project-name: some description
and in reflex-dom
* reflex-frp
* reflex-dom-ui
* etc
* etc
* etc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#161 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABGlYH3xtLgt9OHsUAtRSy0jaVpYuXQSks5tO_XngaJpZM4RvbzL>
.
|
Oh nice find |
Some of these seem half-abandoned: no commits for over two years, builds failing, stuff like that. |
We need to get our own house in order - i.e. make a reflex release - before
we do any of this, I think.
…On Tue, Jan 30, 2018 at 10:03 AM, Alexandre Esteves < ***@***.***> wrote:
https://packdeps.haskellers.com/reverse/reflex
Some of these seem half-abandoned: no commits for over two years, builds
failing, stuff like that.
Should we have some kind of criteria for listing things or just dump
everything and then have some warnings/tags ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#161 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABGlYJXT2Nu7s0QnnR_rgVx0k4i3Q_B0ks5tPy9RgaJpZM4RvbzL>
.
|
As @ryantrinkle said, we won't be able to populate/curate a list ourselves (be it for reflex or reflex-dom) right now, but feel free to get the ball rolling on that and/or continue the discussion. I made a little template just to see how it would look but change anything you see fit. It might make sense to add one-line descriptions to each entry. |
To answer myself above: we don't have any rejection criteria as of now |
Neither Do I. I am planning to just make a table, include info like last commit, reflex version, github star (if applicable), build success (or not). |
@MarisaKirisame Sounds awesome; thanks so much! |
At the moment, most of the activity and open active projects are probably on github and it show's that there is about 180 projects, if searching. Some of the once popular projects seem to be abandoned and there is redundancy (a lot of small do-something-to-learn-projects). Sorting shows projects that have been updated lately. |
cc @andrewthad |
I currently use reflex and reflex-dom at work. |
Lets add this to reflex-frp.org |
This way, it might attract more people to try reflex
It is good for users too, since we can look at other's code to learn, given that documentation is not very good (especially for reflex-dom)
The text was updated successfully, but these errors were encountered: