5 ms·

Honestly, I just want a hard fork of CPython with a few different design decisions and cleaning up of stdlib to support them: * Attributes are no longer dynami

Honestly, I just want a hard fork of CPython with a few different design decisions and cleaning up of stdlib to support them: * Attributes are no longer dynamic, __slots__-like behavior for everything by default * GIL no more * Base off of Pypy for JIT speed * Real lambdas (I like how Lobster does this) * Maybe make type annotations required (but with inference) Python's syntax is so close to nearly perfect (if you don't mind tab-delimited code, I've gotten used to it) I think it would go over better than people fear. If you do what you can to make the core language fast enough, C extension stop being as relevant. Right now, the Python ecosystem is absolutely held back by the FFI hell that it's stuck in.

rich_sasha 3y ago
Right - and you'll wipe out somewhere around 60-90% of the users. The vast ecosystem will largely not be compatible and unless you're very lucky, most will not be compatible with your fork. Language withers. As I said in the other comment, the compromise on everything is what makes it tick... I don't like all of it either, but I like a language that has top class support for ML, database connectivity, web programming, file wrangling, task orchestration and web scraping all in one. And even some poor but workable parallelization.
- packetlost 3y ago
  Retaining the community isn't necessarily a goal, the syntax is the thing I'd want to keep. Bringing over as much of the community as reasonable without compromising on other things, I think, is still a fairly worthy goal.
  - rich_sasha 3y ago
    Of course goals can vary, for many, myself included, the fact that for most things you can _imagine_ there is a quality package on PyPI is a major draw of the language. I probably wouldn't use a fork that is 2x as fast and has 10% of the package coverage.
  - amon22 3y ago
    Why keep the syntax? It's one of the least impressive part of Python
    - packetlost 3y ago
      I disagree! I think it's one of the better parts of the language

rich_sasha 3y ago

Right - and you'll wipe out somewhere around 60-90% of the users. The vast ecosystem will largely not be compatible and unless you're very lucky, most will not be compatible with your fork. Language withers. As I said in the other comment, the compromise on everything is what makes it tick... I don't like all of it either, but I like a language that has top class support for ML, database connectivity, web programming, file wrangling, task orchestration and web scraping all in one. And even some poor but workable parallelization.

packetlost 3y ago
Retaining the community isn't necessarily a goal, the syntax is the thing I'd want to keep. Bringing over as much of the community as reasonable without compromising on other things, I think, is still a fairly worthy goal.
- rich_sasha 3y ago
  Of course goals can vary, for many, myself included, the fact that for most things you can _imagine_ there is a quality package on PyPI is a major draw of the language. I probably wouldn't use a fork that is 2x as fast and has 10% of the package coverage.
- amon22 3y ago
  Why keep the syntax? It's one of the least impressive part of Python
  - packetlost 3y ago
    I disagree! I think it's one of the better parts of the language