Node.js vs PHP: Which Environment To Choose For Your Next Project

preview_player
Показать описание


A debate that was never even into existence has today become a classic standoff in the mobile app development and web app development world, with developers struggling to make a choice between both environments.

Рекомендации по теме
Комментарии
Автор

I don't know where to start everything about that video is wrong.

unlimitedbytes-random
Автор

Wait wait wait wait !!! There are different porposes for each of Node and PHP! As someone specified in a comment, NodeJS is used as a server side JavaScript, let’s think about Visual Studio, some kind of .Net, or Java Applet, when PHP is meant to do ather type of jobs! There shouldn’t be a battle between these two languages. Maybe PHP vs Python .. and even this I am not sure that it can be a battle :))

donlywaybv
Автор

Actually php 7 is faster than node js on intensive cpu operations. With swoole, php blows out node js in i/o speed. With swoole, php can do multi threading and asynchronous well. Php can also handle nosql and json well. Working with relational database is also too much pain using nodejs. I don't see any reason to use node js over php.

ojsojs
Автор

Now What's the best Php Laraval or Node js express js ???

darshmostafa
Автор

thank you very much for the great information you have given in this video

abdougouchti
Автор

7.3 is faster than node in a lot of ways actually

hankschroder
Автор

Great work bro. better than 10 min of into...

divyanshusah
Автор

Thanks! Good concise video, lots of info in short amount of time.

tdevkw
Автор

video: coding on node is complicated
also video: coding on php is easier and simpler

me: so... tell me how many times did your php code fail to validate variable types and gave you headaches...

paulodetarsonr
Автор

Gee. Putting some screen grabs into a video is so NOT helpful.

mrphilbert
Автор

Holy fuck will I never use nodejs ecosystem for anything that handles money or critical. Unless you end up writing your own framework, the package quality, even for well known one, is hot garbage. We had to throw out socket.io library from a project because it turned out to be a major pain in the ass and just having breaking issues. And I'm not even talking dependency tree. We had over 1000 packages at first and we cleaned that out to something like 400 at the moment and we threw out some major packages because of shit quality (like we threw out Prometheus libs because there wasn't a single good one).

Basically to make something quality, the amount of work to do is HUGE and it's expensive. Unless you literally roll in tech money or investment, you are not gonna pick nodejs as your tool as primary tool.

ojsojs
Автор

PHP is the elephant in the room .
node is a nice try ... by the cool kids ... but javascript is slowwww, saying that node is meant for fast aplications is a joke !

Zen-lzhc
Автор

i assume that 90 unlike's are from php developer's xD.

jvcreator