Live data from Hacker News

WordPress on .NET

peachpie.io

111–120 of 174 posts

Re: WordPress on .NET

#111
post #60

PHP is about to face Embrace, extend and extinguish?

Shared Apache+mod_php+MySQL hosting turns out to be impossible to extinguish…

Yes. I had hoped node.js would fill the role of a cheap generic hosting platform with taste. But while it works well for me on VMs/cloud, managed hosting for node.js is nowhere near PHP in terms of ubiquity.

Re: WordPress on .NET

#112

This is a great way for Microsoft to show the potential of and build awareness for .NET core, I hope they are helping these guys. The nuget thing is inefficient, MS should plot a path to make npm a first class citizen in all ms tools.

No, please, no. It'd be nice if somebody would get back to maintaining nuget packages for front-end stuff, the way it was a few years ago, before everyone collectively threw in the towel, shrugged, and said, "I guess npm isn't that painful. You know, compared to having forks shoved in my eyeballs, it's quite nice."

Re: WordPress on .NET

#113
post #92

Earlier quoted context omitted.

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.

It might be a personal thing, but if I had to choose between working for a customer A with SharePoint and customer B with WP, I wouldn't hesitate to choose customer A, even with SharePoint 2007.

May I ask why?

Re: WordPress on .NET

#114
post #90

Earlier quoted context omitted.

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.

I would look at sitecore. It's still .net, but it is closer to wordpress in that you wouldn't necessarily build a sharepoint in it, but you can build pretty much anything else in it. Disclaimer, I work on the UX/UI side of a company that focuses solely on sitecore.

Thanks for sharing this, but what exactly does this provide that WP doesn't to justify the cost?

Re: WordPress on .NET

#115

Earlier quoted context omitted.

I laughed at that. As much as I still shun MS platforms, I have never heard anything good about PHP as a language other than "it worked and was available at the time". Why someone would migrate in this direction is beyond me ;-) but that's just my opinion of course.

Critical mass, availability of developers, good documentation, free. There are many reasons why people pick one technology over another.

Aren't C# devs at least as easy to find as php devs already? This would vary regionally I suppose. I'd worry about the future availability of php devs if node/.NET keep growing as open source web backend platforms.

And .NET is as free as php?

Re: WordPress on .NET

#116
post #92

Earlier quoted context omitted.

It might be a personal thing, but if I had to choose between working for a customer A with SharePoint and customer B with WP, I wouldn't hesitate to choose customer A, even with SharePoint 2007.

May I ask why?

PHP and the overall quality of average WP code?

Re: WordPress on .NET

#117
post #84

Earlier quoted context omitted.

Since you need to support versions of PHP that don't support the extensions that have parameterized queries.

Except… you don't? > 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.

PDO is disabled by default, and was even on default installs of 5.6 last I checked.

Re: WordPress on .NET

#118
post #67
post #51

Earlier quoted context omitted.

The benchmarks http://www.peachpie.io/benchmarks show peachpie outperforming PHP7 easily by 100x.

On Azure, without Opcache enabled. That's not a very good comparison.

I would strongly suspect that the fact it's without opcache by itself makes it pretty much meaningless for any kind of a real-world application.

Re: WordPress on .NET

#119

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.

Err, deploying PHP on IIS is actually very basic.

Re: WordPress on .NET

#120
post #7

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.

If only the .NET version would use proper security (no permissioner to modify files, sandboxed plugins, ....) then yes. But that would be a rewrite.

Otherwise the .NET version only remedies vulnerabilities in php and not those in WordPress or its plugins.

Post reply on HN