Getting real tired of your shit, JavaScript. I sincerely love and hate the language, its so flexible at the same time that flexibility will give you nightmares, I swear to god I'll never recommend Node.js for any big projects, right now the same flexibility is killing our project.

Oh lord, have mercy.

I'm just starting a nodejs and angular 2 course hehe. Thnx for the heads up

I still swear by Node.js
Never experienced any problems with it, even at scale!

@code how big is your project? how many members in team? really curious. I simply havent found anyone who had good experience with big node.js projects.

@peek4y A team of around 5 devs, 1k weekly users but potential for so much for. ~80k lines of code

In fact, I'm the opposite... Never met someone with a bad experience of Node! What went wrong with yours?

@code that gives me a better feeling with starting the courses hehe

@code Ok, ours is a lot more than 100k LoC, around 10 devs have worked on it, the problem is every dev implements in their own way. Lack of consistency, too much freedom, its all fine until this freedom gets to a point where you basically want to shoot the project to oblivion.

No matter how many unit tests, its just seems impossible to get it right with node.

And ofcourse you can always go wrong with JS, so thats there.

@peek4y I know of teams at that scale and they seem to be doing okay. Maybe try implementing a linter tool (ESlint) to ensure people follow the same code guideline. You could also do code reviews to ensure people are keeping to style and ensuring multiple people agree on an approach.

If you want to keep the flexibility of JS, I would personally recommend Typescript, as it will make the code much more consistent. And because it compiles to js, it won't stick any sticks into your workflow

@code We use linters, do code reviews now and then, and there is always a spot that gets fucked up.

@klirix The code base is too late for that.