ronreiter

You're right. Updated

fixed both. the repo does it exist, it's just private

Wow, this is definitely the future of work. Going to try this out right now

Duh :)

fixed, sorry

AI will cause senior developers to become 10 times more effective. AI will cause junior developers to become 10 times less effective. And that's when taking into account the lost productivity of the senior developers who need to review their code.

Unfortunately for the writer, he will probably get fired because of AI. But not because AI will replace him - because seniors will.

I work with the Lightricks team.

This is not an official page created by Lightricks, and we do not know who the owner of this page is or why he created it.

Here’s a breakdown of the *key structural changes*, and an analysis of *potential risks or concerns*:

---

## *What Has Changed*

### 1. *OpenAI’s For-Profit Arm is Becoming a Public Benefit Corporation (PBC)*

* *Before:* OpenAI LP (limited partnership with a “capped-profit” model). * *After:* OpenAI LP becomes a *Public Benefit Corporation* (PBC).

*Implications:*

* A PBC is still a *for-profit* entity, but legally required to balance shareholder value with a declared public mission. * OpenAI’s mission (“AGI that benefits all humanity”) becomes part of the legal charter of the new PBC.

---

### 2. *The Nonprofit Remains in Control and Gains Equity*

* The *original OpenAI nonprofit* will *continue to control* the new PBC and will now also *hold equity* in it. * The nonprofit will use this equity stake to fund “mission-aligned” initiatives in areas like health, education, etc.

*Implications:*

* This strengthens the nonprofit’s influence and potentially its resources. * But the balance between nonprofit oversight and for-profit ambition becomes more delicate as stakes rise.

---

### 3. *Elimination of the “Capped-Profit” Structure*

* The old “capped-return” model (investors could only make \~100x on investments) is being dropped. * Instead, OpenAI will now have a *“normal capital structure”* where everyone holds unrestricted equity.

*Implications:*

* This likely makes OpenAI more attractive to investors. * However, it also increases the *incentive to prioritize commercial growth*, which could conflict with mission-first priorities.

---

## *Potential Negative Implications*

### 1. *Increased Commercial Pressure*

* Moving from a capped-profit model to unrestricted equity introduces *stronger financial incentives*. * This could push the company toward *more aggressive monetization*, potentially compromising safety, openness, or alignment goals.

### 2. *Accountability Trade-offs*

* While the nonprofit “controls” the PBC, actual accountability and oversight may be limited if the nonprofit and PBC leadership overlap (as has been a concern before). * Past board turmoil in late 2023 (Altman's temporary ousting) highlighted how difficult it is to hold leadership accountable under complex structures.

### 3. *Risk of “Mission Drift”*

* Over time, with more funding and commercial scale, *stakeholder interests* (e.g., major investors or partners like Microsoft) might influence product and policy decisions. * Even with the mission enshrined in a PBC charter, *profit-driven pressures could subtly shape choices*—especially around safety disclosures, model releases, or regulatory lobbying.

---

## *What Remains the Same (According to the Letter)*

* OpenAI’s *mission* stays unchanged. * The *nonprofit retains formal control*. * There’s a stated commitment to safety, open access, and democratic use of AI.

Come on. This is a "mongo web scale" type of article.

CPU bound applications MUST use multithreading to be able to utilize multiple cores. In many cases, the framework knows how to give an API to the developer which masks the need for him to deal with setting up a worker thread pool, such as with web applications frameworks - but eventually you need one.

Learn how to be an engineer, and use the right solution for the problem.

Python came way before JavaScript became good. And today it is on the way to lose as a back-end language to TypeScript and Golang.

I just review the pull requests :)