Earlier quoted context omitted.
the coffee and water and juices aren't too bad either. :)
Juices are higher in sugar and calories than soda....
but they're not generally 'less healthy' than a glass of juice from a local restaurant.
The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
81–90 of 102 posts
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#82It 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
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#83This seems like an interesting alternative direction like what HHVM was trying to accomplish.
PHP7 is faster than HHVM nowdays, and looking at the benchmarks for this .net version it's not a whole lot faster. It could even be that part of the win here comes from not needing to check all the php files on disk for changes.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#84Earlier quoted context omitted.
Writing your own userland implementation of prameterised queries is what you consider “very secure”? I’d hate to see what you think is terrible then.
What exactly is your criticism here? Do you know of some issue with prepare()? The quality of the core Wordpress code is quite high. You could argue that the plugin system is a footgun, but it’s kinda an essential element if you want extensibility.
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 the code.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#85Alot 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.
The problem's normally not Wordpress itself (when kept updated), it's the trash fire of plugins that float around it, leaving all sorts of security issues in their wake.
if you actively encourage and enable an ecosystem, you have some kind of responsibility. maybe less that the person who installed it, but the whole WP thing is for non-technical people. it’s still ethically questionable and shameful
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#86Alot 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, or automated tests): Wordpress will make it harder, and if you take over an existing Wordpress site, there's a non-zero chance that the previous developer wasn't doing it, making the hairball of code underneath the shiny interface even harder to work with.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#87Earlier quoted context omitted.
What exactly is your criticism here? Do you know of some issue with prepare()? The quality of the core Wordpress code is quite high. You could argue that the plugin system is a footgun, but it’s kinda an essential element if you want extensibility.
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.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#88Earlier quoted context omitted.
Jekyll or Django, or a hybrid?
Not even close. That's like saying that the alternative to Photoshop is C++.
Agreed. Django gives you the tools to build applications, wordpress is a point and click setup for most people. The users are extremely different audiences.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#89Earlier quoted context omitted.
Not even close. That's like saying that the alternative to Photoshop is C++.
That might be a bit harsh. Closer comparison might be photoshop to gimp?
Not really. Gimp is still an image editor.
Django is your GUI/imaging framework and libraries if you’re going to make that comparison.
Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
#90Earlier quoted context omitted.
> "(ease of deployment, ease of extension, ease of configuration, auto-updates, plugins, etc.)" But those are The Right __and__ The Wrong. For example, adding Composer to the WP "stack" makes sense. But now you've eliminated 90% (?) of the WP "developers." That is, in the Universe of WordPress Composer is more friction, not less (i.e., ease of use). Long to short, for better or worse, WP is Justin Bieber. It will nev…
>But now you've eliminated 90% (?) of the WP "developers." Maybe, but it wouldn't be impossible to rebuild plugins around Composer and PSR standards. And doing so would make them better organized, and make it easier to manage third party dependencies. If you were going to build Wordpress from scratch, today, that's probably what you would do - just make plugins a special case of Composer dependencies. The only questi…
I think before we worry about plugins and themes it would make much more sense to bring WP core itself up to date. What good is a nice, clean, properly organized plugin, if it's sitting on a foundation of sand.
I filed a core bug report once. Long to short, if I passed (I think it was) false to a core function, I got very unexpected results. The dev that replied to me said, "Well then don't do that." Huh?
The idea that the function should check, that it should be aware that humans (and their code) make unexpected mistakes, was completely foreign to her / him. I lost a lot of faith that day. I lose a bit more every time I go poking around in core code. I'm no Super DevMan. So when __I__ see bad patterns you know something is wrong.
p.s. Fwiw, even the lead dog (i.e., Automattic) has some nasty code habits. Simply dumbfounding.