Expanding into Angular some tips needed

[John_Phoenix]

What would you guys say are good additions to use along side C# .Net Core.

Back in the day with ASP. Net, knowing JavaScript, JQuery, Bootstrap made development a lot easier and quicker.

Angular has been brought up by colleague, but why would I want to move my controller development from C# code into JS?

Also, some are saying use NodeJS due to speed, but I have read .Net Core outperforms NodeJS when handing requests.

The only way to really know is build it and benchmark. Test i/o, throughput and memory, that should give you a good baseline.

NodeJS is fast, C# is fast...

Most of the time it's the programmer that sets the pace.

If you rock in C#, do that, and same for JS...

At the end of the day, a stable / reliable / debuggable app is far more valuable than a unstable wormhole that no one understands but works instantly.

Also think twice, write once...

 

[John_Phoenix]

"Angular? Do you want to work for Absa as a code jockey? But seriously Angular is messy, massive and miserable to maintain."

As can anything be if you use it like a retard.

If you don't apply yourself and have the discipline to write neat all code you touch or produce will turn out horseshit.

I've seen react blocks that would make a heap of turd look lightweight or stay within its own singular function.

There's absolutely nothing that stops one from following a standard and / or style guide to create code blocks with any framework without it turning into slap kak.

Of course that standard and style guides itself should promote neatness

Personal development vs Skills dev.

You can teach someone how to code, but they have to teach themselves how to think.

Programming and autodidactic learning go together like warm water and tea leaves.