Realtime Data Update with NodeJS and WebSockets

[Teodor]

Hello @nepatriot

@nepatriot

It seems like Wappler is going in the direction of Node.JS which is great.

However, those of us building apps in PHP before Node.JS was available are stuck in the past. We (at least I) can’t easily switch to Node.JS where all the new fancy features are coming o

The problem with PHP is not we don't like it or we are ignoring it or we don't want to develop it. It's not a thing of the past and it's perfectly fine to use it.

It's actually that:

@patrick

The problem with PHP is that you have a lot of different configurations and versions that you need to support. With node we have lot more control over the environment and the server is build-in.

With PHP we always had to check which version is installed, are the required PHP modules installed on the server, which database drivers are installed, what server does it run on (nginx doesn’t support htaccess files which we use for routing). With node we don’t have this problem, we bundle all the required modules directly with it and we choose which modules we are going to use.

A one-click-magic tool which translates php to node.js could be possible for some simpler actions probably, but for more complex server actions, routing etc. it would be more difficult.
Also some features are only possible to be added in Node.js and exist only for it, because of the reasons I quoted above.