6 ms·

So the point is to improve SEO of Vue apps Perhaps useful to some sites. Assuming Google has issues with Vue. Not useful for someone doing content behind a sig

So the point is to improve SEO of Vue apps Perhaps useful to some sites. Assuming Google has issues with Vue. Not useful for someone doing content behind a sign-in that isn’t going to ever be SEOed anyway?

nullpilot 7y ago
I've found the dev experience with nuxt to be more enjoyable overall than it is with vue-cli. The main reason for that I would say is that you don't have to bother with routes and the generator can set up Tailwind (or other CSS frameworks/tools) Generally, it feels like it strikes a good balance between being fully configurable boilerplate and opinionated framework.
- brianwawok 7y ago
  Ah. I have Vue with DRF, so I can already skip routes if I don’t need them. I don’t send JS, my CDN does, so not a big win there.
pier25 7y ago
> So the point is to improve SEO of Vue apps There are other points in favor of doing SSR + hydration besides SEO: 1) Reducing the amount of JS you are sending to the client. 2) Not making a SPA and keep the native functionality of back/forward behavior (scroll behavior, cached pages, forms are filled when going back). 3) Simplifying development. You don't need to manage central state anymore as you're dealing with one page at a time. You might not need an API as you're rendering the page from the server. Etc. I've been making SPAs for years and for my current project I'm doing SSR + hydration (not using Vue) and loving it.
- tailsdog 7y ago
  Out of interest, what are you using instead of Vue?
  - pier25 7y ago
    Svelte. It reduces the JavaScript sent to each page even further because it doesn't have a runtime per se. Basically each component is "compiled" to a set of imperative DOM instructions with some helper functions.
    - whoisjuan 7y ago
      I wanted to like Svelte so bad, but the lack of tooling made it pretty hard to debug. Hopefully they will get there one day but so far it gives me the feeling that I could hit a dead-end with it at any time.
      - pier25 7y ago
        It's not perfect but I'm willing to accept all its shortcomings because of everything I get in return. Sometimes I hit a little bump on the road which would be faster/easier to solve in React/Vue/etc but even including those slowdowns I save so much net dev time it's crazy.
psychometry 7y ago
That's just one point. Nuxt is the best way to built a multi-page web app with Vue components. Once you're using vue-router and Vuex, you might as well use Nuxt.
- brianwawok 7y ago
  Make sense. Currently using neither, but both are on my list to eval.
bryanrasmussen 7y ago
Well, about the not useful, I was working on a large service for lawyers and accountants behind a paywall, but then the new CEO decided we wanted to open up portions of stuff to google. So just because something isn't going to ever be SEOed anyway, doesn't mean that at some point in time, guess what, we need to SEO optimize some of this stuff!
- brianwawok 7y ago
  This is literally a b2b platform. It wouldn't work to remove a paywall. But cool story.

nullpilot 7y ago

I've found the dev experience with nuxt to be more enjoyable overall than it is with vue-cli. The main reason for that I would say is that you don't have to bother with routes and the generator can set up Tailwind (or other CSS frameworks/tools) Generally, it feels like it strikes a good balance between being fully configurable boilerplate and opinionated framework.

brianwawok 7y ago
Ah. I have Vue with DRF, so I can already skip routes if I don’t need them. I don’t send JS, my CDN does, so not a big win there.

pier25 7y ago

> So the point is to improve SEO of Vue apps There are other points in favor of doing SSR + hydration besides SEO: 1) Reducing the amount of JS you are sending to the client. 2) Not making a SPA and keep the native functionality of back/forward behavior (scroll behavior, cached pages, forms are filled when going back). 3) Simplifying development. You don't need to manage central state anymore as you're dealing with one page at a time. You might not need an API as you're rendering the page from the server. Etc. I've been making SPAs for years and for my current project I'm doing SSR + hydration (not using Vue) and loving it.

tailsdog 7y ago
Out of interest, what are you using instead of Vue?
- pier25 7y ago
  Svelte. It reduces the JavaScript sent to each page even further because it doesn't have a runtime per se. Basically each component is "compiled" to a set of imperative DOM instructions with some helper functions.
  - whoisjuan 7y ago
    I wanted to like Svelte so bad, but the lack of tooling made it pretty hard to debug. Hopefully they will get there one day but so far it gives me the feeling that I could hit a dead-end with it at any time.
    - pier25 7y ago
      It's not perfect but I'm willing to accept all its shortcomings because of everything I get in return. Sometimes I hit a little bump on the road which would be faster/easier to solve in React/Vue/etc but even including those slowdowns I save so much net dev time it's crazy.

psychometry 7y ago

That's just one point. Nuxt is the best way to built a multi-page web app with Vue components. Once you're using vue-router and Vuex, you might as well use Nuxt.

brianwawok 7y ago
Make sense. Currently using neither, but both are on my list to eval.

bryanrasmussen 7y ago

Well, about the not useful, I was working on a large service for lawyers and accountants behind a paywall, but then the new CEO decided we wanted to open up portions of stuff to google. So just because something isn't going to ever be SEOed anyway, doesn't mean that at some point in time, guess what, we need to SEO optimize some of this stuff!

brianwawok 7y ago
This is literally a b2b platform. It wouldn't work to remove a paywall. But cool story.