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

51–60 of 80 posts

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

#51

Post by bpicolo »

ComputerGuru wrote: post #43
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.

Is writing an extra API service layer for what could otherwise use the database directly cheap on developer time?

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

#52

Post by pstuart »

_bxg1 wrote: post #42
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?

Enterprise Resource Planning

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

#53

Post by holtalanm »

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.

RoR and Asp.net Core are not static site generators. They are web app frameworks that typically involve server-side rendered html.

A better example of a static site generator would be something like Jekyll (https://jekyllrb.com/)

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

#54

Post by holtalanm »

hombre_fatal wrote: post #45
taywrobel wrote: post #8

Earlier quoted context omitted.

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.

> Typescript turned out to be much better than Dart

I think we can agree to disagree. I would much rather use Dart, imo.

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

#55

Post by buremba »

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…

That's the main point of Nuxt. You look at the URL and find the page component without going through the routes file. In case that doesn't work for you, you can use `extendRoutes` for dynamic use-cases.

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

#56

Post by bryanrasmussen »

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?

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!

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

#57

Post by warent »

taywrobel wrote: post #48
warent wrote: post #29

Earlier quoted context omitted.

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.

That's _most_ modern web apps. React is a library, not a framework. jQuery is also a library. That covers probably about 95% of the web today.

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

#58

Post by pier25 »

tailsdog wrote: post #50
pier25 wrote: post #27

Earlier quoted context omitted.

> 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?

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.

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

#59

Post by Touche »

warent wrote: post #26
thdrdt wrote: post #19

Earlier quoted context omitted.

It's not only filesize it's also what the browser must parse. Parsing huge files is not a great experience on mobile.

I'm trying to imagine what browser is so outdated that it struggles to parse 100kb of javascript

It's not the browser, it's the processor that's in most non-iPhones.

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

#60

Post by Touche »

fastball wrote: post #47
ehutch79 wrote: post #28

Earlier quoted context omitted.

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.

It's unrelated to network conditions (those just make it worse). It's related to the processor in many mobile phones.
Post reply on HN