reactor VS forem

There is a library for Django that does the same thing, I haven’t tried it but it does look good and well maintained. The library is called Reactor (https://github.com/edelvalle/reactor)

I'd love to see this approach make more headway in the Django community. Based on the last DjangoCon it seems like the community is coalescing around HTMX.

This tool does play very nicely with Django's templating engine; you can just have HTMX re-render a particular template block on the server, and send down that updated block. The migration path is quite clean; you just wrap your "HTMX-updated" template block in a `hx-post` div.

Having not gone too deep on HTMX, I'm interested in folks' thoughts on where it's lacking vs. LiveView and Hotwire. One area I can see is performance; Elixir is going to be faster than Django, and so if you're trying to handle high session counts over websockets. But the impression I get is that HTMX is a bit more light-weight, so I'm wondering if there's usecases that can't be met with it vs. LiveView.

Other Django libraries that haven't quite seen as much uptake:

We have https://github.com/edelvalle/reactor, and a port of Hotwire: https://github.com/hotwire-django but both of these don't seem to have much adoption (yet!).

Thank you for posting those, I wanted to post them but I don't comment often (). Wanted to chip in another contemporary: edelvalle/reactor, which is inspired by LiveView[0].

[0]: https://github.com/edelvalle/reactor

I am using Hotwire for a project, and I'm learning Elixir and Phoenix on the side. Finding edelvalle/reactor was immediately helpful to me though, because I cut my teeth on Python/Django, so reading a Python reference implementation helps me learn nuts and bolts of libraries, faster. (so, I figure that this might help someone else grok how these approaches work.)

If this sounds like a barebones version of notable frameworks like Elixir's Phoenix LiveView, Rails's StimulusReflex or Hotwire Turbo, PHP's LiveWire, Django's Reactor... well, you're right! (Bonus: my colleague @jgaskins built a LiveView clone for Crystal)

Reactor

Reactor is a LiveView library for Django. It enables you to do something similar to Phoenix LiveView using Django Channels.

It looks a bit similar to Elixir Live View. Or similar in Django https://github.com/edelvalle/reactor, there are a couple of libraries.

Django does: https://github.com/edelvalle/reactor

This year again, I contributed to DEV with multiples ways, I've contributed very little to the repository, moderated the bad posts quite a bit, and welcomed newcomers to the platform. I feel that a place like this should always be so welcoming to users, so why shouldn't I?

docs: making updates to Editor Guide #20258

Forem - Open Source Alternative to Circle

Note: There's a PR on the Forem repo open for this. Check out if it has been implemented before trying this!

I have also contributed to other open source projects, including EddieHub, Forem, and my own.

Part of the major userbase pull in GitHub revolves around hosting a considerable number of popular projects including Angular, React, Kubernetes, cpython, Ruby, tensorflow, and well even the software that powers this site Forem.

Want the convenience of containerized setup without having to deal with learning and running Docker commands? dip gem is here to help. The folks at Evil Martians devised this CLI tool that provides a native-like interaction. Once you have Docker installed and our repository cloned:

At OpenSauced, we used forem’s Pull Request template for inspiration for our template.

Using open-source tools to test open-source projects feels like a great match. It wasn't until the other day that I remembered that the team behind DEV had open-sourced the bones of the site as Forem. To make it an even better match, the stack matches up nicely with the currently supported languages included in Bearer's new free and open-source security application security testing (SAST) tool. Unlike many security tools, this one is really focused on helping devs make sense of security concerns in an actionable way.

It's pretty clear the API is still heavily under development by the Forem team, evidenced by the "Tags" endpoint disappearing while I was writing this article (to be fair it wasn't THAT useful anyway) and that there's a fairly new pull request for removing V0 endpoints I think it's likely that access to the OpenAPI docs (and followers and articles) will stay around. I'm thinking I could pull out some more data based around the endpoints I do have, but I do need to do some thinking about. Also, given the API is under active development, and there's a fair amount of data DEV has access to in the analytics console that I don't have access to via the API, it would be nice to extend my dashboard to include this if it does get updated.