4 ms·
I'm not being baited into that argument. If you're starting a greenfield project then one of the first priorities is picking the tech stack and considering all
by qbasic_forever 5y ago
I'm not being baited into that argument. If you're starting a greenfield project then one of the first priorities is picking the tech stack and considering all of the trade-offs therein. In some situations you and your operations team might value deploying a static binary with zero dependencies to manage--Python is not a good choice there. Or in other situations you might depend on scientific code and models which are difficult or impossible to port away from Python. There's no simple answer to your question.
- meowface 5y agoRespectfully, I think you were the one who was perceived as baiting people with your initial post because it seemed to be hinting in an aside that any Python project in general is difficult to deploy and then not elaborating; then kind of seen as further baiting people after multiple replies inevitably constructively asked you for clarification on what you were referring to and you seemingly dodged the question by saying they were baiting you and that you won't dignify them with an answer. It seems like it was probably just a misunderstanding due to an ambiguous way someone could interpret your post. I see what you likely actually meant, now, and that you probably weren't talking about some issue with Python but about different levels of complexity in deployment in general, but I also initially misinterpreted it like the other posters did and thought it was a jab at Python. So everyone was basically misunderstanding everyone else and mutually thought they were being baited even though they weren't, I think.
- PostThisTooFast 5y agoI resent your baiting-abating, which is really thinly-veiled baiting-hating.