nithayakumar

I dont have a real use case for this but I tried it out yesterday and loved it. Incredibly easy to use and great for prank calling my brother

Very excited to see what people do with this

Oh man - i've been watching you guys for awhile. We're YC too and building a superapp for sales ppl. Any killer use cases you've seen or imagined for sales (outside of prospecting vid customization?

I strongly recommend people give this a try. Its got so many quality of life features (like picture in picture).

Just Weta FX - those were the guys and gals that used Weta tooling for producing films and such. Not Weta Tools - those are the guys and gals building and maintaining the Weta tools

I was going to come here and say exactly this at the risk of being flamed. Love seeing this at the top

Very cool. We're working on something similar but we went more narrow because its really hard to unravel the business context from just the data alone. Ours is ponyrun.ai if you want to check it out. Also open to chat and share learnings if you're open to it.

Ive seen data sets like this and they've been bad. My main issues have been that dataset isn't kept updated, theres no sense of proportion (e.g. is 1% of the team java or 50%), and there's often not enough companies in the dataset.

So bad that I probably wouldn't buy this data without some proof that its good data

Awesome - lots of potential here.

Lots of folks are asking "who is this for?". I think that's because the people that should use this don't know that they should yet. And it's probably missing the hotel/car angle too.

This would let people like planners (e.g. destination wedding), events (e.g. festivals), and the like simplify and make money through the entire customer experience/journey.

Good luck!

Does this hold true if you charge $150 for lifetime license vs $50?

I think you have a pricing problem. This is what I see for you:

Subscription Monthly = $84 / year

Subscription Annual = $50 / year

Lifetime = $50 One Time

If I see myself using this for about half a year, I'm just going to get a lifetime sub.

Congrats on the launch. YC W22 founder who loves gaming and used to work in the gaming industry here. Love the concept and I'm excited to see how you guys grow

There's data providers that sell this info.

If you didn't put it on LinkedIn, the spam callers got it through different ways (sales tooling, direct from data providers, leaks, etc.) If you're putting your phone number out anywhere (even in the signature of your email), they're collecting that info and selling it

Yeah - we've (usenimbus.com - a company in this space) have heard the same about Jetbrains IDEs. You should check out our extension (or others') because there's been a lot of work put into making performance better.

M1s are a mixed bag for this way of working. Pre-M1, devs were running into local computing power issues. Post-M1, more compatibility and stability issues.

Thats definitely one way to do it. Im a founder at a remote dev infra startup (usenimbus.com) and this was the model we started with because it was just so simple. But we quickly learned theres no one size fit all solution so expanded into supporting containers, terraform, etc.

>> you need to lack alternatives

I dont believe this. Went through YC this year and many of the founders had great alternatives. You could say that none of the alternatives were as attractive... but thats how all decisions are made

No but even if true, being stupid doesn't mean they should get scammed

Extremely biased here. I'm one of the founders of Nimbus (www.usenimbus.com) and we help companies move to cloud dev environments.

Cloud dev environments are a tool like any other. How they're designed matters. A lot of home grown tooling ends up being limited for ease of build out and maintenance cost/effort.

Congrats on the launch. I've worked in environments with structured and unstructured standups. And the former is so much more impactful.

Gitpod competitor here - www.usenimbus.com

We've made a lot of the opposite decisions and often wonder if we went the right way. Still don't know if it's the right decision but at least our thinking wasn't wrong - so thats a win :)

I cofounded a company and had my first kid 4 months later - it was brutal. I took 2 weeks off completely but then had to take a bunch of days after because babies are hard work.

What I would do next time:

- Take more than 2 weeks (lol)

- Communicate expectations before and during

- Assign out your core responsibilities (start by looking at last months meetings and seeing who wouldve been best to replace you)

- Be available via Slack and E-mail when needed

- Put wife and baby first (this means slack/emails only get tended to when baby is napping and your not cooking/cleaning, etc.)

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.

I've tried so many MKs. This one is almost perfect. I don't like the big digits in the number row but can live with it. But I need more tactile switches :)

Looking forward to the release

For engineers, the most immediate wins here are cutting build/test times with more power, removing new project setup, and reducing environment error rate and troubleshooting.

It also gives more visibility into environments which help SRE like teams resolve issues faster.

What excites me (and many of our users) are the "micro-wins" that save time/let engineers do more. Some of these come from making workflows simpler (e.g. saving time switching context [branches/data/credentials]), improving device performance (e.g. being able to work longer unplugged), and device flexibility.

Nish from Nimbus here.

The cost of a laptop is a factor but its a drop in the bucket relative to the cost of an engineer. A $4k machine over 2 years on an engineer that has a fully loaded cost of over $200k/yr is only 1% of the total cost - not huge.

The real win is in helping engineers do more while saving time. This has huge impacts on the dev experience, productivity and general happiness in a role where many experience burnout.

But to answer more plainly, in some cases it will replace laptops (e.g. some companies ship laptops to their contractors to keep their code and data secure. They wont have to anymore). In other cases, teams save money on laptops (through lower spec'd machines with a longer lifespan).

1. The usage based fee goes up or down based on the hours used. So if you use 60 hours / week, expect it to be double the estimates. In a few months, we'll be launching our "self-hosted" option that lets you avoid usage fees from us by running it on your own AWS.

2. Basically, you'll be able to keep the files synced between your local environment and your Nimbus workstations

We're working on self-hosted right now. When that comes out, you'll be able to do exactly what you want without any usage fees from us (you'll take on the AWS usage, storage, load balancer, and other fees though).

Yeah - the targets are different. Thats probably why comparing the pricing seems odd too. Even our lowest tier has more dedicated memory (so its more expensive for us too). But don't get me wrong - I think Replit is really cool but just not what we're going for :)

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

Facebook definitely does it. Thats where we first learned about this way of working. Some bigger tech companies have actually written about it (see links below) but a list of ones that we've seen with this kind of infra include LinkedIn, Shopify, Dropbox, Stripe, Slack, DataDog, and Palantir - to name a few.

Eng blog links:

LinkedIn: https://engineering.linkedin.com/blog/2021/building-in-the-c...

Shopify: https://shopify.engineering/modelling-developer-infrastructu...

Slack: https://slack.engineering/development-environments-at-slack/

Doximity: https://technology.doximity.com/articles/github-codespaces-i...

Nish from Nimbus here

We have some loose plans but not really high up to be honest.

From a traveling perspective, it works well... as long as you have internet..you get fast download speeds (based on AWS data center transfer speeds), can work on an env more powerful than ultrabooks, and your battery life is longer.

But you can't work from a jungle or a plane without wifi :)

Nish from Nimbus here.

This is on the money. The challenge though is still giving engineers flexibility/freedom. Our approach is to have templates that engineers can use but they can fork it and play around with it, make a snapshot of that fork and share it, etc. Its a fine balance though and every team has to figure out what works best for them