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

Cloud9 Acquired by Amazon

c9.io

Post reply on HN
Print view View original

211–220 of 254 posts

Re: Cloud9 Acquired by Amazon

#211

Post by Kiro »

mevile wrote: post #85
adamors wrote: post #33

I thought for a second Amazon is getting into the esports business. https://en.wikipedia.org/wiki/Cloud9_(eSports)

I don't understand e-sports teams. They're not representative of a geographical region and a "team" can actually have players on multiple games. It's like if the New York Yankees were just the Yankees and also played football, soccer and basketball. I don't understand the convention for how spectators are intended to root for a team. I get that this thing in regular sports for rooting for the team closes to you is ar…

> It's like if the New York Yankees were just the Yankees and also played football, soccer and basketball.

Not uncommon at all in my country. In fact, most major clubs have teams in many different sports.

Re: Cloud9 Acquired by Amazon

#212

Post by Nadya »

spdionis wrote: post #108
mevile wrote: post #85

Earlier quoted context omitted.

I don't understand e-sports teams. They're not representative of a geographical region and a "team" can actually have players on multiple games. It's like if the New York Yankees were just the Yankees and also played football, soccer and basketball. I don't understand the convention for how spectators are intended to root for a team. I get that this thing in regular sports for rooting for the team closes to you is ar…

Usually root for specific players/their teams and don't really pay much attention to the team name/provenience. Remember that most teams are named after their sponsor. A sponsor is not related to any city/esport. It's just a sponsor.

This holds true for traditional sports as well. A number of people will follow "their star/their player" wherever they go. Their favorite quarterback was transferred to a new team? That's their favorite team now. The loyalty isn't to the specific team - it's to a specific player or specific players.

Re: Cloud9 Acquired by Amazon

#213

Post by Karunamon »

cperciva wrote: post #186
hyperdeficit wrote: post #18

I really hope that the Cloud9 service keeps running, and maintains the free version that it currently provides. I have been using Cloud9 with the Michael Hartl Rails Tutorial to teach new programmers the basics of programming with Ruby and Rails and it has greatly reduced the friction for them to start learning. In previous classes we had the students setup a Ruby and Rails environment on their own systems and not on…

the free version EC2's t2.nano, at 0.6 cents per hour, is incredibly close to free. (And that's not even counting the 12 month 'free tier'.)

Just a hair under $5 a month, but unless you have a reason to deal with AWS complexity, you're probably better off with something like Digitalocean or Vultr for the same price and less surprises.

Re: Cloud9 Acquired by Amazon

#214

Post by bastijn »

solipsism wrote: post #146
fogleman wrote: post #116

Earlier quoted context omitted.

But you're not serving it, you're just selling the ingredients.

Good quality ingredients is the most important part, some chefs would say. You're right, but all you'd have to do is build an opinionated "skin" over Emacs, bringing together and properly configuring existing plugins, writing some new ones, and packaging it nicely. I recently started using Spacemacs[1], and I'm basically sold on Emacs as an IDE-building toolkit. And I say that as a decades-long Vim user (I still use…

> ...

> You're right, but all you'd have to do is build cloud9 yourself.

> I recently..

There, I fixed it for you. Now why would anyone want to reinvent the wheel again?

Re: Cloud9 Acquired by Amazon

#215

Post by cperciva »

Karunamon wrote: post #213
cperciva wrote: post #186

Earlier quoted context omitted.

the free version EC2's t2.nano, at 0.6 cents per hour, is incredibly close to free. (And that's not even counting the 12 month 'free tier'.)

Just a hair under $5 a month, but unless you have a reason to deal with AWS complexity, you're probably better off with something like Digitalocean or Vultr for the same price and less surprises.

Just a hair under $5 a month

IF you run it continuously. hyperdeficit was talking about using VMs for teaching, where VMs would presumably be spun up and down as needed.

Re: Cloud9 Acquired by Amazon

#216

Post by SomeCallMeTim »

krisdol wrote: post #182
SomeCallMeTim wrote: post #166

Earlier quoted context omitted.

>Developers with tech jobs often have high end machines provided to them. Developers with tech jobs should also be able to afford high end machines. It's totally worth it, if your employer will allow you to work on your personal machine at all.

Those tech companies should also provide high end machines to developers. I'm glad the last two places I've worked provided high end MacBook pros but also allow devs to use their own machines so inevitably there are a couple of Linux and Windows folks. Interesting that for me it was the startups that provided good machines while the enterprises provided 4 years old lenovo laptops with not so good batteries not the sp…

>enterprises

Yeah, well, I'll just add that to my (very long) list of reasons never to work for enterprise companies.

Re: Cloud9 Acquired by Amazon

#217

Post by scourge »

sytse wrote: post #83
jozan wrote: post #34

Earlier quoted context omitted.

Wouldn't virtual machine basically do the same thing? I've taken some classes where teacher gave us an image where everything was already installed and configured. Everything went smoothly. However, Cloud9 is much more convenient since it runs entirely on browser but VM solution could work in case C9 discontinues its free tier.

I think that the future is having not one but many workspaces. If you review a MR? Start that workspace. Help someone with a question? Login to their workspace. In GitLab we want every issue and every commit to have an IDE button https://gitlab.com/gitlab-org/gitlab-ce/issues/12759 BTW congrats to the Cloud9 team. They made a great product and selling to Amazon will ensure it lives on.

>In GitLab we want every issue and every commit to have an IDE button https://gitlab.com/gitlab-org/gitlab-ce/issues/12759 Have you considered nix environments or even containers for that?

Re: Cloud9 Acquired by Amazon

#218

Post by nocman »

benologist wrote: post #136
fragsworth wrote: post #66

Earlier quoted context omitted.

One of these days we'll have fast enough Internet speeds in the U.S. that remote VMs will work (nicely). We're definitely not there yet.

The nicest thing about Cloud9 is being open source you can install it on your own hardware so those VMs don't have to be remote.

Unless something has changed since last year, it is not truly "open source" if you're going by the Open Source Initiative's definition of "open source".

Evidently there are a number of restrictions placed on the source code that prevent this from being the case. There was a Reddit discussion about it at the time:

https://www.reddit.com/r/programming/comments/2vvs7i/cloud9_...

Re: Cloud9 Acquired by Amazon

#219

Post by ben_jones »

grncdr wrote: post #208
ben_jones wrote: post #99

Earlier quoted context omitted.

Agreed. IMO it's always during an emergency where it's a decision between fixing the server in 20 seconds, or 5 minutes via the normal deployment pipeline.

What's interesting here is that c9 + lambda would make your normal deployment pipeline much less than 20 seconds

I'm including a continuous integration step as "normal deployment pipeline". Probably code review and other steps as well. The point is emergency is always --forced.

Re: Cloud9 Acquired by Amazon

#220

Post by sytse »

scourge wrote: post #217
sytse wrote: post #83

Earlier quoted context omitted.

I think that the future is having not one but many workspaces. If you review a MR? Start that workspace. Help someone with a question? Login to their workspace. In GitLab we want every issue and every commit to have an IDE button https://gitlab.com/gitlab-org/gitlab-ce/issues/12759 BTW congrats to the Cloud9 team. They made a great product and selling to Amazon will ensure it lives on.

>In GitLab we want every issue and every commit to have an IDE button https://gitlab.com/gitlab-org/gitlab-ce/issues/12759 Have you considered nix environments or even containers for that?

Yes, we think this will be great with a container scheduler. The IDE, Review Apps, and Autoscaling CI runners are a great for a container scheduler. We're currently working on making GitLab run great on Mesosphere and RedHat OpenShift, and plan to add others after than.
Post reply on HN