DEV Community

Discussion on: Things that I like better in Vue than in React

Collapse
 
jaydevm profile image
Jaydev Mahadevan

I think Vue historically has improved from things React pioneered

That was my feeling as I was learning Vue as well. Interestingly, the first versions of React and Vue came out around the same time. I think you can attribute part of it to the Vue team being able to learn from and improve on React's API, but it seems like they also have a different philosophy on how a developer API should look in general.

As a mature framework, React's patterns are more or less solidified. Lots of improvements have been released, but they are mostly under the hood.

I think React and Vue will both continue to evolve in a positive direction. As for trends and trendsetters, the cool kids have already moved on to new stuff like Svelte, Solid, HTMX, etc. :)

Collapse
 
dawosch profile image
Dawosch

HTMX looks cool first, but when you think about the problems it‘s no option in my opinion.

The idea behind HTMX reaches back to ajax or like web development with Java and jsf.

This results in Monolithe like systems.
And the biggest problem for me is, that you want to have interfaces for your systems. And with interfaces I mean rest endpoints so that you can get the raw data you want and make different UIs with different technologies.

When you work with HTMX I bet you don’t create separate endpoints for your system so no other system can work with the data your Plattform produces.

I stick to react :)

Thread Thread
 
nafaabout profile image
Nafaa Boutefer

I'm not sure I'd agree much with you in this regard. Exposing json endpoints could be a choice that might/might not be difficult depending on the way you built your backend. I use Ruby on Rails, and with that you can return a response to a request in whatever format is requested. All from the same route and from within the same place.

class Books < ApplicationController
   # Return all books
   # GET /books(.:format)
   def index
      @books = Book.all # can be filtered, paginated, and so on

      respond_to do |format|
           format.html # This expects to find a view under app/views/books/index.html.erb, erb a template engine that renders ruby inside html
           format.json # This expects to find a view under /app/views/books/index.json.jbuilder, jbuilder is just a json template engine than can render some ruby code to return json data
           format.xml
           .... and so on and so on
    end
Enter fullscreen mode Exit fullscreen mode

With this you can easily expose endpoints for different data formats.