Can we just throw wordpress in the trash instead already?
It sucks at everything. It's not a good CMS, its plugins are awful, PHP is a dumpster fire, every web developer hates it, etc.
This is also pointless as a tech demo.
WordPress Playground: A WordPress that runs entirely in the browser
61–70 of 221 posts
Re: WordPress Playground: A WordPress that runs entirely in the browser
#62WordPress was where I got my start, a while ago now. From poking around with PHP files, to building my own things, to Django, and on. It would have been inconceivable back then (mid noughties) that the whole thing could be done client side. The Web has come on a long way. These days I tend to hate WordPress with a passion. Occasionally I will be asked to peek at some technical problem with a WordPress installation an…
>these days most of which seem to be trying to upsell via ads in the admin.
This is my biggest issue with wordpress.
So much that should be in core is left to plugins, some of which are semi-official like jetpack, that it feels a lot more like "open core" than "open source".
Re: WordPress Playground: A WordPress that runs entirely in the browser
#63Its cool and I get it, but how is this useful other than good marketing? If an app's code is run on a device, any rooted device could just modify its memory and do whatever it wants. Just ask a game developer about the infinite anti-cheating war that they deal with.
Could you expand? I don't follow.
WordPress is open source, you can already download it and do whatever you want.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#64When will i have useState in PHP ?
Just use `$_SESSION`.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#65I'm curious as to how useful this will be. Tying it to SQLite makes it portable, but abstracting it so that it can be used with any db would be far more powerful. Why? Because the SQLite implementation is enough to get it working in the browser, but it does not make WordPress 100% SQLite compatible. For example, a WordPress site built on MySQL can't be migrated into an SQLite powered WordPress using a common migration plugin. I know, because I tried.
I installed WordPress in a standard PHP environment, and use the db.php dropin and SQLite compatibility plugin, and actually got WordPress installed on the file system. It works, but when I tried to migrate using all-in-one-wp-migration, it failed.
A neat concept with niche use, but not a panacea for agencies and other devs who need an extensive playground, even if it's self hosted on a persistent PHP server.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#66As a side note, I wonder if WP will still be in demand after all these chatbots come into daily usage
Re: WordPress Playground: A WordPress that runs entirely in the browser
#67WordPress was where I got my start, a while ago now. From poking around with PHP files, to building my own things, to Django, and on. It would have been inconceivable back then (mid noughties) that the whole thing could be done client side. The Web has come on a long way. These days I tend to hate WordPress with a passion. Occasionally I will be asked to peek at some technical problem with a WordPress installation an…
What no-code alternative would you recommend for pro web designers?
I would recommend Kirby, it is not all there, but is getting there.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#68WordPress is an utter crap in terms of DB design and code. Most plugins are even worse and the whole thing is a total mess. Yet, if you have a client needing this and that you can have them started really quick with WordPress. Need an e-commerce? There are plugins for that. Need an event management? There are plugins. Need an obscure app for truck drivers to share their CVs and communicate with clients? There is prob…
The backend is a terrible mess. But most of the time WP sites are served as cached static assets to the end user so you can still get the load times pretty good (despite the dumpster of a backend/DB).
When they are content sites, yes. When there is ecommerce and other dynamic stuff - not so much. I'm often optimizing WP sites after the arsenal of the typical developer - caching, redis object caching, etc - has been wiped off. The db structure and poorly optimized queries are a real pain.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#69I wonder if this could be useful for penetration testing, considering the ease of setting up different plugin combinations on different PHP and Wordpress versions? Or stack used to run it is way more different from real one?
Re: WordPress Playground: A WordPress that runs entirely in the browser
#70Earlier quoted context omitted.
I have thought about making a plugin. The plugin documentation/architecture is a bit gnarly (at least from what I remember). That being said, I feel like most WordPress plugins are awful. I've sometimes wondered if I could make a better version of X plugin, but I fear I'm missing something - like providing customer support or covering every version of WP.
The customer support and testing are key challenges. You have to be ready to help people with things that aren't even your fault if you don't want your rating on the marketplace(s) to go to shit. Plus you'll need to do lots of sales/ads/marketing to get your zero-ratings zero-downloads plugin off the ground, no matter how good it is. Writing a decent and useful plugin is helpful (almost wrote "necessary", but it's ac…
> You have to be ready to help people with things that aren't even your fault if you don't want your rating on the marketplace(s) to go to shit.
Ah, that makes a lot of sense. Now I /definitely/ don't want to make a plugin.