weo3dev

Actually, @grigory-volochiy since you’re being a smartypants – his answer *is* cross browser and…. let me google this for you… one second (literally):

Read:
https://www.safari-is-the-new-ie.com/

Read some more:
https://dev.to/nektro/safari-is-the-new-internet-explorer-1df0

And read from literally four months ago:

Fuck Safari, for real.
by inwebdev

So yes, Virginia, it looks like Safari is the new IE version that we love to hate because it is, quite frankly, deserving of the hate.

Any more unhelpful remarks?

Got it. Fair enough and thanks for the heads up!

Safari is like the new IE.

Ugh. lulz. I guess we’ll always have one….

@otto42 – do you know or believe that Safari is having issues due to how it compiles and renders to the DOM? Honestly I hardly ever touch Safari, but I might pull it out, put it in dev mode and see what I can see. Kinda stinks that the experience with it seems so different than what can be had on Firefox and/or Chrome….

Holy crap! I have not had that experience at all! I spent more time being lost, more than anything….

I have a couple of ideas of how we can track this down, because locally I use Lando and Docker significantly for WP and other dev and unfortunately one of those has a reputation of using large amounts of CPU for no good reason. I am talking 120% and more. My only fix so far on that I’ll share at the end of this response.

For machine reference – I’m using a late 2012 MBP – 2.3 GHz Intel Core i7, 16 GB 1600 MHz DDR3. This is the “newest” model of mac I’ll prob ever use because it’s the last model that didn’t hard solder the ram to the motherboard. I have an 500GB SSD for my main drive.

Thoughts:

1) In terms of machine specs – 8G of ram should be more than enough for you. I could be wrong. However, it is scary to think if we would need more just to use a CMS.

2) Have you opened up the console and checked to see if there’s a js script hanging? Normally, php will just silent fail or error out and keep trudging. JS though, can seriously stall entire processes. I am curious if there’s an issue lurking somewhere in your plugins that may unfortunately be hanging up.

3) Have you used Activity Monitor? It’s in your Utilities folder inside Applications .. just click anywhere on the desktop to put yourself in Finder and then use keyboard shortcut “command + shift + g” to pull up “Go to Folder” modal. in that, type “/Applications/Utilities” and you should see Activity Monitor up top. Open it, and click the CPU% heading so the list of applications running is sorted from most CPU used to least, and see if anything other than Safari is killing your CPU.

4) If in 3) above it is NOT Safari, you can use this little helper app that has saved me a ton of headache. It is NOT a long term fix. It is a bandage. But it keeps you going with less angst. It is called CPU Throttle.

Just download from here: https://www.willnolan.com/cputhrottle/cputhrottle.html – under Source (not the Binary). Put it in top level of your drive – as a sibling of Applications. And then, in terminal, you can use the command he shows to clamp an application down. Again, this is just a bandage, not a solution.

5) If in 2) above, you see any warnings or especially, any errors that are js related, then I would imagine that is the issue. Then, it would be a matter of discovering just which plugin is at fault.

Hope that helps.

Cool story bro.

Gutenberg = future. Classic Editor = good for 2 years. Neat.

You do realize your options that are still php-based in 2 years that are enterprise-level is either Drupal or Joomla. Drupal8 is a rebuild from D7 and prior – so at least you can get it in now while everyone is still helping everyone, and Joomla? Um. Ok.

Or maybe your agency would be happy with Wix? Weebly? Ghost? Sure yeah, you end up paying more in the long run, but again, that’s your agency’s call.

Recognize that what WP has done is open themselves up to an entire new class of developers – JavaScript devs. And as I am one, and all my core dev friends are also JS centric, I guarantee you there will be fast movement in the WP community when it comes to integrating future-facing sites and applications.

I hope you’re able to update and integrate sooner than later, because frankly, ll of my dev friends will be able to offer services just fine that will fill the gaps agencies such as yours will leave, when you refuse to update.

Good luck.

ps all our clients are moving to Gutenberg. We’re already building custom blocks and plugins for our framework. It works. We get paid. Clients are happy.

• This reply was modified 5 years, 6 months ago by weo3dev. Reason: last note

Cool. Very helpful response and rating for the wordpress team.
*sarcastic hat off*

At every point in the past two years, WP has consistently communicated that at no point will anyone be FORCED to use Gutenberg until 2022. That is still two years from now.

Read this:

Do I have to switch to Gutenberg when WordPress 5.0 is released?
Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.

From: https://gutenbergtimes.com/mullenweg-on-gutenberg-roll-out-plan/

If you hate Gutenberg, no hard feelings. Download and install Classic Editor plugin https://www.ads-software.com/plugins/classic-editor/ and you can edit and manage your WP site in the archaic past to your heart’s content.

Until 2022.

Maarten – it is an option, and will continue to be an option, until 2022.

From: https://gutenbergtimes.com/mullenweg-on-gutenberg-roll-out-plan/

Do I have to switch to Gutenberg when WordPress 5.0 is released?
Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.

My best advice to you is to download and install the Classic Editor and continue to manage your websites accordingly.

Hey Gina ~ WordPress specifically has stated multiple times that you have the option to remain with the Classic Editor if you have a website that just doesnt seem to be able to handle the new method of Gutenberg.

Do I have to switch to Gutenberg when WordPress 5.0 is released?
Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.

From https://gutenbergtimes.com/mullenweg-on-gutenberg-roll-out-plan/

Gutenberg is not, and will not ever be backwards-compatible with Classic. WP is taking a completely new step in the direction for the survival and growth of its software. Gutenberg is meant to be the tool to be used for probably the next decade.

Once upon a time, back in 2003 when it first began, WP was literally just a blog site manager. It wasn’t until 2008 that it really became useful for large enterprise companies. And WP has used, essentially, that same codebase/approach since at least 2008. That’s over ten years of the original codebase doing an amazing job (obviously with significant updates and features added).

Gutenberg is a rebuild, which is why, moving forward, you can choose and be able to manage your site as you have been able to, but only by using the Classic Editor plugin.

I hope that helps clarify why “backwards-compatible” doesnt apply to this situation.

Hi Jan, sorry to hear about this.

The decision to change the editor seems to be based on a number of factors. Please note – I am not on the WordPress team or board or anything. Just a developer that uses and builds for it daily.

Per your comments:
WP was stuck, literally, in a sort of time-capsule compared to other website creation/management tools. In order for it to move forward and allow companies and people who wanted to use things like React or Angular or even just build a super custom thing on top of the wordpress ecosystem – WP had to change their entire codebase to allow that to happen.

Yes it appears a step back. Please understand this is like Public Version 1.0 of it being out there. If you used WordPress when it first came out, you would recall that it wasn’t very useful in the beginning, except just for blogs. But now? Now it’s used all over the world by thousands of companies and people for amazing sites of all kinds.

Gutenberg is a step for the next 10 years of the future of WordPress. I am fully confident it will only get better with time, because honestly, that is how my experience with WP has been since 2003. It gets better.

If I can help in any other way, just hit me back here. I’ll try to respond within 36 hours.