3 ms·
>> why would you not choose Python? No type safety. GIL (yes, they are working on it). Slow execution. Terrible packaging and deployment: should you use pi
by thesuperbigfrog 3y ago
>> why would you not choose Python?
No type safety.
GIL (yes, they are working on it).
Slow execution.
Terrible packaging and deployment: should you use pip, pipenv, poetry, conda, setuptools, hatch, micropipenv, PDM, pip-tools, ActiveState platform, homebrew, or your Linux / BSD distro's package manager? "One way to do it"? Nope, it's TIMTOWTDI.
When writing anything new, I have been mainly choosing Rust and Go:
Rust when performance is critical, type safety is important, work is low-level, or the project is expected to be big or long-lasting.
Go for easy, cross-platform "scripting": standard library does most of what is needed. Super-fast build. Easy deployment with just a binary. Can even embed files if needed.
- tianyi-wang 3y agoThe packing is not really a problem for me. I've been doing Python long enough to know how to navigate that. I am not denying any other languages have better toolings. But you cannot beat the ecosystem. Every project you interact with, they'd have a Python SDK, but others may not be guaranteed. And I am thinking more about developing Sass products. There are performance-sensitive bit, but there is also big part of your application that is not. And I would say most products can be developed in many languages, and they will perform just fine. So Python's ecosystem saves you time and money to write your own lib because certain things you want to use do not have an SDK in your chosen language.
- thesuperbigfrog 3y agoIf Python works best for you and your project's needs, by all means use it. All tools have advantages and disadvantages which make them better suited for some types of work and less well suited for others.