Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

hanselman.com

Post reply on HN
Print view View original

91–100 of 102 posts

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#91

Post by laken »

sodosopa wrote: post #82
ckluis wrote: post #2

It would be interesting if someone ripped out the php/js for the gutenberg editor from wordpress as a compiled .net core wysiwyg-block-based editor for use in other .net core projects.

now if they only made gutenberg stick to wcag 2.1 or Section 508, it could change the world. Otherwise, it's not too different from the Frontpages or NetObjects Fusions of the past

I'm a contributor to the WordPress A11y team, and trust us, we are trying. It's an a11y nightmare, and the majority of contributors to Gutenberg seem to not care. The goal is for it to meet WCAG 2.0 on merge, but that's running close. The majority of Gutenberg contributors think of the a11y issues as "low priority."

Because you sound like you know a bit about a11y, we could really use a hand. Accessibility meetings are weekly in the Make WordPress.org Slack instance. One of the problems is that Gutenberg's technology is very different than the rest of WordPress core, so some of the a11y contributors to WordPress Core are staying away from code-contributions to Gutenberg because of that (myself included). I've been playing around with node.js a bit to try and contribute, but it's very different than what I'm used to (PHP).

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#92

Post by kimdotcom »

sjellis wrote: post #86
kimdotcom wrote: post #30

Alot if shitty attitudes about Wordpress here. If it is so awful, why is it on over 25% of sites? It has helped alot of people make alot of money, and continues to do so.

Wordpress is the Microsoft Access of content-driven Websites: it is amazing because the lowers all of the barriers to entry (time, cost, expertise), but it has bad practices and a bad programming language built-in, so stuff built with it is born bad, and will get worse, partly because the folks using that tool are frequently untrained. Think of any modern development best practice that you like (e.g. version control,…

Take a look at roots.io

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#94

Post by stephenr »

AmericanChopper wrote: post #87
stephenr wrote: post #84

Earlier quoted context omitted.

Parameterised queries done properly are sent to the database server specifically as a query with placeholders and values - the values are never evaluated as sql, there is no chance for a userland bug/attack to perform sql injection using them. What wordpress does is basically glorified printf, substituting values into a string. If you can’t see how this is a danger, you’re in no position to comment on the quality of…

Right, so you actually have absolutely nothing to say about the quality of wpdb. My point stands. The worst problems in Wordpress are the plugin ecosystem and poorly maintained instances.

Just because you choose to ignore valid criticism, that doesnt mean there is no criticism.

Go read https://blog.ircmaxell.com/2017/10/disclosure-wordpress-wpdb...

A couple of little snippets to highlight the point I'm trying to make:

> The current system is insecure-by-design. That doesn’t mean it’s always hackable, but it means you have to actively work to make it not attackable. It’s better to switch to a design that’s secure-by-default and make the insecure the exceptional case.

> The best path forward would be to switch to PDO/MySQLi and use real prepared statements and not emulate them in PHP land. That’s the best path forward.

But given that the core wordpress team basically ignore this type of suggestion from PHP core contributors, why would I expect you to believe me about it here?

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#95

Post by wordpressdev »

StavrosK wrote: post #74
wordpressdev wrote: post #19

So, what's the WordPress equivalent in Python?

Wagtail. There's also a very nice library that can dump all the pages from Wagtail into a static site which you can then just copy to a CDN, giving you the best of both worlds: The ease of publishing of dynamic sites and the speed/ease of deployment of static sites.

Wagtail looks good. Wonder what's the learning curve from someone coming from WordPress development background.

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#96

Post by user5994461 »

mgkimsal wrote: post #78
user5994461 wrote: post #66

Earlier quoted context omitted.

A poor comparison. McDonalds is highly variable per location. Just because the one closest to you might be terrible doesn't say anything about the rest of the world.

food, not service. mcdonalds food is about as 'same' as you can get per location around the globe.

The point being, no it's not.

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#98

Post by SahAssar »

AmericanChopper wrote: post #70
petra wrote: post #22

Can this solve the Wordpress security nightmare ? are we going to see hosting services built on PeachPie in the near future ?

Wordpress core has very secure coding practices, and if you can find an 0-day in it, then you've done very, very well. The problems with Wordpress are mostly: 1. WP installations are often not properly configured or maintained. 2. The plugin ecosystem is a mess of vulnerable and/or malicious code, or simply dead code that isn't maintained yet still deployed in the wild.

It took more than 7 months to fix https://blog.ripstech.com/2018/wordpress-file-delete-to-code... and at the time rips went public with it (after waiting for 7 months) it still was not fixed.

That a POST param even was used to as the path to a file to delete without sanitizing it is not usually indicative of "secure coding practices".

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#99

Post by sodosopa »

laken wrote: post #91
sodosopa wrote: post #82

Earlier quoted context omitted.

now if they only made gutenberg stick to wcag 2.1 or Section 508, it could change the world. Otherwise, it's not too different from the Frontpages or NetObjects Fusions of the past

I'm a contributor to the WordPress A11y team, and trust us, we are trying. It's an a11y nightmare, and the majority of contributors to Gutenberg seem to not care. The goal is for it to meet WCAG 2.0 on merge, but that's running close. The majority of Gutenberg contributors think of the a11y issues as "low priority." Because you sound like you know a bit about a11y, we could really use a hand. Accessibility meetings a…

Thanks for the response. I think most web devs have always treated accessibility as "low priority". It's not top of mind until it becomes a part of your daily job. I've been there.

How close is it to 2.0 A, currently?

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#100

Post by laken »

sodosopa wrote: post #99
laken wrote: post #91

Earlier quoted context omitted.

I'm a contributor to the WordPress A11y team, and trust us, we are trying. It's an a11y nightmare, and the majority of contributors to Gutenberg seem to not care. The goal is for it to meet WCAG 2.0 on merge, but that's running close. The majority of Gutenberg contributors think of the a11y issues as "low priority." Because you sound like you know a bit about a11y, we could really use a hand. Accessibility meetings a…

Thanks for the response. I think most web devs have always treated accessibility as "low priority". It's not top of mind until it becomes a part of your daily job. I've been there. How close is it to 2.0 A, currently?

It's tricky to even tell now, unfortunately.

These are the issues that are remaining that we (the a11y team) want fixed prior to merge: https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is...

When these issues were added to the merge proposal, they were what were left for 2.0 level A. But accessibility regressions have gotten introduced many times now while other developers are working on things from other merge proposals. We were doing some tests with users of various assistive technologies, and these were also the problem areas for them.

Here are the open a11y issues for Gutenberg in general: https://github.com/WordPress/gutenberg/issues?page=1&q=is%3A...

A lot of these are still quite important. The UI is also super confusing, as it's an entirely new type of UI, and it's confusing to figure out where everything is if you can't see it. We are working on some documentation that describes it for assistive-technology users, as it's virtually impossible for them to infer how it works.

Post reply on HN