Live data from Hacker News

WordPress on .NET

peachpie.io

41–50 of 174 posts

Re: WordPress on .NET

#42
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.

Re: WordPress on .NET

#43
post #26

I've been following the peachpie project for a while. The effort they put in is very impressive. They choose to heavily modify the C#/VB compiler (Roslyn) to handle php syntax. Microsoft should be investing time into helping them succeed, it would be great to see the Roslyn compiler platform become more broadly used.

Microsoft is doing quite a bit of supporting, can't complain there :)

[deleted]

Re: WordPress on .NET

#44

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.

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.

Re: WordPress on .NET

#47
post #11

I don't care about performance, show me if security has improved! (which in the case of Wordpress can't be that hard)

You're seriously out of touch if you think the WP Core is not secure. You must realize they have a very competent team (https://automattic.com/), not to mention thousands of OSS developers that continually contribute. Does your company, or does this small team of techs even come close?

https://wordpress.org/about/security/

Re: WordPress on .NET

#48
post #11

I don't care about performance, show me if security has improved! (which in the case of Wordpress can't be that hard)

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"?

Re: WordPress on .NET

#49

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.

Or "facebook uses it". That one tends to go far.

Re: WordPress on .NET

#50
post #11

I don't care about performance, show me if security has improved! (which in the case of Wordpress can't be that hard)

I'll do you one better.

We're hosting a private-facing WordPress with several custom post types and some custom fields using ACF Pro. Then we pull directly out of the database with some not-too-complex and fast SQL queries and build a static site with Jekyll. The whole thing is about 200 lines of Ruby + a bunch of configuration for each post type. I'm working on making this a little more generic, because this thing really smokes.

In migrating to this, I'm doing a similar process with our previous mess of a WordPress site by pulling from the DB and writing JSON. WP All Import + ACF plugin takes care of the rest.

All uploads are now served out of S3 buckets and our editors write Kramdown now instead of HTML and inline CSS. We can easily A/B test or Multi-Armed Bandit now too.

It would have been a lot easier if the Wordpress REST API weren't a piece of junk. SQL is consistent at least.

Post reply on HN