Message from JavaScript discussions

September 2017

— No


Nobody should start to undertake a large project. You start with a small trivial project, and you should never expect it to get large. If you do, you'll just overdesign and generally think it is more important than it likely is at that stage. Or worse, you might be scared away by the sheer size of the work you envision. So start small, and think about the details. Don't think about some big picture and fancy design. If it doesn't solve some fairly immediate need, it's almost certainly over-designed. And don't expect people to jump in and help you. That's not how these things work. You need to get something half-way useful first, and then others will say "hey, that almost works for me", and they'll get involved in the project.

— Guess who?

— Sure, I'll buy that. But then the thing gets big. You have 1m users. Now, it's time to refactor because it ain't scalable. What? No engineering?

Message permanent page

— And who is it?

— Yes, then it's time

— Only then

— Linus

— Ok, so what then? Does this architecture make sense within a JS project?

— I barely started with JS a year ago and I'm aware that it is not a OO languare. That's the main thing why this might not make sense

Message permanent page

— It doesn't make sense at all to me

— JS or not