9 ms·
The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie
- ckluis 8y agoIt 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.
- kimdotcom 8y agoI would like to see Beaver Builder do this, too.
- sodosopa 8y agonow 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
- laken 8y agoI'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).
- sodosopa 8y agoThanks 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?
- laken 8y agoIt'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%3Aissue+label%3AAccessibility+milestone%3A%22Merge+Proposal%3A+Accessibility%22 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%3Aopen+is%3Aissue+label%3AAccessibility&utf8=%E2%9C%93 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.
- sodosopa 8y agofrom earlier today "WordPress aims to make the WordPress Admin and bundled themes fully WCAG 2.0 AA compliant where possible." https://wordpress.org/about/accessibility/ https://wordpress.org/about/accessibility/ The jump from A to AA is difficult and to put the statement of AA out there, is bold (and probably naive).
- laken 8y agoYes, that’s our new accessibility page! I’ve heard the argument by many though that if someone needs WCAG AA, that they can just use the classic editor (which will be supported via a plugin maintained by wp.org). Will be interesting to see how it all plays out
- wpdev_63 8y agoIt would be amazing if they rewrote wordpress in C# using modern design patterns.
- dan1234 8y agoOne of the major selling points of WordPress is its huge array of 3rd party plugins. You'd need to port the most popular ones before the C# version got any traction. How's Linux for .NET hosting? Because Linux hosts are generally cheaper than Windows hosts.
- magnat 8y ago> How's Linux for .NET hosting? For .NET Core there are binary packages [1] for Debian/Ubuntu, Fedora, Red Hat and SUSE, so you can apt-get/rpm/yum hosting environment in a matter of minutes. I'd say it's easier to set up and run ASP.NET Core app with Apache or nginx as reverse proxy than with IIS. For "old" .NET you are stuck with Mono [2] which works okay-ish if you don't use Windows-only dependencies. [1] https://www.microsoft.com/net/download/linux-package-manager/rhel/runtime-current https://www.microsoft.com/net/download/linux-package-manager... [2] https://www.mono-project.com/ https://www.mono-project.com/
- squirrelicus 8y agoI've been having great luck with ASP.NET core / nginx. Very stable, low overhead with 40k req/sec served in a ubuntu VM. I hate MVC, so I've been using Nancy (Sinatra based) as the web framework. I'm highly confident in .NET Core being production ready.
- custos 8y agoDecompile the resulting library and start refactoring and adding comments?
- nicoburns 8y agoWhy would you start with a decompiled binary when the source code is available?
- alexandernst 8y agoHoly mother of the pile of crap this thing must be...
- ihsw2 8y agoWe were so preoccupied with whether or not we could, we didn't stop to think if we should.
- dbwest 8y agoReminds me of 'Phuby on Phails', Ruby on Rails in PHP...just because. I think the WTFF is about the same (off the charts).
- egypturnash 8y agohttp://adrianzandberg.pl/cobol-on-wheelchair/ http://adrianzandberg.pl/cobol-on-wheelchair/
- oaiey 8y agoAs much as I love .NET I think, it is not the right thing to run PHP apps on it. PHP is good on its own. However, Peachpie seems like an awesome showcase what is possible in modern environments and apps.
- btschaegg 8y agoAaah, it's always nice to see a well-placed JP quote :) I raise you another: God help us; we're in the hands of engineers.
- deleted 8y ago[deleted]
- wordpressdev 8y agoSo, what's the WordPress equivalent in Python?
- kimdotcom 8y agoJekyll or Django, or a hybrid?
- armandososa 8y agoNot even close. That's like saying that the alternative to Photoshop is C++.
- mgkimsal 8y agoThat might be a bit harsh. Closer comparison might be photoshop to gimp?
- giancarlostoro 8y agoJekyll is closer to Wordpress but Django is a library / framework so Photoshop to C++ is kinda close, but a little too far.
- mgkimsal 8y agoI'm thinking "django cms", not just django - sorry. colleague of mine has been doing a lot of work in django cms the last year and I conflate the two sometimes :)
- giancarlostoro 8y agoAh makes more sense.
- armandososa 8y agoHuh. Django cms actually looks pretty nice.
- petra 8y agoCan this solve the Wordpress security nightmare ? are we going to see hosting services built on PeachPie in the near future ?
- frankzander 8y agoThis can only be solved by a rewrite.
- mgkimsal 8y agoThe 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 away. However, you lose the "press here to upgrade your entire site and all the plugins in one easy step!" functionality, and the "upload files via the browser" ease-of-use. If you're truly modifying public media files on regular basis, a non-writeable file system kinda stinks (either make the FS writeable or use an external media host, which adds complexity and cost). MOST systems I run in to aren't doing this often - it's "put up the site and updates some pages every few months" (or, blogging, which is often just text). For these, I recommend turning off write permissions to the whole of the WP system, and periodically turning it back on to do updates, then turning it off again. Yes, this doesn't cover 100% of exploit cases, but nothing does, and I've found this to go a moderately long way to reduce the impact of various exploit attempts. So, to answer the question, I would say "it depends". If the .net hosted version also by default allows for writeable media that is also executable, then there would be problems. However, I don't expect a .net-based system would allow you to get a ".aspx" file in a publicly accessible URL and have it just execute when accessed (unless there's some deployment mode that would allow for that?)
- pchp 8y agoPeachPie 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.
- kimdotcom 8y agoAlot 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.
- mgkimsal 8y ago"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.
- armandososa 8y agoWP 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.
- mgkimsal 8y agoif you're a developer, or have a development team, loads of options are even more extensible and versatile. and those options would all come with more flexible deployment, testing and scalability options. if you're not big in to development, you're reliant on a plethora of plugins, and you need to hope that the dozens of plugins you tie together know how to play nicely together. I'd run in to multiple situations where poorly built plugins for plugins were hacked on and then conflicted with other plugins - everyone pointed the finger at someone else. and then the standard support line from a couple vendors (these were plugins with paid support, btw) - "disable 100% of all your plugins, then enable them one by one to see where the problem is". Sweet. And when I tell people I inherited a wp site with just shy of 60 plugins, few people actually believe me. "I would never do that! I would never built anything with more than 4 (substitute with various numbers representing experience levels of people) plugins - that's all anyone ever needs!" When it works well, it works well. When it doesn't, it's a bloody nightmare.
- whatyoucantsay 8y agoA fractal abomination.
- Nelkins 8y agoCLR is really earning its name with this one.
- MrRubbish 8y agoWhat’s a cornrower?
- brian_herman 8y agoThis is great!
- skunkworker 8y agoThis seems like an interesting alternative direction like what HHVM was trying to accomplish.
- kreetx 8y agoPHP7 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.
- hbcondo714 8y agoTo push the MS stack further, integrate with Project Nami (Wordpress on SQL Server) https://projectnami.org https://projectnami.org
- pchp 8y agoThat's an awesome idea. Will do!