Live data from Hacker News

WordPress on .NET

peachpie.io

121–130 of 174 posts

Re: WordPress on .NET

#121

Earlier quoted context omitted.

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?

Not in places where wages are low.

Re: WordPress on .NET

#122

Earlier quoted context omitted.

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.

What "default"? Compiled from source? Debian package?

Just checked, seems enabled by default on FreeBSD.

(Commented out in php.ini doesn't mean disabled — here it's enabled in separate files like /usr/local/etc/php/ext-30-pdo_mysql.ini)

MODX Revolution uses PDO exclusively, never had problems with it on any hosting service.

Re: WordPress on .NET

#123

Earlier quoted context omitted.

> Http.sys also seems like a more secure product than openssl How is a goddamn HTTP parser in THE KERNEL more secure than a crypto/TLS library? http.sys is a fundamentally horrendous idea, see CVE-2015-1635 https://technet.microsoft.com/library/security/MS15-034 An exploited HTTP parser shouldn't lead to RCE "in the context of the System account".

The .NET Core example in the article uses the ASP.NET Core Kestrel server which operates entirely in user mode.

I know about Kestrel, I'm responding to that particular phrase in the comment :)

Re: WordPress on .NET

#124

Any chance we can get PHP's HashDoS vulnerability removed if we switch to PeachPie? PHP 7.2 will make libsodium a core extension, so if you use that, you can make use of SipHash-2-4.

Interesting question. Beside that ASP.NET limits request size, Peachpie uses .NET hash function that differs from that used in PHP. Am I close ?

Re: WordPress on .NET

#125

Earlier quoted context omitted.

> Http.sys also seems like a more secure product than openssl How is a goddamn HTTP parser in THE KERNEL more secure than a crypto/TLS library? http.sys is a fundamentally horrendous idea, see CVE-2015-1635 https://technet.microsoft.com/library/security/MS15-034 An exploited HTTP parser shouldn't lead to RCE "in the context of the System account".

That's mostly client-side and easily avoided by not using IE/Edge. .NET uses its own library as well I believe. Not sure what the default is. Historically, the schannel infrastructure has been secure, especially as compared to openssl. >How is a goddamn HTTP parser in THE KERNEL more secure than a crypto/TLS library? Because, lets face it, openssl is a shit project of legacy code no one wants to fix and https a desig…

"an attacker would have to send a specially crafted HTTP request to the affected system"

"Disable IIS kernel caching"

That's definitely not client-side at all. IIS is the thing that uses http.sys, and classic ASP.NET apps (not the new Core stuff) are usually deployed with IIS.

Re: WordPress on .NET

#126
post #2

<3 this! any idea on when it will be production-ready?

Hard to say. We want to test it thoroughly before releasing version 1.0. Also, we are still missing a few key functions/constructs of PHP, such as eval() or PDO. A rough timeline would be "a few months" :)

Re: WordPress on .NET

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

Yes, and look at the avg response times. It looks likely that the webserver can't handle the load. The number of concurrent requests should be limited.

Re: WordPress on .NET

#128
post #94
post #90

Earlier quoted context omitted.

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.

I only had a project with Sitecore, v6.5 at the time, and really enjoyed using it. Just the overall replication of Windows desktop for the backend management UI seemed a bit extreme. :)

Yeah it was a bit odd for me too, coming from PHP and node land. Most of the editing should be done in the experience editor.. which is fairly WYSIWYG in context editing. Concrete5 still does that part of it better. Sitecore has a lot of engagement value scoring and content a/b testing built into it.

Re: WordPress on .NET

#129

Earlier quoted context omitted.

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?

Not in places where wages are low.

[deleted]

Re: WordPress on .NET

#130
post #54

Earlier quoted context omitted.

This is on .NET Core, so you can actually run this anywhere! I do a lot of Core development on a Mac, but it runs well on AWS/Linux/my toaster. Weird times, huh?

Out of curiosity, why do you use .NET? (Assuming you use Mac/AWS/etc because you like them)

Because C# is awesome. The most intuitive OO language I have ever used.
Post reply on HN