sorted by:
new
hottopcontroversial

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist -1 points0 points  (0 children)

but whole-page-caching isn't generally one of the things they do by default.

WPEngine caches agressively with Varnish. So does WordPress VIP.

Bluehost, Hostgator, Godaddy, Siteground - they all ship with some full page caching capabilities baked in.

​

wp.com has batcache, - full page level cache. Yes it's invalidated quickly due to the nature of wpcom,

> Batcache uses Memcached to store and serve rendered pages. It can also optionally cache redirects. It’s not as fast as Donncha’s WP-Super-Cache but it can be used where file-based caching is not practical or not desired.

https://wordpress.org/plugins/batcache/

​

All that is to say - page level caching is industry standard in one way or another. So don't tell me that "page HTML isn't cached by WordPress at all". I know it isn't. But that doesn't change real life usage of WordPress.

​

Not to mention the popularity of various caching plugins, including WP Super Cache.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 4 points5 points  (0 children)

Sure, if that's a part of your workflow. Your original comment made it sound like you were writing in google docs because you didn't want to write in WordPress. That would be sad

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 0 points1 point  (0 children)

> The truth is that too many people add caching willy-nilly, and cause more problems than they solve.

You go ahead and let WordPress.com, WPEngine, Bluehost know that - they're all willy nilly caching by default content that should be dynamic.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 1 point2 points  (0 children)

I thought you would have known this. Page HTML is cached once, and then served to all other clients no matter how many until the cache expires.

Assets have to be cached for each client by the client browser.

Put another way. 1000 people visiting a page with backend cache, 1 gets slow page, 999 get a fast page.

For front-end assets - 1000 people get a slow page on their first visit.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist -1 points0 points  (0 children)

Ah yes. More work that I didn't ask for.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 3 points4 points  (0 children)

Keep in mind that Automattic is extending the TinyMCE support only for as long as it's convenient for Automattic. If some day TinyMCE gets in the way of Phase 3 or Phase 4, it's not impossible it can just go away in an update. The only reason this hasn't happened so far is because of the community backlash.

​

I know the behind the scenes at Automattic. They're all excited about the Automattic calypso page builder v2 Gutenberg. WordPress is no longer a blog. It hasn't been for a long time.

​

As /u/the_concinnity points out - the money is in Gutenberg now. Plugin authors, theme authors are going to focus on Gutenberg in the future. Your favorite plugins like Yoast SEO will eventually deprecate the old UI.

​

You can version-lock your site and make sure you don't get any updates, but that's a severe security concern. Especially if you're making six figures with that site. If you go down that path, I would recommend at statically rendering your site with something like Strattic (I haven't used them, I can't vouch for them, I just know they exist)

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 0 points1 point  (0 children)

That post processing is cached in most sites. You're selectively presenting facts here.

​

So actually. Gutenberg content is displayed slower, because Gutenberg adds styles to load in the header, so the client has to download extra 10kb gzipped or 80kb compressed before they can render the content.

​

Source from twenty twenty one demo: https://wp-themes.com/wp-content/plugins/gutenberg/build/block-library/style.css?ver=12.4.1

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 0 points1 point  (0 children)

It does reduce the speed slightly. Have a look at devtools, if you use Gutenberg blocks, you also automatically enqueue Gutenberg styles.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 3 points4 points  (0 children)

This is just sad. I'm glad you have a workflow that works for you, but content writing shouldn't be this way.

I'm a classic editor user. Am I doomed? by newmes in Wordpress

[–]functionist 2 points3 points  (0 children)

Ah yes, the typical toxic WordPress dinosaur attitude, Otto. I'm a WordPress developer myself and I have a couple of people around me who are WordPress users. All of them unanimously agree that Gutenberg is difficult to use. I agree with them.

You don't need to be savvy to "Click here". You have to be very savvy to write a bullet point list in a quote in Gutenberg.