this post was submitted on 04 Jan 2024
109 points (95.8% liked)

Programming

17525 readers
374 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] redcalcium@lemmy.institute 1 points 10 months ago (1 children)

Why not? Is it because a typical nodejs app include hundreds of npm dependencies? As long as it can launch and finish within 60s (default timeout for apache), you should be able to use it.

[–] TCB13@lemmy.world 2 points 10 months ago (1 children)

Who wants to wait 60s for a website to load?

[–] redcalcium@lemmy.institute 1 points 10 months ago (1 children)

Not saying you should use CGI (who does these days), but saying you could still use it if you want

[–] TCB13@lemmy.world 1 points 10 months ago

The point is that PHP is much more performant and doesn't waste resources as NodeJS does. While you can run PHP on CGI with a decent bootstrap performance that won't get people annoyed the same can't be said of NodeJS. Nowadays people do PHP-FPM which is way faster at scaling up that any NodeJS process manager out there and doesn't sit wasting resources when a particular application doesn't have requests.