search

langleyfoxall / technologies

Technical overview of Langley Foxall, related technologies, frameworks, style guides and more.
https://technologies.langleyfoxall.co.uk/
Other
8 stars 8 forks source link

Standardisation of JS Framework #112

Open jaredkove opened 5 years ago

jaredkove commented 5 years ago

What you would like to change/add

I'd like to suggest and enforce that we stick to React as our frontend framework of choice for our applications.

Why you would like to change/add this

I'd like to set this in stone as we've had some on-boarding issues recently with developers that haven't worked with VueJS, and it causing those developers to slow down.

This could be slightly controversial but commercially it needs to happen in my opinion.

Checklist

AlexCatch commented 5 years ago

We all know React to a greater extent than we do Vue so from a commercial perspective it makes sense.

dextermb commented 5 years ago

As we already have projects written in Vue I think it'd be good for everyone to at least read through the documentation to at least get a general understanding of how Vue works, and the differences between React.

James34Shaw100 commented 5 years ago

I think its fair to say people can probably guess my views on this one, given my own preference having now worked in both frameworks and being able to say I personally think Vue is superior in a number of areas in terms of things such as built in animation support requiring less third party add-on libraries. I found working in React required a ton of boilerplate code to move data between components. It also seemed very hard to maintain separation of concerns between different components. Data in general never seemed where I wanted it to be.

I had been hoping to use my present project given its small scope as an example of how to build a very clean tight and easy to follow Vue SPA with state management and such, and prior to the weekend I had begun blasting through the tasks blisteringly quick once I got the state manager and router up and functional, but sadly being taken out of action by my injury meant I'd not yet had any time to start writing documentation and the project had to continue in a different direction.

I'm keen and hopeful to have a chance in future to show how really clean a Vue project can be as some of the older projects were doing quite complicated things without a State manager which they really could have benefited from, but I was unfamiliar with that section of the framework at the time so those apps are not as great as they'd be if I wrote them knowing what I know now.

AlexCatch commented 5 years ago

@JamesLF Most of the time it comes down to preference and experience, I know through experience all the issues you're facing can be solved by state management (redux, mobx) & by utilising techniques like HOCs & context providers.

I assume the above has equivalents in Vue so for me it's down to what other members of the team are in favour of.