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.
I would like to see Beaver Builder do this, too.
The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
31–40 of 102 posts
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#32Can this solve the Wordpress security nightmare ? are we going to see hosting services built on PeachPie in the near future ?
Which nightmare? Maybe we can fix it. To answer your second question - yes, that's exactly what we're planning :)
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#33So, what's the WordPress equivalent in Python?
Jekyll or Django, or a hybrid?
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#34Can this solve the Wordpress security nightmare ? are we going to see hosting services built on PeachPie in the near future ?
The bulk of WP security issues stem from the 'writable file system' defaults that many plugins (and, to some extent) core either expect or encourage. I can't say all, but the huge bulk of security issues I've seen revolve around some exploit which ends up writing a new file, or overwriting an existing file, which is then publicly accessible. If your file system is not writable, the large majority of WP exploits go aw…
PeachPie doesn't allow this. We will enable the option once on-the-fly compilation will be implemented, but this is really really poor practice and we highly discourage the use of it.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#35Alot 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.
"If it is so awful, why is it on over 25% of sites?"
If McDonalds is so bad for you, why do they serve 550 million Big Macs every year?
WP is 'free', has a low barrier to entry, and for many years non-developers were able to relatively easily add custom functionality (sometimes done well, but often security and performance nightmares).
A lot of people make a lot of money from selling illegal drugs, or fatty foods, or bad investment/insurance products.
WP has its place, and in the right skilled hands, for the right projects, addresses many business needs decently well. Until it doesn't.
But this "right tool for the right job" argument has been beaten to death when it comes to WP. Biggest 'meta' issue I see with WP is that it doesn't do much to encourage most people "developing" on it to ever consider other tools; they just learn to fit more and more jobs in to the same ecosystem, whether it's a good fit or not. And due to the size of the ecosystem, it has enough gravity to keep attracting people to it.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#36Earlier quoted context omitted.
The bulk of WP security issues stem from the 'writable file system' defaults that many plugins (and, to some extent) core either expect or encourage. I can't say all, but the huge bulk of security issues I've seen revolve around some exploit which ends up writing a new file, or overwriting an existing file, which is then publicly accessible. If your file system is not writable, the large majority of WP exploits go aw…
PeachPie doesn't allow this. We will enable the option once on-the-fly compilation will be implemented, but this is really really poor practice and we highly discourage the use of it.
if there's a way you can enable writeable file sytem, but not compilation of anything executable, that may end up being the best of both worlds.
WP could address some of this by requiring plugin media/js assets to be copied over to public folders during an 'init' process, while requiring the core PHP code to be outside of the document root/public area. But it would break on certain hosting platforms (I know that years ago, Plesk templates would enforce that nothing could live outside the document root - every upgrade they'd change all PHP permissions to only allow PHP execution inside the document root, perpetuating poor security practices for anyone who wanted to host on plesk-managed servers).
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#37It would be amazing if they rewrote wordpress in C# using modern design patterns.
You could take “C#” out of that sentence and still be accurate. Wordpress is not and I imagine never will be anywhere close to “modern design patterns”. It’s not even close to old design patterns, unless Heinz has a namesake software design pattern. Wordpress uses practices that were considered a bad idea a decade or more ago, and still refuses to change.
Then perhaps, in true open source fashion, you can put your time where your opinions are and either start another project or help the wordpress team to correct what you think is bad.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#38Can this solve the Wordpress security nightmare ? are we going to see hosting services built on PeachPie in the near future ?
Saying Wordpress is a security nightmare is like saying Windows is a security nightmare. It has broad use, it has tons of people using it with outdated or unmanaged plugins on installs that haven't been updated in years...Some running near extinct PHP versions. If managed properly, put behind a firewall, etc it is quite safe. The hatred of Wordpress is laughable. It has its limits, but it meets most small-medium sized business needs when the project calls for minimal needs.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#39A fractal abomination.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#40Alot 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.
"If it is so awful, why is it on over 25% of sites?" If McDonalds is so bad for you, why do they serve 550 million Big Macs every year? WP is 'free', has a low barrier to entry, and for many years non-developers were able to relatively easily add custom functionality (sometimes done well, but often security and performance nightmares). A lot of people make a lot of money from selling illegal drugs, or fatty foods, or…
WP is really extensible. The way hooks and filters work and the way they are used trough the codebase allows you to completely alter and change virtually every aspect of the software. That includes everything from the admin UI to the processing and displaying of content. None of the modern alternatives are remotely as powerful and versatile as WP is.