The "# of model-generated tokens per response" chart in [the blog introducing gpt-5-codex](https://openai.com/index/introducing-upgrades-to-codex/) shows an example of how we're improving the model good at both.

Comments URL: https://news.ycombinator.com/item?id=40198120

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=40052112

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=39972270

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=39943266

Points: 5

# Comments: 0

Link expires in 6 days. Most of the discussion is in the comments.

For anyone who doesn't want to load a ton of JS, in short:

# Free

Mostly pairing features. Free because we think that collaborative pairing functionality should be available to everyone, whether or not you can pay. If you're an individual contributor, you should just be able to sign up. Our closest competitor charges $30 a month for just pairing functionality, and as a result many small teams can't afford to use it.

# Standard

Mostly features to help with async communication and documentation. We think that distributed work in it's ideal is "Pair often, write a lot, and minimize meetings."

We think it makes sense to draw the paywall here because a/ The async features cost us more to run, and b/ This problem is something that team leaders or managers care about. And those are the people with credit cards.

We support teams having a mix of Free and Standard seats. Just pay for the power users.

# Enterprise

There are some features that cannot be per-seat: They have to be the whole team or nothing. For example, SSO (yes #ssoTax), API access, bespoke security review etc. For these, we can talk to the team about what their usage will look like in deciding the price.

Hope that helps. We're very open to feedback on this. DM's open at @embirico on Twitter if you have thoughts privately.

Comments URL: https://news.ycombinator.com/item?id=36127230

Points: 220

# Comments: 117

We want to try running small teams using the best stack for each platform.

> When 7/10 team mates comply and keep it on always, the pressure is on the remaining 3 to turn on their cameras as well.

This is our site being unclear again. Remotion coworking rooms default to audio and video muted. However, we struggling with how to represent Remotion on our site: When you're out of a call or your camera is off, we show users as "selfies" because we think those feel more human that just a green dot. Website viewers often interpret these selfies as being live video.

> when you go offline, it is now amplified in terms of visibility [...] This may affect my performance reviews

Candidly, I think that the root symptom of what you're describing is your team/manager. Let me ask you this: Do you want to work on a team that wants you to be at your desk all the time?

Our philosophy at Remotion is to be radically transparent about breaks, to the point of celebrating them. Apart from a few hours of meeting overlap in the middle of the day, we work on our own terms, including taking breaks for walks/errands/etc in the middle of the day. It goes to the point of actively posting photos of our midday breaks in an OOTO channel. Teammates react to those, making a point of saying: "Hey, prioritizing yourself is good. Being offline is good."

> pro-privacy zoom alternative

Interesting, will bear in mind.

Re video on/off, the defaults in the app can influence a lot here. Our coworking rooms default to audio and video off.

> By writing code in a non-standard fashion, we took on overhead that we would have not had to worry about had we stayed with the widely used platform defaults. This overhead ended up being more expensive than just writing the code twice.

https://dropbox.tech/mobile/the-not-so-hidden-cost-of-sharin...