Actually, I am currently working on a Large Scale Project and I have selected Node for that Project, Yet Node is very fast but it has code scattered everywhere. And it is also a different and abstract architecture that makes it a kind of crappy.
The more I learn about Node, the worse it gets. It seems that library versioning is a real pain point for everyone, and Lerna doesn't seem to make things much better. Here is an example of how developers have to manually enforce patterns on their team just to keep things from getting out of control jackcuthbert.dev/blog/managing-a-m.... This kind of thing is so straight forward in java and maven that no one even thinks about it.
On an even more basic level developers always wonder about things like, should I check in my lock file to git, or should I delete my lockfile when I build. Is there a lockfile in a sub folder that I don't know about. Yuck!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Actually, I am currently working on a Large Scale Project and I have selected Node for that Project, Yet Node is very fast but it has code scattered everywhere. And it is also a different and abstract architecture that makes it a kind of crappy.
The more I learn about Node, the worse it gets. It seems that library versioning is a real pain point for everyone, and Lerna doesn't seem to make things much better. Here is an example of how developers have to manually enforce patterns on their team just to keep things from getting out of control jackcuthbert.dev/blog/managing-a-m.... This kind of thing is so straight forward in java and maven that no one even thinks about it.
On an even more basic level developers always wonder about things like, should I check in my lock file to git, or should I delete my lockfile when I build. Is there a lockfile in a sub folder that I don't know about. Yuck!