3 ms·

Our company migrated to vue.js, 4 months ago. Our complex app is messy with JSX, router, and new dev can't keep up with code. Now we start every new app with Vu

Our company migrated to vue.js, 4 months ago. Our complex app is messy with JSX, router, and new dev can't keep up with code. Now we start every new app with Vue.js. The gap between junior dev and senior dev comes closer. They can collaborate with less bugs, less problems and less time to develop.

nip 9y ago
Is it because of the technology or because of the team? Rhetorical question - I am by no means attacking you or your team, I just clicked on your "is messy with JSX, router" sentence and decided to put my reply under yours. I see many people tackling React but not developing in a 'React' way. For example I recently saw on HN some user complaining that he had to create N functions to handle N items on a form, while computed properties would have done the trick with only one. I have no experience with Vue but extensive with React, having developed both small and bigger apps and the only real issue for bigger apps was that it was hard for new users to grok the project initially because of the component-based approach of React. I do agree that the learning curve for React is pretty steep, but you reap the benefits later on as React 'scales' extremely well in my opinion.
- k__ 9y ago
  I think the flux-wars made many codebases messy.
- haukur 9y ago
  In case anyone reads this and is left wondering, there's no need to have n functions to handle n inputs - you only need one. A simple example would be to set the state based on `event.target.name`.
- sheeshkebab 9y ago
  router and redux make it messy (or rather lack of standard of routing and global state management in react makes every one create their own half assed implementations)... also transitioning web developers from writing giant HTML pages to thinking about smaller components is a difficult, without dedicated react designer. All these make non trivial react apps a graveyard of crappy jsx and messy untyped tangles of JavaScript code.
  - nightski 9y ago
    I'd be really surprised if the team you had producing this huge mess was all of a sudden producing super clean code in Vue. It sounds like a very inexperienced team. Probably would be worth investing in a senior developer or team lead to help guide these fresh devs.
  - aeriklawson 9y ago
    > also transitioning web developers from writing giant HTML pages to thinking about smaller components is a difficult, without dedicated react designer. Can you elaborate? I naturally gravitate towards separating code into components in a framework-agnostic sense - React was very intuitive to me and devs I've talked to seem to feel the same way. Writing huge atomic pieces of HTML is nothing but a huge headache; it's awful to maintain as it results in copious amounts of redundancy / tech debt.
    - sheeshkebab 9y ago
      perhaps I was being impatient observing a group of web developers and designers trying to jump into a large React project, practically with no prior experience in react (although familiar with Angularjs, html, css, js, dom) - however the fact is that after 3 months of dev, the react codebase turned into an absolute mess - albeit following best practices around branches, testing, pull request reviews, continuous delivery to staging environments etc... The main issues seemed to do with global state management favored by Redux (hello global variables, I thought we were over you years ago :) ) and tendency to jam html into react components designed as screens, rather than components.

nip 9y ago

Is it because of the technology or because of the team? Rhetorical question - I am by no means attacking you or your team, I just clicked on your "is messy with JSX, router" sentence and decided to put my reply under yours. I see many people tackling React but not developing in a 'React' way. For example I recently saw on HN some user complaining that he had to create N functions to handle N items on a form, while computed properties would have done the trick with only one. I have no experience with Vue but extensive with React, having developed both small and bigger apps and the only real issue for bigger apps was that it was hard for new users to grok the project initially because of the component-based approach of React. I do agree that the learning curve for React is pretty steep, but you reap the benefits later on as React 'scales' extremely well in my opinion.

k__ 9y ago
I think the flux-wars made many codebases messy.
haukur 9y ago
In case anyone reads this and is left wondering, there's no need to have n functions to handle n inputs - you only need one. A simple example would be to set the state based on `event.target.name`.
sheeshkebab 9y ago
router and redux make it messy (or rather lack of standard of routing and global state management in react makes every one create their own half assed implementations)... also transitioning web developers from writing giant HTML pages to thinking about smaller components is a difficult, without dedicated react designer. All these make non trivial react apps a graveyard of crappy jsx and messy untyped tangles of JavaScript code.
- nightski 9y ago
  I'd be really surprised if the team you had producing this huge mess was all of a sudden producing super clean code in Vue. It sounds like a very inexperienced team. Probably would be worth investing in a senior developer or team lead to help guide these fresh devs.
- aeriklawson 9y ago
  > also transitioning web developers from writing giant HTML pages to thinking about smaller components is a difficult, without dedicated react designer. Can you elaborate? I naturally gravitate towards separating code into components in a framework-agnostic sense - React was very intuitive to me and devs I've talked to seem to feel the same way. Writing huge atomic pieces of HTML is nothing but a huge headache; it's awful to maintain as it results in copious amounts of redundancy / tech debt.
  - sheeshkebab 9y ago
    perhaps I was being impatient observing a group of web developers and designers trying to jump into a large React project, practically with no prior experience in react (although familiar with Angularjs, html, css, js, dom) - however the fact is that after 3 months of dev, the react codebase turned into an absolute mess - albeit following best practices around branches, testing, pull request reviews, continuous delivery to staging environments etc... The main issues seemed to do with global state management favored by Redux (hello global variables, I thought we were over you years ago :) ) and tendency to jam html into react components designed as screens, rather than components.