Live data from Hacker News

Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

news.ycombinator.com

21–30 of 96 posts

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#21

The remote dev environment space is heating up. Quite a few variants and competitors now emerging in this generation of vendors. I started and sold Codenvy to Red Hat which implements Eclipse Che and Eclipse Theia as CodeReady Workspaces. There are increasingly limited differentiation between various vendors. The biggest improvement areas needed now are simpler configuration, faster boot times for complex projects (p…

I LOVED Codenvy! Kudos.

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#22

Great stuff. Looking forward to JB Gateway compatibility! Really looking forward to cloud environments being more of a "thing". All the places I've worked at have struggled with various Dev environment issues

Nimbus is now compatible with JB Gateway actually even though we don't have an official JB plugin, which we are actively working on already!

Feel free to check out our doc about how to set it up here: https://www.notion.so/Connect-to-Nimbus-workspace-8c7c5b41d9...

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#23

The remote dev environment space is heating up. Quite a few variants and competitors now emerging in this generation of vendors. I started and sold Codenvy to Red Hat which implements Eclipse Che and Eclipse Theia as CodeReady Workspaces. There are increasingly limited differentiation between various vendors. The biggest improvement areas needed now are simpler configuration, faster boot times for complex projects (p…

I wonder if there are any drop in self-hosted solutions for this? Would be great to just use a tool like this even for personal dev.

self-host is definitely on our roadmap. For the first step, at least we want to deploy the EC2s in your own cloud rather than Nimbus's cloud.

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#25
I like this idea, but on a side note:

Mainframes are back baby!

> engineers can work from any [network connected] machine because the code runs and stays in the cloud.

Now that we have pervasive and quick internet in most of the places people want to work, we can start offloading the work back to centralized machines.

It's honestly a more efficient use of resources to have shared central systems, we just had to move away from them for a few decades because the networks couldn't keep up with where people wanted to work.

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#26
how does it work ? it is git integrated i assume...and do u export a Dockerfile or something to replicate the exact runtime ?

my fundamental question is : how easy is it to go from writing code to production deployment ? This has been the big issue with cloud dev. Take an example of Python flask with Pandas. There are problems depending on whether u used an alpine dev environment or debian. Now if i just take the code and try to deploy it on redhat...it goes all screwy. lots of the c library extensions start screwing up.

Can i single click create a running docker environment with my running code EXACTLY like the code dev environment.

Funnily enough, the only good one here is AWS Sagemaker - https://docs.aws.amazon.com/sagemaker/latest/dg/docker-conta...

They do this for machine learning code. You can take your data and algorithms out of the ide and get a running docker container with all the build scripts and everything.

second - ur pricing is off. part of the charm of a cloud dev environment is never turn it off. like shutting the lid of my macbook m1 and opening tomorrow morning. even the cursor is in the same place. There is zero incentive for me to shutdown a system and reopen tomorrow morning. In that scenario, ur pricing for an 8 core 32 gb instance is 421 USD per month. Comparitively a Google Cloud 8core 32 gb instance with 100 GB SSD is 212 USD.

Sagemaker Python notebooks ml.t3.2xlarge are 0.399 USD per hour - about 288 USD per month. you will need to adjust pricing.

replit pricing of 7$ hacker plan is cheaper than equivalent Sagemaker pricing (about 36$ per month)

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#27

The remote dev environment space is heating up. Quite a few variants and competitors now emerging in this generation of vendors. I started and sold Codenvy to Red Hat which implements Eclipse Che and Eclipse Theia as CodeReady Workspaces. There are increasingly limited differentiation between various vendors. The biggest improvement areas needed now are simpler configuration, faster boot times for complex projects (p…

Tyler, don't forget about Coherence! (withcoherence.com)

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#28

how does it work ? it is git integrated i assume...and do u export a Dockerfile or something to replicate the exact runtime ? my fundamental question is : how easy is it to go from writing code to production deployment ? This has been the big issue with cloud dev. Take an example of Python flask with Pandas. There are problems depending on whether u used an alpine dev environment or debian. Now if i just take the cod…

> "my fundamental question is : how easy is it to go from writing code to production deployment ? This has been the big issue with cloud dev."

This is my question too.

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#29
One of the biggest problems with dev environments is maintenance just like documentation. As a dev, when I am working on my local environment, if something breaks, I usually end up finding some hack to fix it and move on with my feature/assigned task. Most devs leave it to the "new guy" who is onboarding. I also think having templates as code might be a way to alleviate that issue to certain extent.

Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams

#30

how does it work ? it is git integrated i assume...and do u export a Dockerfile or something to replicate the exact runtime ? my fundamental question is : how easy is it to go from writing code to production deployment ? This has been the big issue with cloud dev. Take an example of Python flask with Pandas. There are problems depending on whether u used an alpine dev environment or debian. Now if i just take the cod…

Nish here. Let me address the run time and pricing question - my cofounder wants to touch on the other question.

Teams have told us that they want to avoid 24/7 machines. It gets really expensive (and wastes energy) when people keep creating instances and leave them on. Our approach is to let people keep them on 24/7 if they want, but we want them to stop the instances too (we have automation for this).

That said, the way we’ve set up our environments is that the machine doesnt “turn off” - we just stop it. So its like closing your macbook lid and reopening it. You don’t lose your progress and youre not charged for the time in between.

And Replit’s Hacker plan is cheap but they aren’t very powerful (just 2vCPU and 2GB ram)

Post reply on HN