4 ms·

I programmed in python for years, am starting to code in javascript/node and am really liking it. Typing in python is weird, i much prefer flow/typescript. Asyn

I programmed in python for years, am starting to code in javascript/node and am really liking it. Typing in python is weird, i much prefer flow/typescript. Async in python has a history of being weird, from twisted, to yield from, and finally to async/await (which still has some issues, but is much better). I thought javascripts "callback hell" actually made sense, promises made it easier, and now async/await which works great. Pip has a long way to go to catch up to npm/yarn (i cant believe im saying that). Virtualenvs are weird, even though node_modules can be bloated i think its a lot more intuitive. Anyway, long winded answer that i think i prefer node after a lifetime of python

BurningFrog 8y ago
pipenv replaces pip and virtualenv, and is actually decent.
- xkcd-sucks 8y ago
  Pipenv looks good on paper, but it is a total trap. Pipenv breaks differently on every single release. The user experience is absolutely hideous. I am currently in my third hour of getting a pipenv+pyenv python project running. I started the project this past summer, and have reinstalled it three times. Each time I have spent 3-6 hours getting pipenv working, and each time the errors/problems/workarounds are completely different!!!!!!
  - BurningFrog 8y ago
    All I know is it works well on our projects. I'm not the one doing any dirty work though...
Rotareti 8y ago
> Typing in python is weird, i much prefer flow/typescript. I find the exprience working with TypeScript and Python/Mypy very similiar. (in VSCode) > Async in python has a history of being weird, from twisted, to yield from, and finally to async/await (which still has some issues, but is much better). I thought javascripts "callback hell" actually made sense, promises made it easier, and now async/await which works great. Both ended up with async/await. I find async programming is similar annoying in both Python/JS. > Pip has a long way to go to catch up to npm/yarn I don't see a big difference working with pipenv/poetry compared to npm. Once your project structure is configured it boils down to `pipenv install`/`poetry add`/`npm install`. > Virtualenvs are weird, even though node_modules can be bloated i think its a lot more intuitive. Again, once configured I don't see a big difference (from a user's perspective). One system puts your packages into `npm-packages` the other puts them into `some-venv-dir`. I think npm works better out of the box, but you can configure your python dev enviornment very similar, if you want, without much effort. To me working in either TS/Python+Mypy feels pretty much the same.

BurningFrog 8y ago

pipenv replaces pip and virtualenv, and is actually decent.

xkcd-sucks 8y ago
Pipenv looks good on paper, but it is a total trap. Pipenv breaks differently on every single release. The user experience is absolutely hideous. I am currently in my third hour of getting a pipenv+pyenv python project running. I started the project this past summer, and have reinstalled it three times. Each time I have spent 3-6 hours getting pipenv working, and each time the errors/problems/workarounds are completely different!!!!!!
- BurningFrog 8y ago
  All I know is it works well on our projects. I'm not the one doing any dirty work though...

Rotareti 8y ago

> Typing in python is weird, i much prefer flow/typescript. I find the exprience working with TypeScript and Python/Mypy very similiar. (in VSCode) > Async in python has a history of being weird, from twisted, to yield from, and finally to async/await (which still has some issues, but is much better). I thought javascripts "callback hell" actually made sense, promises made it easier, and now async/await which works great. Both ended up with async/await. I find async programming is similar annoying in both Python/JS. > Pip has a long way to go to catch up to npm/yarn I don't see a big difference working with pipenv/poetry compared to npm. Once your project structure is configured it boils down to `pipenv install`/`poetry add`/`npm install`. > Virtualenvs are weird, even though node_modules can be bloated i think its a lot more intuitive. Again, once configured I don't see a big difference (from a user's perspective). One system puts your packages into `npm-packages` the other puts them into `some-venv-dir`. I think npm works better out of the box, but you can configure your python dev enviornment very similar, if you want, without much effort. To me working in either TS/Python+Mypy feels pretty much the same.