react_phoenix VS surface

Compare react_phoenix vs surface and see what are their differences.

surface

A server-side rendering component library for Phoenix (by msaraiva)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
react_phoenix surface
2 11
492 1,959
- 0.7%
0.0 7.9
about 1 year ago 11 days ago
Elixir Elixir
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

react_phoenix

Posts with mentions or reviews of react_phoenix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-03.

surface

Posts with mentions or reviews of surface. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-04.
  • htmlgui.nvim - Create html + css + lua apps with neovim as 'browser'. ( proof of concept )
    2 projects | /r/neovim | 4 Jun 2023
    I should have been more clear that my intent was to create/use a compiler for some kind of component syntax. There are lots of them, from Surface (Elixir), Blade (PHP/Laravel), and JSX (React, Vue, Etc)
  • Would you still choose Elixir/Phoenix/LiveView if scaling and performance weren’t an issue to solve for?
    3 projects | /r/elixir | 7 Mar 2023
  • Why I selected Elixir and Phoenix as my main stack
    36 projects | dev.to | 21 Jan 2023
    There I learned more deeply about LiveView and Surface UI.
  • Something similar to Vuetify for Phoenix LiveView?
    2 projects | /r/elixir | 3 Dec 2022
    I think Surface is the ideal candidate for this. But it doesn’t have the components you are looking for but you can build anything with it. Hopefully, in future we can have set of headless components built using Surface 🤞
  • Course/Extensive tutorials for Phoenix 1.6?
    2 projects | /r/elixir | 26 Dec 2021
    This is just an idea, but what about implementing using Phoenix.View(via use MyAppWeb, :view in your module)? Then assign I think has access to @conn. Then maybe work some magic to still allow Phoenix.Component syntax - but at this point, this is something I believe is a flow that might be in development. Try investigating / asking in Surface, because that is a lot more similar to React in its approach. In fact, I think Surface is where more aggressive features are pushed out, and ironed-out features get included into Phoenix. This was the case for Phoenix.Component, and HEEX.
  • We Got to LiveView
    19 projects | news.ycombinator.com | 22 Sep 2021
    I totally get the "Am I doing this the right way?" feeling, especially coming from Rails where everything was so opinionated and wanting to stay idiomatic.

    Phoenix, while it does have opinions, is far less opinionated in the sense that it doesn't do it darndest to force you into certain conventions (for example, if your module name doesn't match your file name, Phoenix won't complain). Its generators do try and push you toward using good DDD practices (which is my opinion is a GREAT thing), but of course the generators are completely optional.

    I don't have experience writing large LiveView apps but I would say that if you are familiar with any component-based frameworks (like React), I would take a look at SurfaceUI[1]. It simplifies a few "gotchas" in LiveView (though I would say they are very minor gotchas and worth learning about at some point) and gives you a component-rendering syntax more like React. Once you get going, you'll learn that LiveView doesn't have all the headaches that come with bigger React apps (like having to memoize functions or comparing props to avoid a re-render and whatnot). The recent release candidate for Phoenix 1.6 has made strides for a cleaner component syntax, but if you're having trouble with LiveView, Surface might bring some familiarity.

    [1] https://github.com/surface-ui/surface

  • Phoenix 1.6.0-RC.0 Released
    3 projects | news.ycombinator.com | 27 Aug 2021
    Have you seen Surface UI? Pretty cool. Collection of LiveView components. https://surface-ui.org/
  • Letter Square: Post Mortem
    3 projects | dev.to | 3 Mar 2021
    I also did not use "vanilla" LiveView, as I used the Surface library. This is a wrapper around LiveView that brings a whole new syntax to make the experience even more comfortable.

What are some alternatives?

When comparing react_phoenix and surface you can also consider the following projects:

plug - Compose web applications with functions

torch - A rapid admin generator for Elixir & Phoenix

Raxx - Interface for HTTP webservers, frameworks and clients

plug_cloudflare - Parses CloudFlare's CF-Connecting-IP header into Plug.Conn's remote_ip field.

phx_component_helpers - Extensible Phoenix liveview components, without boilerplate

phoenix_live_reload - Provides live-reload functionality for Phoenix

webassembly - Web DSL for Elixir

phoenix_live_view - Rich, real-time user experiences with server-rendered HTML

scaffold - A mix task for creating new projects based on templates fetched from a Git-repo