←back to thread

261 points rbanffy | 1 comments | | HN request time: 0.203s | source
Show context
pjmlp ◴[] No.44004601[source]
On the other news, Microsoft dumped the whole faster Python team, apparently the 2025 earnings weren't enough to keep the team around.

https://www.linkedin.com/posts/mdboom_its-been-a-tough-coupl...

Lets see whatever performance improvements still land on CPython, unless other company sponsors the work.

I guess Facebook (no need to correct me on the name) is still sponsoring part of it.

replies(6): >>44004800 #>>44004845 #>>44004858 #>>44005777 #>>44006075 #>>44006359 #
rich_sasha ◴[] No.44004845[source]
Ah that's very, very sad. I guess they have embraced and extended, there's only one thing left to do.
replies(2): >>44005137 #>>44005839 #
stusmall ◴[] No.44005839[source]
That shows a misunderstanding of what EEE was. This team was sending changes upstream which is the exact opposite of "extend" step of the strategy. The idea of "extend" was to add propriety extensions on top of an open standard/project locking customers into the MSFT implementation.
replies(1): >>44006353 #
jerrygenser ◴[] No.44006353[source]
Ok so a better example of what you describe might be vscode.
replies(1): >>44006499 #
nothrabannosir ◴[] No.44006499[source]
What existing open standard did vscode Embrace? I thought Microsoft created v0 themselves.

A classic example is ActiveX.

replies(3): >>44006590 #>>44010084 #>>44010717 #
1. JacobHenner ◴[] No.44010084[source]
VSCode displaced Atom, pre-GitHub acquisition, by building on top of Atom's rendering engine Electron.