Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Eating Our Own Dog Food: Behind the Scenes at Cloud9

c9.io

Post reply on HN
Print view View original

21–30 of 31 posts

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#21

Post by williamstein »

williamstein wrote: post #15
hasch wrote: post #10

400,000 lines of original source code sound really impressive! are you sure about that? Does sloccount say that or some wc -l ?

[edit] I think it sounds somewhat unimpressive, as shorter code is often better code. Anyway it is true and I'm curious why so much code is needed. Here's the output using cloc on their core github repo (so this does include, e.g., the ace editor): Javascript: files: 1125, blank lines: 58790, comments: 114390, code: 330409.

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.

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#22

Post by brianwawok »

lennartcl wrote: post #18
brianwawok wrote: post #4

Earlier quoted context omitted.

Hum 5MB background image of dogfood for an article about an IDE. Thinking maybe the tech team did not design this post ;)

In this case the tech team recently switched to Ghost for blogging and didn't realize that it doesn't automatically scale images when you upload them :)

As someone who is trying out Ghost, thanks for the heads up ;)

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#23

Post by lennartcl »

callumjones wrote: post #19

Great article, it's good to hear about IDE companies dogfooding and using that to improve their product. I don't want to call you out but in https://c9.io/blog/content/images/2015/07/recursion.png you're really only running C9 in C9 - the rest have the same URL.

The URL is very similar but notice how the subdomain differs. The outer Cloud9 runs on (ide.)cloud9-lennartcl.c9.io. It responds on that URL and on *.cloud9-lennartcl.c9.io. That's where the inner Cloud9 runs: (ide.)cloud9-lennartcl.cloud9-lennartcl.c9.io. Visit that URL and you actually go through 3 proxies: the production proxy of c9.io and those of two inner instances. And note that the user names look the same in this case in this case, but that's really just for symmetry; ide.cloud9-2-lennartcl-2.cloud9-lennartcl.c9.io would have looked too awkward :) Each instance can have its own database with user names and workspaces. And each workspace runs in its own container.

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#24

Post by roninb »

I only ever used Cloud9 to try to help a few friends get into programming (which worked wonders since we could all work on the same repos together [my way of teaching them git before any programming was stupid and got dangerously close to turning them off to programming] and I could correct them with commit messages as well as inline comments) and didn't know that you could actually get a preview after running your program[0]. I'm pretty sure this is going to be all I use for the next few weeks until classes start back up.

[0] http://i.imgur.com/vDvYAvo.png

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#25

Post by duskwuff »

moistgorilla wrote: post #13
sebpark wrote: post #6

I've been watching too much dota. I just assumed this was about Cloud9.gg , the eSports team haha

Who do you think sponsors them?

HyperX, G2A, Logitech, and a handful of other gaming-oriented hardware and software companies:

http://cloud9.gg/sponsors/

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#26

Post by lennartcl »

williamstein wrote: post #15
hasch wrote: post #10

400,000 lines of original source code sound really impressive! are you sure about that? Does sloccount say that or some wc -l ?

[edit] I think it sounds somewhat unimpressive, as shorter code is often better code. Anyway it is true and I'm curious why so much code is needed. Here's the output using cloc on their core github repo (so this does include, e.g., the ace editor): Javascript: files: 1125, blank lines: 58790, comments: 114390, code: 330409.

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

#27

Post by lennartcl »

williamstein wrote: post #21
williamstein wrote: post #15

Earlier quoted context omitted.

[edit] I think it sounds somewhat unimpressive, as shorter code is often better code. Anyway it is true and I'm curious why so much code is needed. Here's the output using cloc on their core github repo (so this does include, e.g., the ace editor): Javascript: files: 1125, blank lines: 58790, comments: 114390, code: 330409.

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.

We indeed count third-party node_modules and large packed JavaScript files as "dependencies".

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#28

Post by bigtunacan »

I've used Cloud9 mostly as a way to collaborate with interactively with novice developers. I think it is a solid tool; in many businesses however using an externally cloud hosted environment for source code isn't an option. Have you ever considered a licensing package for customer based installs, similar to how Atlassian licenses Stash as an alternative to BitBucket?

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#29

Post by moistgorilla »

mavsman wrote: post #16
moistgorilla wrote: post #13

Earlier quoted context omitted.

Who do you think sponsors them?

Cloud9 IDE was founded a few years before Cloud9.gg and the two have no affiliation (or sponsorships)

Oh wow, I could have sworn they were related. (and I learned about cloud9 -the ide- because of them)

Re: Eating Our Own Dog Food: Behind the Scenes at Cloud9

#30

Post by mark_l_watson »

I hope I am not being rude, but could someone compare Cloud9 with nitrous.io? I am a light user of pro nitrous.io (a few hours per week) and like always having Haskell, Clojure, my most recent project repos cloned, etc.

Is it worth checking out Cloud9? Perhaps not a fair question, but I am interested in hearing from people who have used both. I enjoyed Google's internal browser based IDE Cider, and think that web based development has a strong future.

Post reply on HN