Like I said. xenForo may know how to accomplish it, but they need to know how to accomplish it on any host. Right now, they're telling everyone to move to 7.2. (Not straight up, but yes, that's what they're doing.)
Let me put it simply then. A car is not an airplane. People will try to turn cars into little airplanes, but it simply will not happen.
Asides from WebFaction, I don't know of any shared hosts who allow the sort of things which are necessary and that it because the hosts themselves are probably a decade behind the rest of the world technologically.
Innovations happen, but they hold the world back. Plus, if you're paying $200 for a forum software, then you really want a host who actually knows what they're doing and makes an effort to stay current, otherwise just use phpBB.
Beyond that, there's always the choice of using a VPS, it's only like $3/month, although it might take some basic server administration know-how. There are VPS' complete with cPanel and people giving you help, but those are far pricier.
And that's even before we get to the point of supporting ridiculously old versions of PHP for really long times, when any host worth their salt should have phased those out long ago and holding back the software that way.
Again, if you're already paying a fair chunk, then they should at-least be that competent, it's not like people are going to be running this stuff on free hosts and the like. Pay a large premium for a top quality software only to skimp on the host.
I don't like them. But, if they know more about something, I won't discount them. PHP is the industry standard right now. Every time I see a new platform like Wordpress or xenForo, one of the requirements is PHP. Why? Not only because of it being industry standard, it's because hosts support it.
It's not an industry standard at all.
People use it because anyone and their grandma can deploy the thing, and even then, things aren't even that simple with things like fiddling with database permissions, file permissions, server settings, etc. so that you don't get hacked.
Above that, there are hordes of cheap Wordpress programmers who will do almost everything they can to make easily hackable plugins for you, but at-least they're cheap and plentiful.
You see, PHP appears easy and simple on the surface, right until you factor in security and that suddenly becomes the admin's problem.
It is so easy for anyone to quickly whip up a web-page, one of the tauted advantages of the language, but they can be hacked within a day and securing things involves reading countless thousands of pages from the manual, watching new reports closely in dozens of different places, or praying that the framework handles it.
Do you know what one of Drupal's vulnerabilities was? It was that instead of using real prepared statements, they decided to use *emulated* ones, a feature the PHP Core Team should never, ever, ever have implemented as it's not secure and people will wind up picking for "performance".
And for the record, in every platform other than PHP, prepared statements are actually faster than the emulated ones due to the use of query pools or the database caching the statements.
Even Facebook, the biggest user of PHP, winded up creating their own language which somewhat looks like PHP, but make no mistake, it is nowhere near similar.
The reason that XenForo uses PHP, especially the classical way of using it, is because it is easier to get their customers to migrate to PHP7 than it is to get them to migrate to Python or to get people to run it as a web app.
I knew this before you said it. That's (bolded) the other reason why I don't like JS. vBulletin has been using them for years, and it bogged down servers. When I finally got my own vBulletin license, I was ready to roll, until I realized as owner of a few sites, I realized JS is dragging the server sometimes. vB4 showed glaringly how bad it is. *snorts and laughs*
JavaScript is an order of magnitude faster than PHP, although it has it's own problems. The reason that your server is / was running slow is actually because of PHP and the architecture of your software.
With JavaScript, it fired off really frequent requests at a stack which can barely take any requests at all. Elsewhere, you can sometimes even get things faster by a factor of ten thousand or even more, it really depends on the route, architecture, and language.
Plus, with modern technologies like WebSockets and friends, you can just hold a connection open and push events as they happen rather than having every user firing off who knows how many queries just to get a bit of data every second, even if nothing has changed.
In addition to that, classical systems hold a lot of state on the server, rather than holding more data on the client and pushing only what's changed or is necessary.
I saw that, but then again, that was the old style of PHP. This is 2018, if that happens again, the PHP brand will be tarnished.
Have you ever read Eevee's Fractal of Bad Design? It's really the same PHP and it's broken in more ways you can possibly imagine. It's impossible to completely fix without breaking every bit of code and the core team are terrified of having the same sort of schism as with Python where some people are on 2 and others on 3 and the situation ensues for over a decade.
Every-time I speak to programmers from any stack other than PHP, there is one unanimous opinion. PHP is slow, insecure, and horribly designed. That is universal. People'll have their debates of whether one language is better than the other, but the moment PHP comes up, it's like a unifying force.
In fact, one major player in the PHP ecosystem who helps to do the standards left in a rage because all the recruiters thought they were incompetent because they were mainly a PHP programmer and wouldn't give them a senior position.
That is to say, the brand has been irreparably tarnished.
scraping is the act of pulling your content and put it on their site
I'm not even sure where you got this from or what it refers to, if you do find out, then we can continue that, otherwise it'll be a little unfruitful.
I could say the same for you and PHP
There is no misunderstanding, I'm not entirely a layperson looking at the situation from the outside, I have actually seen PHP's source-code, and have studied a fair bit about Cloudflare, DDoS attacks (bored lol), performance, building scalable systems, etc.
To put it simply, you can lead a man to water, but you can't make him drink.
I say what I say, and if you get to take something away from it, then great. Otherwise, meh.
I don't like them. But, if they know more about something, I won't discount them.
Do you know what they were criticising in one case recently? The random number generator. Random numbers are the lynch-pin of all security.
There was a case where the numbers were not truly random, and you wouldn't know if you didn't dig deep into a bit of the documentation no one ever reads. And then, they mocked the core team for dismissing the issue and blaming developers for not memorising the manual.
Do you know where random numbers are used in computer systems? Cryptography, session management, etc.
Every-time you login, the server generates a bunch of random numbers, translates those numbers to text, and then it sends that random text to you in a cookie and every-time you send that cookie to it, it'll recognise it as you and grant you admin access and what-not.
I can expect Google to take security seriously. Ditto for Microsoft. Facebook. Mozilla. The Python folks. And so on. It takes a certain air of paranoia. But, I can't take PHP seriously in the slightest, it's always... Uh, I think it should be safe.
That is partly because quite a few other languages for the large part are meticulously designed by some of the brightest minds in the world, while PHP was quickly cobbled together as a bunch of utilities for C programmers to quickly throw together a website and it grew far beyond what they intended.
It's like a physics teacher trying to compete against Einstein in physics.
Likewise, operating system developers and what-not who have been in the industry for many decades and written highly acclaimed papers and invented whole new paradigms, etc. meticulously designing systems against random C programmers randomly slapping things together.
And even then, PHP can be outright ridiculous at times. One of the errors, is or at-least was, this:
Code:
Parse error: syntax error, unexpected (T_PAAMAYIM_NEKUDOTAYIM)
That one error compared to every other error which is in English is instead in Hebrew. Hebrew. I mean, come on. And then, the core contributors had a brawl and the leader and creator of PHP, Rasmus and his faction, insisted on keeping it because it shows their respect to the contributions out of Israel.
In the end, they compromised after someone discovered some way of wrangling the parser into spitting out '::' as-well producing:
Code:
Parse error: syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM)
You now know what double colon means in Hebrew.
Learn something new every-day. Again, nothing against Israel, but this is simply bizarre.
There was a large scale hack towards a specific version of Wordpress.
The problem with Wordpress is that these sorts of exploits (SQL Injection, etc.) shouldn't even be happening, not in 2018. It's a solved problem.
I doubt Oracle will want that to happen again.
People don't even really use Oracle MySQL anymore, at-least not those who care about performance. There's that fork, MariaDB, which was done by the creator of MySQL.
We are talking about xenForo, and it's relevant. I bet when people search this page, they will learn a thing or two. But yeah, we could do that.
People will see the text wall and be like... Uh... No... Not reading this, most likely.