Back-end languages are coming to the front-end

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com
featured
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video.
Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
getstream.io
featured
  1. htmx

    </> htmx - high power tools for HTML

    > 2) If there's a form input at each step, the server needs to store that info and be aware that the user has an incomplete checkout. Now the user is at step=2 and presses the back button, or clicks on the step=1 link. In that case, the server should know the information stored in the point no. 2 above, and return an HTML form with the data pre-filled based on the last state.

    The problem is that when you press back button in the browser, it doesn't make another request to the server. It reloads the page from browser memory. A link back can be made to work, but that's not what I was speaking to.

    I tested the most trivial case, when you return a response, and push navigate to next step, then press browser back button, form state is not retained. Both chrome and firefox do not restore the form state on navigation back after a url push navigation.

    I don't think that without some client side JS that saves/reloads prior form state this is a solvable problem because of browser behavior. Either that, or perhaps use different divs for each step then have js hide/show them which is what I will try next but involves writing js to do so.

    It's pretty clear that htmx hasn't considered back button much at all, it also clobbers the page titles in history as well (https://github.com/bigskysoftware/htmx/issues/746), but that's a fixable problem.

  2. InfluxDB

    InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

    InfluxDB logo
  3. pagoda

    Rapid, easy full-stack web development starter kit and admin panel in Go

    I was going to mention that I was surprised htmx wasn't mentioned in the article. It's backend-agnostic an extremely easy to use. Drop in Alpine.js and I think you have a really powerful setup without writing any JS. I've been using this with Go[0] and enjoying it.

    [0] https://github.com/mikestefanello/pagoda

  4. Wt

    Wt, C++ Web Toolkit

  5. django-unicorn

    The magical reactive component framework for Django ✨

    You can try Django Unicorn (https://www.django-unicorn.com) if Django is your cup of tea.

    Have used it in production and it works great. Author is also very responsive to bugfixes / feature requests.

  6. Lift

    Lift Framework (by lift)

  7. wasmer-python

    🐍🕸 WebAssembly runtime for Python

  8. Stream

    Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

    Stream logo
  9. Scala.js

    Scala.js, the Scala to JavaScript compiler

    I do not usually write front-end but when I do I use https://www.scala-js.org/

  10. mumba

    Write web-native p2p distributed apps in Swift (and others)

    > I feel like this would enable a more sensible choice:

    I'm working in something like this

    https://github.com/mumba-org/mumba

    The applications developers publish native, Swift applications, where Swift have the full access to the Webkit/Blink api the same way Javascript does and even more with the patterns from the Chromium renderer (for instance, access to lifetime events).

    The offline first comes from the fact that every application runs first as a daemon which provide a gRPC api to the world of the services it offers, where the web-UI application process might also consume this same api from its daemon -process manager or from other applications.

  11. diode

    Scala library for managing immutable application model

  12. slinky

    Write Scala.js React apps just like you would in ES6

  13. Laminar

    Simple, expressive, and safe UI library for Scala.js (by raquo)

  14. joystick

    A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.

    I do use a virtual DOM but I only use it to patch the HTML in the browser (no synthetic events or anything like that). The meat of it starts here: https://github.com/cheatcode/joystick/blob/development/ui/sr....

    My focus for v1 is on developer ergonomics and solidifying an API (this will be frozen after v1 with the only changes being additions if absolutely necessary—a component you write today will look identical to one you write in 10 years).

    All future major versions will be solely focused on performance and security (my way of saying: I haven't stress-tested renders, but for the time being it will work well for the majority of use cases).

  15. reactor

    Phoenix LiveView but for Django

    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!).

  16. luajit

    Discontinued LuaJIT is JIT compiler for the Lua language. (by LuaDist)

  17. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Understanding RESTful APIs

    2 projects | dev.to | 19 Jun 2025
  • Request for maintainer(s)

    2 projects | dev.to | 2 Jun 2025
  • How to build image search with semantic understanding

    3 projects | dev.to | 25 May 2025
  • Building a Sentiment Analysis App with React, Flask, and Hugging Face Transformers

    2 projects | dev.to | 17 May 2025
  • Building a Full-Stack AI Chatbot with FastAPI (Backend) and React (Frontend)

    3 projects | dev.to | 21 Apr 2025

Did you know that Scala is
the 32nd most popular programming language
based on number of references?