5 ms·

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,

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 the server, for no real gain other than the round trips on the api. The routes can be a problem as well. My routes have different navigation guards depending on permissions and state for the user, i haven't checked but i doubt auto generated guards based on folder structure wouldn't handle our weird business logic. COmbined with the difficulty of dealing with errors server side, nuxt.js isn't going to work in these kinds of cases. TL;DR Nuxt.js does not work for everyone, even if people say it does.

_bxg1 6y ago
What is ERP?
- pstuart 6y ago
  Enterprise Resource Planning
- ehutch79 6y ago
  Think SAP or Salesforce with a bunch of custom/addons. Sometimes account features are built in. It's very much on a different scale of complexity than a todo app. Or any app that 'does one thing well'. I think a lot of devs forget this when talking about what everyone MUST do, or making recommendations like a form should never have more than 5 fields.
ComputerGuru 6y ago
In an enterprise context, round trips (on the intranet) are cheap.
- bpicolo 6y ago
  Is writing an extra API service layer for what could otherwise use the database directly cheap on developer time?
- ehutch79 6y ago
  Agreed. Even across the internet, it's not bad. Most of the ssr for performance is around how a couple extra milliseconds will increase your bounce rate. For some of us, if our users bounce, they get fired, because the site is the tool they use to do their job. (but we should always endeavour to be performant, because we don't want to make their job more miserable) So things like bounce rate doesn't matter.
kangoo1707 6y ago
Nuxt works fine for all the uses case that I have come across, even for ERP projects. With Nuxt you can have real redirects, real 404 pages, and a well-established project structure. The only hard thing is that server-side error is more difficult to inspect

_bxg1 6y ago

What is ERP?

pstuart 6y ago
Enterprise Resource Planning
ehutch79 6y ago
Think SAP or Salesforce with a bunch of custom/addons. Sometimes account features are built in. It's very much on a different scale of complexity than a todo app. Or any app that 'does one thing well'. I think a lot of devs forget this when talking about what everyone MUST do, or making recommendations like a form should never have more than 5 fields.

ComputerGuru 6y ago

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

bpicolo 6y ago
Is writing an extra API service layer for what could otherwise use the database directly cheap on developer time?
ehutch79 6y ago
Agreed. Even across the internet, it's not bad. Most of the ssr for performance is around how a couple extra milliseconds will increase your bounce rate. For some of us, if our users bounce, they get fired, because the site is the tool they use to do their job. (but we should always endeavour to be performant, because we don't want to make their job more miserable) So things like bounce rate doesn't matter.

kangoo1707 6y ago

Nuxt works fine for all the uses case that I have come across, even for ERP projects. With Nuxt you can have real redirects, real 404 pages, and a well-established project structure. The only hard thing is that server-side error is more difficult to inspect