Suggestion - Making a PHP and Node.js Version rather than moving away from PHP
I just thought about the future of SourceBans++ version about moving away from PHP, and I got an idea instead of that way.
What about releasing PHP version and Node.js version of SourceBans++ separately? For more compatibility, server owners can use PHP version. If the hosting provider supports Node.JS and for more performance, they could use the Node.js Version. |
Re: Suggestion - Making a PHP and Node.js Version rather than moving away from PHP
Quote:
That would typically also mean separate maintainers, and two different - but yet identical projects, which often leads to the one of them being somehow maintained, while the other one is ending up on getting forgotten. Quote:
There are so many things suggesting both that PHP would be the better choice for speed / performance, but also things suggesting Node.JS is. As to your compatibility part, e.g.: Quote:
So where PHP is available on like all webhosting companies? But Node.JS not? There I would personally keep the focussing on PHP one, eventually by rewriting older, legacy(, and potentially "shitty") parts, rather than moving over to / focussing in another way, where the majority of the (current) user base might not even have a chance of being able to follow. There are already a various of different threads similar to "how many 128tick servers can I run on this little $1/mo pizza slice VPS?", - with that attitude, a move away from PHP and towards something that is even more complicated for a lot of users, that really yells for trouble going forward.. That's obviously my 2 cents / view on the situation. |
Re: Suggestion - Making a PHP and Node.js Version rather than moving away from PHP
Quote:
|
Re: Suggestion - Making a PHP and Node.js Version rather than moving away from PHP
Quote:
|
All times are GMT -4. The time now is 18:12. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.