3 ms·

I don’t think anyone here is giving remix enough credit for what they’re trying to do. In fact I’ve been a long time lurker and finally made an account today to

by aobdev 5y ago

I don’t think anyone here is giving remix enough credit for what they’re trying to do. In fact I’ve been a long time lurker and finally made an account today to share this opinion. My company is building a B2B ordering system. We take reservations and store fulfillment details with some email and SMS functionality bolted on to a web interface; at least for now it’s a simple business CRUD app. We chose to use Vue for the frontend and Python REST APIs on the backend. And it has been thoroughly frustrating to just ship our MVP, because when I look into our frontend codebase, more than half of it is a bunch of API calls, state management, authentication, and error handling that honestly does not provide much value to the product that we’re offering. I half wish that we had built this in Rails or Django. Except, we are geospatial-enabled and have a killer interactive map view that powers this whole thing. And it’s not just a single asset-tracking view, but this map component is going to be embedded in several places across the app. And when you zoom, pan, or search the relevant data on screen is updated. I wouldn’t dare try to build this in anything other than one of the big 3 SPA frameworks today. Why do I have to choose between a traditional app with poor ergonomics for developing frontend JS, and a clunky SPA that reinvents everything the browser has gotten good at in the last 20 years? Remix is a hybrid and I think they are on to something really great here. I can write my server side models and controllers as in days of yore and pass them straight to a renderer that happens to be full blown React + React Router that does as many fancy interactive things on the frontend as I wish once the page is hydrated. I think it’s easy for backend devs to discount how nice it is to use JSX across the stack if they’re used to a templating language and writing JS sprinkles to manipulate the DOM. And it’s easy for frontend devs to discount how much extra work it is to create an API when your team is only using it internally for a first-party app, because you need APIs for SPAs. But once you realize that you can eliminate these entire bodies of work (manipulating the DOM and writing an unnecessary API), you get the best of both worlds and everything about complicated web dev today feels so achievable. Even if it’s early days yet, and Remix can’t hold a candle to comprehensive frameworks like Rails, this is much more than just Sinatra or Flask written in JS. I’m seriously excited about where Remix is headed and I’m rooting for these guys all the way.

dmitriid 5y ago
> I don’t think anyone here is giving remix enough credit for what they’re trying to do. We would give it credit if Remix actually told us what they are trying to do. Instead we see very heavy-hanvded marketing claiming nothing short of a revolution and failing.
rk06 5y ago
> more than half of it is a bunch of API calls, state management, authentication, and error handling that honestly does not provide much value to the product that we’re offering Authentication and error handling are deal breakers, hence very valuable for any paid product. API calls and state management can be offloaded via libraries. However, they too are essential part of App. Just because they are not sexy or in business domain does not mean that they do not add any value
midrus 5y ago
> Why do I have to choose between a traditional app with poor ergonomics for developing frontend JS You don't. The same JavaScript is not 20 year's ago JavaScript, PHP is not 20 year's ago PHP, etc, etc. Not doing an SPA doesn't mean form POSTs for a like button reloading the whole page or doing jQuery spaghetti. MVC and server side templates rendering has come a long way too. Some technologies that would make your reservation system trivial to implement with this approach: - Hotwire (Rails). See https://hotwired.dev/ https://hotwired.dev/. - Livewire (Laravel). See https://tallstack.dev/ https://tallstack.dev/. - Unpoly (fw agnostic). See https://unpoly.com/ https://unpoly.com/ and there are many others. The caveat here is that you need an open minded engineering team that are happy with using programming languages as tools to build something and not js/python/elixir fanatics which can't touch anything which is not js/python/elixir/etc.

by aobdev 5y ago

dmitriid 5y ago

> I don’t think anyone here is giving remix enough credit for what they’re trying to do. We would give it credit if Remix actually told us what they are trying to do. Instead we see very heavy-hanvded marketing claiming nothing short of a revolution and failing.

rk06 5y ago

> more than half of it is a bunch of API calls, state management, authentication, and error handling that honestly does not provide much value to the product that we’re offering Authentication and error handling are deal breakers, hence very valuable for any paid product. API calls and state management can be offloaded via libraries. However, they too are essential part of App. Just because they are not sexy or in business domain does not mean that they do not add any value

midrus 5y ago

> Why do I have to choose between a traditional app with poor ergonomics for developing frontend JS You don't. The same JavaScript is not 20 year's ago JavaScript, PHP is not 20 year's ago PHP, etc, etc. Not doing an SPA doesn't mean form POSTs for a like button reloading the whole page or doing jQuery spaghetti. MVC and server side templates rendering has come a long way too. Some technologies that would make your reservation system trivial to implement with this approach: - Hotwire (Rails). See https://hotwired.dev/ https://hotwired.dev/. - Livewire (Laravel). See https://tallstack.dev/ https://tallstack.dev/. - Unpoly (fw agnostic). See https://unpoly.com/ https://unpoly.com/ and there are many others. The caveat here is that you need an open minded engineering team that are happy with using programming languages as tools to build something and not js/python/elixir fanatics which can't touch anything which is not js/python/elixir/etc.