Re:Eating Our Own Dog Food: Behind the Scenes at Cloud9
by lennartcl on Wednesday July 29, 2015 @03:50PM
(#9971147)
We did a massive rewrite last year (https://c9.io/blog/announcing-the-all-new-cloud9-development...). We adopted a new plugin system and started with a completely new, clean code base. We ported the old plugins one by one, optimizing them and fitting them into the new system, and actually throwing out quite a few of them entirely. So the code is actually rather clean. But note that this figure includes code for a lot of backend systems that are part of the Cloud9 service infrastructure, such as backup workers and container management code, as well as code for partners and plugins that are not exposed to the normal user base.
Re:Eating Our Own Dog Food: Behind the Scenes at Cloud9
by williamstein on Wednesday July 29, 2015 @06:58PM
(#9972171)
Many thanks for the clarification and discussion of the structure of your code base.
Re:Eating Our Own Dog Food: Behind the Scenes at Cloud9
by williamstein on Wednesday July 29, 2015 @03:02PM
(#9970833)
Of this 330409 lines of Javascript code, the majority (223414 lines) of it is stuff in the node_modules subdirectory, which probably is what you mean by dependencies...? E.g, there is one file in there https://github.com/c9/core/blob/master/node_modules/ace/lib/... that contains 54209 lines of code.
Javascript: files: 1125, blank lines: 58790, comments: 114390, code: 330409.