81–90 of 174 posts
Running PHP and indeed WordPress on the .NET CLR seems like a great way to eliminate a whole tranche of bugs/vulnerabilities in one swoop. Respect.
Also, why would php-on-net be updated more often than one of the most used runtimes on the web?
I work at a large company and we are starting to branch out into other languages. the problem is most of our infrastructure in .NET. Something like this would be really cool as it would allow us to utilize PHP while not asking too much of infrastructure team. I might put in an OSS approval request for this.
PHP is about to face Embrace, extend and extinguish?
Earlier quoted context omitted.
WordPress security is complex. The core code is OK, security wise. Comparible to similar projects, I guess. The two major issues are that typically PHP runs with permission to modify the WordPress directory, which is useful for automatic upgrades, but means any exploit in any plugin, theme, etc. instantly becomes, "can replace WordPress". The other is that all themes and plugins are completely unsandboxed, and the qu…
> OK, security wise Since when is implementing your own home-grown shitty replacement for parameterised queries "OK"?
Earlier quoted context omitted.
On Azure, without Opcache enabled. That's not a very good comparison.
While I do know that Azure is owned by Microsoft I'm not so sure on why it's such a valid argument. In the end it's not like they're actively trying to ruin languages other than C# on their servers? Especially since that would ruin it for a lot of customers?
Earlier quoted context omitted.
Didn't they start with it and migrate away?
They use something called HHVM, which is a PHP compiler. http://hhvm.com/
Earlier quoted context omitted.
> OK, security wise Since when is implementing your own home-grown shitty replacement for parameterised queries "OK"?
Since you need to support versions of PHP that don't support the extensions that have parameterized queries.
> WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities
> PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0
Unless you mean "hosts that disabled PDO"… I think they can safely be ignored.
PHP is about to face Embrace, extend and extinguish?
Earlier quoted context omitted.
I think you might be the first case I've heard of of someone wanting to go from .NET to PHP.
We literally spend millions on licensing Share Point to do what WordPress can do much better and easier. I'm not saying we're going to start writing everything in PHP, but being able to experiment with WP could affect the bottom line in a big way.
Disclaimer, I work on the UX/UI side of a company that focuses solely on sitecore.