Are you hiring for customer service or engineering roles by any chance?
Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
91–96 of 96 posts
Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
#92I don't see a lot of discussion about security at the moment, other than a potential for self-hosting. I created an account but I don't see MFA, which is a hard requirement for me. I'd love to look again once virtual MFA or hardware MFA is supported. I'd also be comfortable with GitHub OAuth as well, since I can manage MFA there and I think I'd integrate GitHub anyway. I'd love to see a paid bug bounty program for a…
Liusha from Nimbus here.
>I'd love to look again once virtual MFA or hardware MFA is supported.
MFA is not far. We have already started to work on MFA across our solution. I will ping you as soon as we have it ready for you.
Actually your use case is also something we are really interested in. Engineers who work on contracts or work at IT consultant companies switch between different environments way more frequently than other use cases. I wonder how you mitigate that problem today?
> The cloud env worked well, although I noticed the latency.
About latency, can I ask what your geolocation is? (country?) and which region did you select from Nimbus?
> I'd want fast VM start times
We have provided a `active hours` feature (not available for trial user). You can have your server start/stop at a given time of the day. During that time range your server will always be active. only takes about 10-15 seconds to connect.
Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
#93Earlier quoted context omitted.
Nish from Nimbus here. Personally, I dont think this is going to be a space where one company "wins the market". Whats best for developers is having flexibility and choosing the right tool for what their building and their team. So I'm hoping that these products become/stay more open and let people pick them up and drop them as needed. On the differentiation front.. there's some common differentiation points, but to…
> Whats best for developers is having flexibility and choosing the right tool for what their building and their team. One of the things that's annoyed me about codespaces and gitpods is that they really require/assume the whole team will use that one product. Codespaces does that through their billing and permissions, and gitpods does it via their PR based features etc. Is this something Nimbus is going to try and av…
I think more people on remote environments does lead to better overall experience. But the incremental benefit for each additional team member drops until everyone is working on the cloud - because then you can do some cool things or stop doing some dull things.
That said, we avoid doing anything that forces an entire team to move to our cloud environments. That's an easy way to piss people off and build a crappy product. Hopefully this approach doesnt burn us.
Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
#94What does this support outside of Javascript?
If you are talking about programming languages - it supports Golang, PHP, Java, Ruby and more. Mostly any frontend/backend languages (other than mobile development languages) You can actually treat the Nimbus workspace as your laptop on cloud. If there's anything you see not supported on Nimbus at the moment, you can create a workspace, install as many packages as you need. And once you want to share the set up with…
ok, I couldn't find any info about that on your site in my cursory glance and the only examples I saw looked like node...
Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
#95Earlier quoted context omitted.
If you are talking about programming languages - it supports Golang, PHP, Java, Ruby and more. Mostly any frontend/backend languages (other than mobile development languages) You can actually treat the Nimbus workspace as your laptop on cloud. If there's anything you see not supported on Nimbus at the moment, you can create a workspace, install as many packages as you need. And once you want to share the set up with…
ok, I couldn't find any info about that on your site in my cursory glance and the only examples I saw looked like node...
Thanks! That's a fair feedback, will take it back to the team and see how we can improve it!
Re: Launch HN: Nimbus (YC W22) – Cloud dev environments for teams
#96Earlier quoted context omitted.
Liusha from Nimbus here. Actually the larger the organizations the more necessary a cloud-based dev environment solution. That is why all the tech giants have a solution internally like Nimbus and all organizations with more than 500 engineers that I have talked to have something like Nimbus. > To me this seemed like a novel way to enforce strictness in SDLC for junior devs writing javascript-like code... The key is…
Thanks for the detailed explanation. You're right, "consistent" SDLC is what I meant. For compatibility, docker itself is kind of a sort of standard. I say sort of because of OCI. The idea is that if you run your own registry, create your own base images (and include your security team's input) and enforce a policy where you can only pull from your registry than development is forced to use your standard images, your…
I think you are right :) with a great dev infra and policy setup and proper enforcement, docker can be a great solution of environment consistency/standardization.
One use case I forgot to mention and I want to share. In some scenarios, engineers need to work on more than one project and they have completely different set up, which would be difficult for them to maintain multiple environments on their laptops. Back to our docker example, if project A requires docker desktop 4.1.0 and project B requires 4.7.0 it would difficult for the engineers to manage that. I know this is an extreme example but good enough to make the point. This scenarios happen a lot in consultant business where one engineer need to work for multiple clients at the same time.
In terms of desktop codebases, do you mean native desktop application development? I think that is a tricky one as well for similar reasons as mobile development because you need to run the apps on a specific OS for testing. But if one finds a workaround for testing, then writing code on Nimbus environments should be as good as on your local environments.
About the concern the big brother can always slip a timeclock in there: haha~ as an engineer I feel you. That is never the goal of Nimbus and I would not want my boss to stalk my every single keystroke.