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

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

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 96 posts

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

#51

Post by liushh »

shafyy wrote: post #44
liushh wrote: post #16

Earlier quoted context omitted.

> How does that work from the IDE's perspective? We have been adding different IDE integrations into our solution so that a user would not even feel they are coding on a remote environment. We support a very smooth VSCode experience now and JetBrains IDE is on the way. > What does being "machine-first" mean for the end-user experience? It means you have the full control and flexibility to define how your environment…

> It means you have the full control and flexibility to define how your environment looks like instead of being forced to have one repo per environment. This flexibility enables the exact same experience as the one you have in your laptop from development and env management perspective. One thing I love about Gitpod is that everyone gets the same exact environment when they start Gitpod from a repo/PR. It seems like…

haha I want to be clear. I meant you can define your environment however you like in terms of flexibility. You can have 27 different repos with 2 k8s clusters with other integrations you like in an environment.

Nimbus can achieve exactly the same. You can define an environment template and all workspaces your team create from that template will have exactly the same environment.

In short, a team can enforce consistent environment with Nimbus easily.

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

#53

Post by zoomzoom »

TylerJewell wrote: post #45
zoomzoom wrote: post #27

Earlier quoted context omitted.

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

Ha! I maintain a public database and people can navigate it by going to tylerjewell.substack.com. It links into a public google sheet. The tracking methodology buckets companies by the primary product they advertise. Withcoherence is in a different category that has a broader platform definition. There are companies like gitlab and Codegiant that also have remote dev envs as features of the broader product line.

Thanks! And appreciate the context here...

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

#54

Post by radiojasper »

Your documentation in Notion is annoying me because at the bottom of each page you have no footer, no navigation, nothing. So after each page I've read, I have to use the top left breadcrumb, remember which page I've just read and find the next page in the list to continue reading through your documentation.

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

#55

Post by nithayakumar »

radiojasper wrote: post #54

Your documentation in Notion is annoying me because at the bottom of each page you have no footer, no navigation, nothing. So after each page I've read, I have to use the top left breadcrumb, remember which page I've just read and find the next page in the list to continue reading through your documentation.

Noted and very fair comment - thats definitely an area that we want to upgrade.

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

#56

Post by blibble »

nithayakumar wrote: post #30
sandGorgon wrote: post #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 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, th…

every virtualisation product for 20 years has supported saving the machine state to a file and then restoring it at some point later (maybe years)

I do this a lot on my home machine, with an nvme ssd it's under a second to save or restore the entire machine state

it's a shame the big cloud providers (Azure, GCP, AWS) virtualisation offerings are so... crappy compared to VMware workstation/ESXi/Xen/KVM/... from 20 years ago

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

#59

Post by sandGorgon »

nithayakumar wrote: post #30
sandGorgon wrote: post #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 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, th…

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

with all due respect, ur equivalent plans are far more expensive. because the equivalent on Nimbus is 30 hours per week. But on replit - u can actually host a website. The repl is "always on".

I think we probably have to agree to disagree on wasting energy here. The magic of cloud environments is always on environments where my scratch api is also running for my other developer to ping. Replit is pretty good for this. So is Sagemaker. But I do respect that ur target market is a bit different.

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

#60

Post by sandGorgon »

neilxchen wrote: post #37
sandGorgon wrote: post #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 cod…

Neil from Nimbus here. You can view Nimbus workspace as a linux machine that you have, but on the cloud. We built an internal Dockerfile-like IDL to replicate the exact dev environment every time when a new workspace is being created. - We love Dockerfile, but we didn't directly build on top of it because there are more configurations we want to enable (such as on create/start/stop/delete lifecycle hooks, and persona…

>making Nimbus a seamless part of engineers dev workflow (among all your task tracking, SCM, CI/CD tools)

tricky. unless u can allow my prod environment to be imported into nimbus (or the other way around - export). Otherwise my prod packages and your packages will always be out of sync. And that is too bothersome. The problem is not code merging and branching. But if its a "dev environment", it has to be in sync with my production environment.

Everyone here has been burnt by different version of operating system libraries, so stuff doesnt work properly. Python is notoriously funky about this because most of its libraries are written in C actually.

Post reply on HN