Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nuxt.js over Vue.js: when should you use it and why

bornfight.com

Post reply on HN
Print view View original

41–50 of 80 posts

Re: Nuxt.js over Vue.js: when should you use it and why

#41

Post by ComputerGuru »

jmkni wrote: post #38
whoisjuan wrote: post #36

In my humble opinion, you lose a lot when you go fully static. One particular case that becomes a pain in the ass is redirections. Nuxt has some redirect modules but they feel super half baked. Also routing is a mess. Really no way to set up routing in a decent, understandable way. So in my opinion just use Nuxt when you are sure your website is not going to need any complex functionality that is easily achievable wi…

I feel as though if you just want a static website, you're better to use one of the more mature frameworks designed for that purpose, like Ruby on Rails or Asp.net Core etc. I worked on a project built with Nuxt about a about a year ago and I really didn't like it. Everything felt like a chore.

Am I missing something or did the definition of static website change? AFAIK a static site is one that has no backend and you can throw on S3 or whatever. An ASP.NET project is pretty much the absolute furthest you can get from a static website.

Re: Nuxt.js over Vue.js: when should you use it and why

#42

Post by _bxg1 »

ehutch79 wrote: post #31

There are people over on reddit who say that EVERY project should use nuxt. from the lowly todo app, to huge erp projects... Yet, especially for ERP projects, most of those features are problematic. Like SEO. I don't want a search engine to ever see my content. In fact, my robots.txt says not to index it. SSR is a non starter, since everything would vary based on the user, we're just shifting the rendering back to th…

What is ERP?

Re: Nuxt.js over Vue.js: when should you use it and why

#43

Post by ComputerGuru »

ehutch79 wrote: post #31

There are people over on reddit who say that EVERY project should use nuxt. from the lowly todo app, to huge erp projects... Yet, especially for ERP projects, most of those features are problematic. Like SEO. I don't want a search engine to ever see my content. In fact, my robots.txt says not to index it. SSR is a non starter, since everything would vary based on the user, we're just shifting the rendering back to th…

In an enterprise context, round trips (on the intranet) are cheap.

Re: Nuxt.js over Vue.js: when should you use it and why

#44

Post by thomasedwards »

avolcano wrote: post #37
thomasedwards wrote: post #35

We use Nuxt on a fairly large project. One of the biggest problems we’re having is that there’s no routes file you define yourself, you structure it by putting views in folders. This is a nightmare once you have more than a few models. It also leads to highly confusing page names, and if you have more than one variable in a route, completely screws everything up. We’ve ended up grouping things together in folders jus…

Does extendRoutes ( https://nuxtjs.org/api/configuration-router#extendroutes ) not work for y'all? I haven't had to use it (yet) but I was happy to see an escape hatch, though I could imagine it not scaling very well...

My understanding was that it just added to the existing generated list, I can’t work out how you’d tell it to ignore all your current pages and then manually write them all out?

Re: Nuxt.js over Vue.js: when should you use it and why

#45

Post by hombre_fatal »

taywrobel wrote: post #8
andarleen wrote: post #4

Earlier quoted context omitted.

probably because there are so many js “frameworks” that they are running out names

Sort of makes me bummed out that the Dart project failed. If there was one time when we could have escaped the client side hell that is JavaScript it would have been then, when chrome had astonishing market share, and Dart could compile down to JS to ease the transition until native support became standardized. But nope, here we are with anotherone.js every week.

I don't get it. Dart looks almost 1:1 exactly like Javascript. How would it have saved you from people building frameworks in it?

I think we're very lucky that Chrome never decided to include that Dart VM. Typescript turned out to be much better than Dart.

Re: Nuxt.js over Vue.js: when should you use it and why

#47

Post by fastball »

ehutch79 wrote: post #28
chimen wrote: post #5

Earlier quoted context omitted.

Depending on what you're building, I don't find 100k to be that much .

For low end android devices on a network in rural areas, that's a lot.

I would guess that for the majority of JS-heavy websites, android users in rural areas probably do not make up that much of the target market.

Re: Nuxt.js over Vue.js: when should you use it and why

#48

Post by taywrobel »

warent wrote: post #29
taywrobel wrote: post #6

Oh good, another .js. Throw it in the pile. The quagmire of subtly different JavaScript frameworks is definitely the leading reason I avoid front end work like the plague.

If you just said the first two sentences and we could have inferred that you don't work in frontend. Every technology has tradeoffs, and frankly I'd like to hear about this mystical backend panacea you're implying.

I generally work in go, where the standard library covers the vast majority of use cases. If you have some crazy specific performance needs there are frameworks for that, but generally vanilla go will get you where you need to go.

I’d love to see a “modern” web app built in pure JavaScript without a framework.

Re: Nuxt.js over Vue.js: when should you use it and why

#49

Post by canada_dry »

swyx wrote: post #9

this title and entire premise of the essay is the definition of false dichotomy. when you use nuxt.js you use vue.js. its very clear to webdevs what the metaframework does more than the framework, and you need both.

> this title and entire premise of the essay is the definition of false dichotomy

The article's very first words are: Nuxt.js is a frontend framework built upon Vue.js so I think it's more of a semantics thing on what he meant by "over" (i.e. on top of vs. replaces).

Re: Nuxt.js over Vue.js: when should you use it and why

#50

Post by tailsdog »

pier25 wrote: post #27
brianwawok wrote: post #11

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?

> 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 o…

Out of interest, what are you using instead of Vue?
Post reply on HN