4 ms·
tl;dr: Ken is upset and amazed that disrupting the workflows and toolchains of entrenched Python developers is causing a backlash, and that negative things are
by lsh 8y ago
tl;dr: Ken is upset and amazed that disrupting the workflows and toolchains of entrenched Python developers is causing a backlash, and that negative things are being said about him.
The post is self-aggrandising and he has the audacity to think he knows what is best for everybody. There is also the real chance this tool will replace other tried and true tools and workflows with a more complicated one. It smacks of systemd vs upstart vs sysv
- rthomas6 8y agoBut... You don't have to use it? How does pipenv disrupt anyone's workflow? It's optional.
- StavrosK 8y ago> Ken is upset and amazed that disrupting the workflows and toolchains of entrenched Python developers is causing a backlash I'm not a huge fan, but how is he disrupting the workflows and toolchains? He wrote a tool, if you want to use it, that's cool, if not, that's cool too. It's not like he came to your house and forced you to use Pipenv instead of what you were already using. If you want something to be mad at, it's the larger issue: We just started moving to Pipfile for dependencies and now we're switching again to some new project.toml file? The tool we use over this file is pretty much irrelevant, since all that matters is this file, and you can use any one of a myriad of tools to manage it and install your dependencies with. If you don't like Pipenv, use something else that can install stuff from a Pipfile, but why are we making yet another standard to replace all previous ones (xkcd here)?