18 Comments

  1. Rob

    Wow. What a YAWN! Without the new Gutenberg editor, this release is a snore. A couple of new widgets (without using a plugin)…whoop-de-dooooo!

    Report

  2. Alex H

    Actually, what to expect seems to be a bunch of security patches, vulnerabilities, and problems. 5 security updates to 4.7 already.

    Skip 4.8 – how about taking some time to pour a new foundation for wordpress, call it 5.0. Do a general cleaning and get rid of all of the legacy stuff. Keep 4.8.x as a LTS and move forward with less problems.

    Report

    • Luglio7

      agree

      Report

    • Matthew

      That’s a great idea, especially if 4.7.x became a LTS release with at least 2 years of support while 5.0 launched with minimal requirements bumped to php 5.6, (with the promise of dropping it for php 7.1 within a year, to give plugins and hosting providers time to adapt), MariaDB 10.1.x and other current technologies. Damn, maybe they could even drop Apache…
      It would become safer, faster and easier to code for, while also forcing hundreds of hosting providers to embrace the current year instead of being stuck in the 2000s.

      Report

    • Rick Gregory

      Do a general cleaning and get rid of all of the legacy stuff.

      Yeah because huge rewrites are easy and never go wrong… Wait, they almost always do.

      I agree with you on the spirit of the comment but piecewise rewrites are almost always the best way to do these things, esp when you have a large base of users. Look at 4.7… 5 patches already and it was a minor release. Imagine what would happen with a large-scale rewrite.

      Report

  3. Danny Brown

    WordPress is kinda getting like my Android when it comes to updates these days. Like Rob and Alex mention, maybe skip such frequency and actually wait for a major push that really takes WordPress to a new level?

    Report

  4. Sallie Goetsch

    For the non-developer, the image, audio, and video widgets will be welcome. Adding an image to a text widget is pretty confusing for someone at the technical level of most of my clients.

    Report

    • Klaas

      Only there is a plugin (and has been in the repo for many years already) that does that job excellent.
      Since the “new” widget is based on that existing plugin, there really is nothing new under the sun!

      Report

  5. Dave Warfel

    While I agree in spirit with dropping legacy code, bumping minimum requirements, pushing hosts to advance their technology stacks, etc… I think we have to keep in mind just how many average, everyday, non-technical users WordPress has.

    When you’re dealing with this many users, sometimes even the smallest changes leave people in utter confusion. With so many variations amongst hosts, and so many non-technical users spread across a bunch of different platforms, a complete re-write of the codebase could cause widespread issues across hundreds of thousands of sites (if not millions).

    There’s no question that we all want more, bigger, better features. But can you really fault them for wanting to ship these couple of enhancements, instead of sitting on them for another couple of months? Like Sallie mentioned, for many users, the new media widgets are a big deal.

    At times, I also get frustrated with the pace at which WordPress introduces new features. I have to remind myself of its user base. And the vast sea of plugins that add 100x the functionality of WordPress itself. And the fact that all of it is available to me for free. And how I’ve been able to make an entire career for myself because of it.

    I appreciate the efforts of the 4.8 team, as well as everyone in the community who continues to move WordPress forward… regardless of its pace.

    Report

    • Klaas

      There’s no question that we all want more, bigger, better features.

      Actually we don’t.

      We want a safer, more modern and less bloated version of WordPress!

      Report

  6. Kristal

    UGH I just updated to 4.8 and I hate having the visual editor in the text widget! It automatically opens in the visual tab and messes up all of my html coding. Is there any way around this?

    Report

Comments are closed.

%d bloggers like this: