Live data from Hacker News

Astral to Join OpenAI

astral.sh

301–310 of 951 posts

Re: Astral to Join OpenAI

#301
post #253
post #224

Earlier quoted context omitted.

The biggest scam the mega-clouds and the Githubs ever pulled was convincing open source developers that the GPL was somehow out of vogue and BSD/MIT/Apache was better. All so they could just vacuum it all up and resell it with impunity.

I don't remember GitHub or Amazon advocating MIT over GPL. Feel free to prove me wrong by pointing out this massive amount of advocacy from "mega-clouds" that changed people's minds. The ads, the mailing list posts, social media comments. Anything at all you can trace to "mega-clouds" execs.

https://choosealicense.com/

https://choosealicense.com/about/

> "GitHub wants to help developers choose an open source license for their source code."

This was built by GitHub Inc a very very long time ago.

Re: Astral to Join OpenAI

#302

Not often that I audibly groan at a HN headline :-(

I think, it may be the first time I am actually upset by acquire announcement. I am usually like "well, it is what it is", but this time it just feels like betrayal.

Re: Astral to Join OpenAI

#303
post #296

Earlier quoted context omitted.

If the product did what it was advertised to do, they could simply build their own ecosystem for producing software and train the model to use it.

Or, they could use a battle-proven existing solution because they can.

"Because they can", after spending a bunch of money to acquire an existing solution. I suppose when it's other people's money, there's no problem with burning it by the fistful. Apparently, "because they can" does not extend to building solutions with their own product.

Re: Astral to Join OpenAI

#304
post #221

Earlier quoted context omitted.

anecdotally every place ive worked at has switched over and never looked back.

been in the python game a long time and i've seen so many tools in this space come and go over the years. i still rely on good ol pip and have had no issues. that said, we utilize mypy and ruff, and have moved to pyproject etc to remotely keep up with the times.

uv solved it, it will be the only tool people use in 2 more years. if you’re a python shop / expert then you can do pip etc but uv turned incidental python + deps from a huge PITA for the rest of us, to It Just Works simplicity on the same level or better than Golang.

Re: Astral to Join OpenAI

#305

Earlier quoted context omitted.

Most popular product on the planet acquires a random python packaging org for mindshare? What am I not seeing here?

I think this is more about `ruff` than `uv`. Linting is all about parsing the code into something machines can analyze, which to me feels like something that could potentially be useful for AI in a similar way to JetBrains writing their own language parsers to make "find and replace" work sanely and what not. I'm sort of wondering if they're going to try to make a coding LLM that operates on an AST rather than text,…

Writing a parser is not that much of work to buy a company in order to do it. Piggybacking on LSP servers and treesitter would be more efficient.

Re: Astral to Join OpenAI

#307

While I -- like most other commenters -- am dubious of both OpenAI and this acquisition, I think it's pretty reasonable to wait to see how this turns out before rushing to final judgment. Everything I've seen from Astral and Charlie indicates they're brilliant, caring, and overall reasonable folks. I think it's unfair to jump to call them sell-outs and cast uv and the rest as doomed projects.

We always "wait and see" and it always turns out terrible. Even if the original founders stay on, eventually they will get pushed out when their morals conflict with company goals. Wont happen overnight, but uv will enshitify eventually.

Re: Astral to Join OpenAI

#308

Earlier quoted context omitted.

> If you don't want your lunch eaten by a private equity firm, make sure whatever tool you use is GPL licensed. 1. For the record: the GPL is entirely dependent on copyright. 2. If AI "clean-room" re-implementations are allow to bypass copyright/licenses, the GPL won't protect you.

Maybe I'm reading wrong here, but what's the implication of the clean room re-implementations? Someone else is cloning with a changed license, but if I'm still on the GPL licensed tool, how am I "not protected"?

1. Company A develops Project One as GPLv3

2. BigCo bus Company A

3a. usually here BigCo should continue to develop Project One as GPLv3, or stop working on it and the community would fork and it and continue working on it as GPLv3

3b. BigCo does a "clean-room" reimplementation of Project One and releases it under proprietary licence. Community can still fork the older version and work on it, but BigCo can continue to develop and sell their "original" version.

Post reply on HN