Please see my comment to the question.
Even though the question is not quite correct, it makes some practical sense. The situation with PHP popularity just eliminates many problems except… using this language itself, which I consider as a kind or ersatz. It's up to you of course; you still can solve many Web development problems. It's just makes the choice of an HTML server not really critical, you can choose nearly anything, depending on other factors.
There are many of those other factors. But let's consider just one kind of choice,
LAMP:
LAMP (software bundle) — Wikipedia, the free encyclopedia.
What would be the consequences? First, you can choose from the widest possible set of hosting opportunities. Moreover, the cheapest solutions are also most likely will be LAMP. You will have Apache service, which is extremely compact and light weight, compared with, say, IIS. It is one of the most reliable solutions, if not the most reliable. LAMP-based types of hosting are also the most well established. When you get such hosting, most likely you will get near-standard familiar environment, very similar in many hosting providers. Should you choose to get rid of your provider and switch to another one, who provide better service in terms of figures or quality of customer service, and, most likely, your environment will be almost the same. It's more likely that you easily find help, if you face problem, because so many people also use LAMP or know its components very well.
Installation of LAMP components for self hosting is also extremely easy, but this is rarely the choice. However, this is still the benefit, because you can easily install all the environment needed for development and test everything on your LAN (Intranet) or even local Apache server, with all required
modules.
Knowing all that, you still can make different choice, WAMP, IIS and a good number of less popular but more compact or specialized solutions. The choice is yours; and it may depend on many other factors.
[EDIT]
Or, I almost forgot: even if you decide to switch to ASP.NET, Apache still can work with it (but I have no idea where to get such shared hosting; I failed to find any, but it won't be a problem with expensive VPS or even more expensive dedicated hosting).
One solution is based on Mono with Apache mod_mono module, another, more modern one, with Microsoft .NET Core with Apache ASP.NET Core:
mod_mono — Wikipedia, the free encyclopedia,
.NET Core — Wikipedia, the free encyclopedia,
ASP.NET Core — Wikipedia, the free encyclopedia.
—SA