Why Wordpress?
21–30 of 90 posts
Re: Why Wordpress?
#22I love wordpress, but I don't love PHP, updates, security flaws, or hosting. I haven't done it yet, but I'm considering using the Simply Static plugin[0] to migrate to generated static pages from my wordpress instance, which sidesteps all of those problems. [0]: https://wordpress.org/plugins/simply-static/
https://www.netlify.com/blog/2016/05/02/top-ten-static-websi...
Roots is mentioned, but the team has since developed Spike which is built on a more modern stack:
Re: Why Wordpress?
#23I love wordpress, but I don't love PHP, updates, security flaws, or hosting. I haven't done it yet, but I'm considering using the Simply Static plugin[0] to migrate to generated static pages from my wordpress instance, which sidesteps all of those problems. [0]: https://wordpress.org/plugins/simply-static/
I would also look into the myriad of static site generators that are probably much faster than the WP static site plugin and use modern tools and libraries. https://www.netlify.com/blog/2016/05/02/top-ten-static-websi... Roots is mentioned, but the team has since developed Spike which is built on a more modern stack: https://github.com/static-dev/spike https://www.spike.cf/
Re: Why Wordpress?
#24Earlier quoted context omitted.
That's why wpengine is such an excellent choice for a lot of users. On the topic of PravlageTiem, the issue of WordPress' security flaws seems to be incidental to his attempt to accuse Sam Altman of censorship. If I had to guess, that would be why the comment is dead. I wouldn't call that sarcasm.
Even with WPengine, security issues are a very common thing. WPengine can keep some things up to date, but plugins and themes are exploited often. Worse, an enterprise deployment at scale is a huge nightmare. Exploiting WP sites on HackerOne can be a very profitable business for many.
Re: Why Wordpress?
#251 - use a C panel "one click" install of the CMS from your web host
2 - start looking for plugins to give you the functionality you want
3 - install said plugins without sand boxing them or even testing them for vulnerabilities.
4 - end up getting hacked and then wonder what happened
It's true that for the most part the WP core is pretty solid, but its the billions of sketchy plugins that people use that create vulnerabilities and allows their sited to get hacked.
Re: Why Wordpress?
#26Because people who don't actually know how to build websites are fooled into thinking they have a tool that will fill that knowledge gap, despite the security implications that they are oblivious to.
It's the first choice among a huge number of web devs though, which seems contrary to it being that the person deploying it doesn't know better.
Re: Why Wordpress?
#27Re: Why Wordpress?
#28So they pick wordpress: 1 click install in cpanel, no html, css, js, php knowledge whatsoever, pick a free theme from millions of themes, pick plugins from millions free ones, done. Maybe a bit of google to personalize it but that's it.
What do you offer devs who can make a quick 50 bucks in afternoon installing a plugin/theme, or even 100 for a quick website with admin panel and all that easy stuff?
There is a market for everyone and cms's will live one way or another. The simple & free stuff will always be more successful.