Rant Time: It’s time for Gutenberg to go.
As the title may suggest and as a WordPress.com blogger, I’ve given up using the Gutenberg editor for articles. Let’s explore exactly the reasons why.
Gutenberg, Block Editing and Calypso
One of the biggest selling points of Gutenberg (the latest WordPress editor, first released in 2018 and headed up by Matias Ventura) is its ability to have literal text blocks. Each paragraph is literally a square block that is separate from all other blocks. The blocks allow for movement with an arrow up and down. The point to this movement system is to allow for easily rearranging your articles. At least, that was the main selling point.
In reality, the blocks are more of a chore than a help. I’ll explain this more in a bit. When Gutenberg first launched, it replaced the previous editor, Calypso, which was released in 2015. Calypso loaded extremely fast (in under 3 seconds you’re editing). Typing in text was flawless and simply just “worked”. When Calypso first released, there were a number of performance issues, some bugs and it didn’t always work as expected. However, after several updates over the initial months, all of that was solved. The slowness and performance issues were completely gone.
Before Calypso arrived, there was the much older “black colored” editor that was simple text-only editor. Meaning, there was no ability to graphically place or drag-move objects. Instead, you had to use specific HTML tags to manually place images and use inline CSS to get things done. It was a hassle, but it worked for the time. The big update for WordPress was that Calypso would bring modern word processor features and a more WYSIWYG type experience to blogging. Calypso did that exceedingly well, but in an occasionally limited way.
Unfortunately, Calypso had a short lifespan of about 3 years. For whatever reason, the WordPress.org team decided that a new editor was in order and so the Gutenberg project was born.
Gutenberg Performance
The real problem with Gutenberg is its performance. Since its release, Gutenberg’s block-building system has immense overhead. Every time you type something into a block, the entire page and all blocks around it must react and shift to those changes. Performance is particularly bad if you’re typing into a block in the middle of an article with many other blocks. Not only does the editor have to readjust the page on every single keystroke entered, it has to do it both up and down. Because of this continual adjustment of the page, keystrokes can become lagged by up to 12 seconds behind the keyboard typing.
Where Calypso’s typing performance is instant and without lag, Gutenberg suffers incredible lag due to its poorly conceived block design. Gutenberg has only gotten worse over time. Unlike Wine which ages and gets better every day, Gutenberg gets worse every day. There are literally hundreds of bugs in the Gutenberg editor that have never been corrected, let alone the aforementioned severe performance issue.
Classic Editor
You might be asking, “What editor are you using?” Technically, I’m using Calypso inside of Gutenberg because there’s no other option than the antiquated “black editor”. When Gutenberg came about, they had to find a way to make old articles written in Calypso compatible with Gutenberg without having to convert every single article into the new Gutenberg block format. To do this, the Gutenberg team included Calypso in the block called the “Classic Editor” block. It’s effectively a full version of Calypso in a single block.
The Classic Block type is what I’m now using to type this and all new articles. I must also say that every character I type into the Classic Block is spot on in speed. No lags at all. Typing is instantaneous. However, with Gutenberg, typing words into a Gutenberg “paragraph” block can see text show up literally many seconds after I’ve typed it… sometimes more than 10 seconds later. I can literally sit and watch the cursor make each letter appear after I’ve stopped typing. It’s incredibly frustrating.
Few typists are 100% accurate 100% of the time. This means using the backspace key to remove a double tapped letter, add a missing letter or rewrite a portion of text is required. When you’re waiting on the editor to “catch up” with your typing, you can’t even know what errors you made until it finally shows up. It’s like watching paint dry. It’s incredibly frustrating and time wasting.
Editor Performance
Gutenberg’s performance has gotten progressively worse since 2018. By comparison, Calypso’s launch performance suffered when it was first released, taking 10-12 seconds to launch. The Calypso team managed to get that under control within 6 months and reduced the launch time to under 2 seconds. Literally, you could go from a new browser tab to editing an existing or brand new article in under 2 seconds. Gutenberg’s launch performance has remained consistent at ~10 seconds and has never wavered in the many years since it launched in 2018. And… that 10 seconds all for what? An editor with horrible performance?
Gutenberg launched with “okay” block performance years ago, but in the last 6 months, its performance level has significantly degraded. Literally, the Gutenberg paragraph block, the mainstay of the entire Gutenberg editor, is now almost completely unusable in far too many circumstances.
If you’re looking to type a single short paragraph article, you might be able to use Gutenberg. Typing an article like this one with a large number of paragraphs of reasonable length means slower and slower performance the longer the article gets, especially if you need to edit in the middle of the article. That’s not a problem when using the Classic Block as the article has only one block. It’s when there’s an ever growing number of blocks stacking up that Gutenberg gets ever slower and slower. Gutenberg is literally one of the most horrible editing experiences I’ve ever had as a WordPress blogger.
Gutenberg’s Developers
As a user of Gutenberg, I’ve attempted to create bugs for the Gutenberg team in hopes that they would not only be receptive to wanting these bug reports, but that they would be willing to fix them. Instead, what I got was an ever growing level of hostility with every bug reported… culminating in myself and one of the Gutenberg developers basically having words. He accused me of not taking the right path to report bugs… but what other path is there to report bugs if not in the official bug reporting system devoted to Gutenberg’s bugs? This one entirely baffled me. Talk about ungrateful.
Sure, I’m a WordPress.com user, but the WordPress.com team doesn’t accept bug reports for Gutenberg as they have nothing to do with Gutenberg’s development. They’ll help support the WordPress.com product itself, but they don’t take official bug reports for sub-product components. In fact, I’d been told by multiple WordPress.com support staffers to report my bugs directly into the Gutenberg project bug reporting system. That’s what I did. I explained that to the developer who suddenly became somewhat apologetic, but remained terse and condescending.
Let’s understand one thing. WordPress.com is a separate entity from the WordPress.org Gutenberg development team. The two have no direct relationship whatsoever, making this whole situation even more convoluted. It’s a situation that WordPress.com must workout with WordPress.org. As a blogger, it’s not my responsibility to become the “middle man” to communicate between these orgs.
Any development team with this level of hostility towards its end users needs to be reevaluated for its project values. Developers can’t develop in a bubble. They need the feedback from users to improve their product. Developers unwilling to accept this feedback need to be pulled from the project and, if their attitude does not improve, be jettisoned. Bad attitudes need to be culled from any development project. It will only serve to poison the end product… and nowhere is this more abundantly clear than in the Gutenberg editor. This editor is now literally falling apart at the seams.
WordPress.com is at a Crossroads
At this point, WordPress needs to make a choice. It’s clear, the Gutenberg editor can’t last. WordPress.com must make a new editor choice sooner rather than later. Gutenberg is on its last legs and needs to be ushered out of the door.
If that means re-wrappering the entire editor so that the Classic Block becomes the only and default block available, then so be it. I’d be perfectly happy if WordPress.com would make the Classic Block not only the default editor block type when entering a new editor, but the ONLY block type available. After all, everything that can be done with individual blocks in Gutenberg can be done in the Classic Block.
Then, refocus the Gutenberg development team’s efforts to improving ONLY the Classic Block. Have them drop the entirety of development for every other block type from that horrible Gutenberg editor product.
Blocks and Gutenberg
Let’s talk about Gutenberg’s design for a moment. The idea behind Gutenberg is noble, but ultimately its actual design is entirely misguided. Not only has Gutenberg failed to improve the editor in any substantial way, it has made text editing slower, more complex and difficult in an age when an editor should make blogging easier, faster and simpler. All of the things that should have improved over Calypso have actually failed to materialize in Gutenberg.
The multiple block interface doesn’t actually improve the blogging experience at all. Worse, the overhead of more and more blocks stacking to create an article makes the blogging experience progressively slower and less reliable. In fact, there are times when the editor becomes so unresponsive that it requires refreshing the entire editor page in the browser to recover. Simply, Gutenberg easily loses track of its blocks causing the editor to essentially crash internally.
None of this is a problem with the Classic Editor block because editing takes place in one single block. Because the Classic Editor is a single block, Gutenberg must only keep up with one thing, not potentially hundreds. For this reason, the Classic Editor is a much easier solution for WordPress.com. WordPress.com need only force the Classic Block as the primary editor in Gutenberg and hide all of the rest of Gutenberg’s garbage blocks that barely work. Done. The editor is now back to a functional state and bloggers can now move on with producing blog articles rather than fighting Gutenberg to get a single sentence written. Yes, Gutenberg is that bad.
Bad Design
Worse, however, is Gutenberg’s block design idea. I really don’t fully understand what the Gutenberg team was hoping to accomplish with this odd block design. Sure, it allows movement of the blocks easily, but it’s essentially a technical replacement for cut and paste. How hard is it really to select a paragraph of text, cut it and then paste it into a different location? In fact, cut and paste is actually easier, faster and simpler than trying to move a block. Block movement is up or down by one position at a time when clicked. If you need the block moved up by 10 paragraphs, then you’re clicking the up button 10 times. And, you might have to do this for 5 different paragraphs. That’s a lot of clicking. How does that much clicking save time or make blogging easier? Cut and paste is always four actions. Select the text, cut, click cursor to new location, paste. Cut and paste has none of this click-click-click-click-clickity-click BS. Of course, you can cut and paste a whole block, but that sort of defeats the purpose of building the up and down function for movement, doesn’t it?
Instead, I’ve actually found in practice that Gutenberg’s alleged more advanced “design” actually gets in the way of blogging. You’d think that with a brand new editor design, a developer would strive to bring something new and better to the table. Gutenberg fails. The whole cornerstone and supposed “benefit” of Gutenberg’s design is its blocks. The blocks are also its biggest failing. Once you realize the blocks are mostly a gimmick… a pointless and a slow gimmick at that, you then realize Calypso was a much better, more advanced editor overall, particularly after using a Classic Block to blog even just one article.
Change for Change’s Sake
Here’s a problem that’s plagued the software industry for years, but in more recent times has become a big, big problem. With the rush to add new features, no one stops to review the changes for functionality. Product managers are entirely blinded by their job requirement to deliver something new all of the time. However, new isn’t always better and Gutenberg proves this one out in droves. Simply because someone believes a product can be better doesn’t mean that the software architects are smart or creative enough to craft that reality.
We must all accept that creating new things sometimes works and sometimes fails. More than that, we need to recognize a failure BEFORE we proceed down the path of creation. Part of that is in the “Proof of Concept” phase. This is the time when you build a mini-version of a concept to prove out its worth. It is typically at the “Proof of Concept” stage where we can identify success or failure.
Unfortunately, it seems that many companies blow right past the proof-of-concept stage and jump from on-paper design into full-bore development efforts. Without a proper design review by at least some stakeholders, there’s no way to know if the end result will be functional, useful or indeed solve any problems. This is exactly where Gutenberg sits.
While I can’t definitively state that the Gutenberg team blew past the proof-of-concept stage, it certainly seems that they did. Anyone reviewing Gutenberg’s blocks idea could have asked one simple question, “How exactly are blocks better than cut and paste?” The answer here is the key. Unfortunately, the actual answer to this question likely would have been political double-speak which doesn’t answer the question or it might end up being a bunch of statistical developer garbage not proving anything. The real answer is that this block system idea doesn’t actually improve blogging. In fact, it weighs down the blogging experience tremendously.
Instead of spending time writing, which is what we bloggers do (and actually want to do), we now spend more time playing Legos with the editor to determine which block fits where. As a blogger, an editor should work for us, not against us. Spending 1/3 of our time managing editor blocks means the loss of 1/3 of our time we could have been writing. Less time writing means less articles written.
Because blogging is about publishing information, speed is of utmost importance. Instead of fumbling around in clumsy blocks, we should spend our time formulating our thoughts and putting them down onto the page. For this reason, Gutenberg gets in our way, not out of our way.
At a Crossroads — Part II
Circling back around, we can now see exactly WHY WordPress.com is at a crossroads. The managers at WordPress.com need to ask this simple question, “What makes our bloggers happy?” The answer to this question is, “A better and faster editor.”
Are Gutenberg’s failings making bloggers happy? No. Since the answer to this question is “No”, WordPress.com managers need to realize there’s a problem afoot… a problem which can be solved. Nothing requires the WordPress.com platform to use Gutenberg… or at least the block portions of it. Because there exists a solution in the Classic Block, it would be simple to launch Gutenberg directly into a locked-in version of the Classic Block and not allow any further blocks to be created… essentially dumping the vast majority of Gutenberg.
This change reverts the editor back to Calypso and effectively does away with Gutenberg almost entirely. Though, this is a stop-gap measure. Eventually, the WordPress.com managers will need to remove Gutenberg entirely from the WordPress.com platform and replace it with a suitably faster and more streamlined editor, perhaps based on a better, updated version of Calypso. It’s time for this change. Why?
If the Gutenberg team cannot get a handle on crafting an editor that works after 3 years, then Gutenberg needs to be removed and replaced with an editor team actually willing to improve the blogging experience. WordPress.com needs to be able to justify its sales offerings, but it’s exceedingly difficult when you have what should be the cornerstone of the platform, the editor, working against you. This makes it exceedingly difficult for new would-be buyers to literally spend money for WordPress.com platform. Paying for an editor that barely works is insane. WordPress.com managers can’t be so blind as to not see this effect?
The bottom line is, how do you justify replacing an editor with an under 2 second launch time with an editor that now has a 10-20 second launch time? That’s taking steps backwards. How do you justify an editor that lags behind the keyboard typing by up to 12 seconds when the previous editor had no lag at all? Again, steps backwards. Isn’t the point in introducing new features to make a product better, faster and easier? Someone, somewhere must recognize this failure in Gutenberg besides me!! Honestly, it’s in the name of the product “WordPress”. How can we “press words” without an editor that “just works”?
WordPress.com, hear me, it’s time to make a change for the better. Dumping Gutenberg from the WordPress.com platform is your best hope for a brighter future at WordPress.com. As for the WordPress.org team, let them waddle in their own filth. If they want to drag that Gutenberg trash forward, that’s on them.
↩︎
Rant Time: Google’s Lie
I’ve already written an article or two about YouTube giving content creators the finger. I didn’t really put that information into this article’s context so that everyone can really understand what’s actually going on at YouTube, with the FTC and with Google. Let’s explore.
Lies and Fiction
Google has asserted and maintained, since at least 2000 when COPPA came into effect, that it didn’t allow children under age 13 on its platforms. Well, Google was caught with its proverbial pants down and suffered a $170 million fine at the hand of the FTC based on COPPA. Clearly, Google lied. To maintain that lie, it has had to do a number of things:
- For YouTube content creators, YouTube has hidden its metrics for anyone under the age of 13 from viewer stats on YouTube. What that means to creators is that the viewer metrics you see on your stats page is completely inaccurate for those under the age of 13. If Google had disclosed the under 13 age group of stats on this page, Google’s lie would have unraveled far faster than it did. For Google to maintain its lie, it had to hide any possible trail that could lead to uncovering this lie.
- For other Google platforms (Stadia, Chromebook, Android phones, etc), they likely also kept these statistics secret for the same reasons. Disclosure that the 12 and under age group existed on Google meant disclosing to the FTC that they had lied about this age group using its services all along.
- For Android phones, we’ll let’s just say that many a kid 12 and under have owned Android phones. Parents have bought them and handed them over to their children. For the FTC to remain so oblivious to this fact for years is a testament to how badly operated this portion of the government is.
- Google / YouTube had to instruct engineers to design software systems around this “we don’t display under age 13 metrics” lie.
Anyway, so lie Google did. They lied from 2000 all of the way to 2019. That’s almost 20 years of lying to the government… and to the public.
YouTube’s Lie
Considering that even just one COPPA infraction found to be “valid” could leave a YouTube channel owner destitute. After all, Google’s fine was $170 million. Because a single violation could cost a whopping $42,530, it’s a major risk simply to maintain a YouTube channel.
Because of the problem of Google perpetuating its lie about 12 and under for so long, this lie has become ingrained in Google’s corporate culture (and software systems). What this means is that for Google to maintain this lie, it had to direct its engineers to write software to avoid showing any statistic information anywhere that could disclose to anyone that Google allows 12 and under onto any of its platforms, let alone YouTube.
This also means that YouTube content creators are entirely left in the dark when it comes to viewer statistics of ages 12 and under. Because Google had intended to continue maintaining its “we don’t serve 12 and under here” lie, it meant that its systems were designed around this lie. This meant that any place where 12 and under could have been disclosed, this data was specifically culled and redacted from view. No one, specifically not YouTube content creators, could see viewer metrics for anyone 12 and under. By intentionally redacting this information from its statistics interfaces, no one could see that 12 and under were actually viewing YouTube videos or even buying products. As a creator, you really have no idea how many 12 and under viewers you have. The FTC will have access into YouTube’s systems to see this information, even if you as a content creator do not.
This means that content creators are actually in the dark for this viewer age group. There’s no way to really know if this age group is being accurately counted. Actually, Google is likely collecting this information, but they’re simply not disclosing it over public interfaces. Though, to be fully safe and to fully protect Google’s lie, they might have been purging this data more often than 13 and older data. If they don’t have the data on the system, they can’t be easily caught with it. Still, that didn’t help when Google finally did get caught and were fined $170 million.
Unfortunately, because Google’s systems were intentionally designed around a lie and because they are now already in place, undoing that intentional design lie could be a challenge for Google. They’ve had 19 years worth of engineering effort build code upon code avoiding disclosure of 12 and under using Google’s platforms. Undoing 19 years of coding might be a problem.
Swinging back around to that huge fine, this leaves YouTube in a quandary. It means that content creators have no way to know if the metrics that are being served to content creators are in any way accurate. After all, Google has been maintaining this lie for 19 years. They’ve built and maintained their systems around this lie. But now, Google must undo 19 years of lies built into their systems to allow content creators to see what we already knew… that 12 and under have been using the platform probably since 2000.
For content creators, you need to think twice when considering setting up a channel on YouTube. It doesn’t matter what your content is. If that content attracts children under 13, you’re at risk. The only type of channel content that cannot at all be seen as “for kids” is content that kids would never watch. There is really only a handful of content type I can name that wouldn’t appeal to children (not an exhaustive list):
- Legal advice from lawyers
- Court room video
- Horror programs
- Political programs
- Frank sex topics
It would probably be easier to state those types of programs that do appeal to children:
- Pretty much everything else
What that means is topics like music videos, video game footage, cartoons, pet videos, singing competitions, beauty channels, fashion channels, technology channels and toy reviews could appeal to children… and the list goes on. You name it and pretty much every other content type has the possibility of attracting children 12 and under… some content more than others. There’s literally very little that a child 12 and under might not consider watching.
The thing is, when someone decides to create a channel on YouTube, you must now consider if the content you intend to create might appeal to children 12 and under. If it’s generalized information without the use of explicit information, children could potentially tune in. Though, YouTube doesn’t allow true adult content on its platform.
Google’s lie has really put would-be channel creators into a huge bind with YouTube, plummeting the value of YouTube as a platform. For monetization, not only is there now the 1,000 subscriber hurdle you must get past and you must also have 14,000 views in a month, but now you must also be cognizant of the audience your content might attract. Even seemingly child-unfriendly content might draw in children unintentionally. If you interview the wrong person on your channel, you might find that you now have a huge child audience. Operating a YouTube Channel is a huge risk.
YouTube’s Value as a Platform
With this recent Google change, compounded by Google’s lie, the value of YouTube as a video sharing platform has significantly dropped. Not only did Google drop a bomb on its content creators, it has lied to not only the government, but to the public for years. With the FTC’s hand watching what you’re doing on YouTube, YouTube really IS moving towards “big government watching” as described in George Orwell’s book 1984. Why Google would allow such a deep level of governmental interference over its platform is a major problem, not just for Google, but for the computer industry as a whole. It’s incredibly chilling.
$42,530 per COPPA violation is not just small change you can pull out of your pocket. That’s significant bank. So much bank, in fact, that a single violation could bankrupt nearly any less than 100,000 subscriber channel on YouTube.
Not only do you have to overcome YouTube’s silly monetization hurdles, you must attempt to stay far away from the COPPA hurdle that YouTube has now foisted on you.
Google’s Mistake
Google did have a way to rectify and remediate this situation early. It’s called honesty. They could have simply fixed their platform to accurately protect and steer 12 and under away from its properties where they don’t belong. It could have stated that it did (and does) allow 12 and under to sign up.
If Google had simply been honest about 12 and under and allowed 12 and under to sign up, Google could have set up the correct processes from the beginning that would have allowed not only Google to become COPPA compliant, but by extension allow YouTube creators to remain compliant through Google’s tools. Google should have always remained in the business of protecting its creators from governmental interference. Yet, here we are.
In fact, the COPPA legislation allows for parental permission and consent and it’s not actually that hard to set up, particularly for a large organization like Google. For Google, in fact, it already has mechanisms it could leverage to attempt to obtain verifiable parental consent. If Google had chosen to setup and maintain a 12 and under verifiable parental consent program all along, YouTube content creators could have been left off of the hook. Instead, YouTube has given content creators the finger.
If YouTube content creators must share in Google’s lack of COPPA compliance, then content creators should equally share in a Google created parental consent system. Parental consent isn’t that hard to implement. Google could have spent its time building such a system instead of lying.
Trust and Lies
When companies as big as Google participate in lies of this magnitude, you should seriously question any business you do with such a company. Companies are supposed to be ethically bound to do the right thing. When companies don’t do the right ethical thing and perpetuate lies for years, everyone must consider how much you trust that company.
What else are they lying about? It’s difficult to trust someone who lies. Why is it any different when a company chooses to lie?
When that lie can cost you $42,530 per violation, that’s what comes out of lying. Google not only didn’t protect its content creators, it perpetuated a lie that has now left its content creators hanging out to dry.
This is why YouTube as a content creator platform is about as worthless as it can possibly be… not only for the lie and COPPA, but also the monetization clampdown from 2017-2018. Every year has brought another downside to YouTube and for 2019, it’s Google’s lie.
For large creators who have an entrenched large audience and who are making ad revenue bank from their audience (at least for the moment), I understand the dilemma to ditch YouTube. But, for those content creators who make maybe $5 a month, is it worth that $5 a month to risk $42,530 every time you upload a video? Worse, the FTC can go back through your back video catalog and fine you for every single video they find! That’s a lot of $42,530 fines, potentially at least one per video. Now that’s risky!
Solutions
There are solutions. The biggest solution, ditch YouTube for other video platforms such as Facebook, SnapChat, Vimeo or DailyMotion. If you’re live streaming, there’s YouNow, Twitch and Mixer. You’re not beholden to YouTube to gain an audience and following. In fact, with the huge black COPPA cloud now permanently hanging over YouTube, it’s only a matter of time before the FTC starts its tirade and cements what I’m saying here in this article. For small and medium sized creators, particularly brand new creators, it’s officially time to give YouTube the (just as Google has given us the
). It’s long past time to ditch YouTube and to find an alternative video sharing platform. You might as well make that one a 2020 New Year’s resolution. Let’s all agree that YouTube is officially dead and move on.
Just be sure to read the fine print of whatever service you are considering using. For example, Twitch’s terms and conditions are very explicit with regards to age… no one under 13 is permitted on Twitch. If only Google had been able to actually maintain that reality instead of lying about it for nearly 20 years.
↩︎
2 comments