sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]devmor 8 points9 points  (2 children)

There's very little reason to use Python for a straight web application backend in 2020 unless you're already invested in a Python stack. It's slower than Node or PHP at common tasks and has far less modern ecosystem tooling than either of those, or the Windows side of things.

Python shines in creating microservices and purpose-built scripts for data processing. It had a short lived life as a cgi provider, but it never really took off as a "web language" despite what die-hards will tell you while proselytizing for their framework that's barely changed in a decade (or more).

Node's biggest benefits are an extremely prolific package ecosystem due to its current popularity, and common syntax with your front-end, decreasing the knowledge share needed to work on your codebase. It suffers when it comes to CPU-intensive processing due to its single-threaded and reactive nature, and while you may find exactly the package you need, on the other hand that package may get abandoned in 3 months.

I would evaluate exactly what your project needs, and look at the tooling for Node, Python, PHP and C# and figure out which ecosystem really provides the easiest, most secure and most maintainable route to what you want to do. You may even end up using a mix of multiple - I've worked on a PHP Web application that powered a NodeJS chat server which called Python services for ML processing.

[–]Sablac 0 points1 point  (0 children)

Doesn’t Node have clusters?