1

Going to begin an intranet web application. Confused between choosing Angular, Vue or React.

I have worked with Angular but this application will be managed by some junior developers with me overlooking it. And Angular seems overkill regarding this, it is too over engineered and then there is TypeScript. So I am thinking from the perspective of those junior developers so that they don't face a huge learning curve and become productive very fast.

Then there is the bullshit that usually goes around in every corporate intranet application where management becomes too nosy. That's why I decided that back end API should be done with Laravel which is stable not some kiddie framework of Node.js

Comments
  • 0
    Whatever you do, don't use react. It's the jquery of frontend frameworks imo.
  • 0
    It is going to be only for intranet and lightweight is something that the management doesn't understand. All other intranet applications here are behemoth. For once I am trying to build something that has a proper architecture. So anything is an improvement over those legacy apps.
  • 0
    Great! Vue.js seems to be a humble beginning for those juniors. But I'll keep an eye on Svelte...
    Might use it on something for myself.
  • 3
    Vue is just angular v1 without any of the polish or engineering weight behind it.
  • 0
    I appreciate wanting to avoid Angular's inherent complexity.

    On the other hand I'm not really sure how much Vue any given Jr. would have seen out there as far as experience goes.

    IMO they're all just tools, you have to deal with the same things eventually regardless. I'm not a big believer that any given framework avoids or creates any given result.

    If I or someone else is going to dork something up or not dork it up ... I probably will regardless of the tool.
  • 1
    The main inspiration for me is that my juniors will learn a thing or two about software architecture. Most of the devs just focus on learning these tools while not developing any quality software. Architecture a software is something that a lot of devs never even realise. Quite a large number of devs are happy with creating basic landing pages, lead generation forms and some basic jQuery.
    At least front-end JS frameworks have put some focus in this regard now.
    I myself introduced moment.js to one such person last year who was happy with his own little jQuery and been stuck at that level for past 4 years.
  • 1
    @themissingbrace
    If you want to teach them architecture and the patterns that back it, go Angular. It doesn't hide them from you behind a wall of simplifying abstraction.

    And yes, please, don't allow jQuery πŸ˜†
  • 0
    @SortOfTested Makes sense. I tried that back in 2018 and the junior dev just imported jQuery again within Angular. Bad habits die hard 😁
  • 0
    @themissingbrace
    That's why Cthulhu invented la chancla.
  • 0
  • 0
    @M1sf3t
    Architecture:
    Composition
    Layering
    Pipelines
    Workflows
    Streaming data patterns
    Etc etc

    Angular hides nothing. Everything they use is available for you to hook into, extend or override. Every system characteristic is documented, and the vast majority are pluggable.
  • 0
    @M1sf3t
    Point wasn't what had what, it was that you can see those patterns in action and documentation, and even change them out for other implementations in angular. So from an architectural teaching perspective, you can actually learn software composition, rather than a tool's approach.
  • 1
    Angular is not overkill at all. Quite the opposite. As opposed to React and Vue the Angular framework comes with much more components like routing, guards and http out of the box.

    Then the juniors can use their time making things to work instead of what things to use, and you can spend time overseeing work done instead of what things are needed.
Add Comment