Absolutely hate it from developer POV

  • gsc89

    (@gsc89)


    3 years ago

    I can’t put into words how much time I have wasted recently trying to develop or rather even just make small tweaks to existing custom blocks for this editor its an absolute nightmare to develop for when your coming from a position of 10+ years of PHP experience and suddenly to make editor blocks for the editor forced upon your chosen CMS you have to suddenly learn to wrestle with some of the worst looking syntax known to man….

    This is the worst thing to happen to WordPress, I knew it was going to be bad back in 2018 and time has only proved how right all of its detractors were.

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi there. There is definitely a steep learning curve to development for and around the block editor, especially if JavaScript is not your primary development language. It’s hard to be a newbie again and learn something new. Many people have a love/hate relationship with JavaScript.

    Are there any specific problems, you are setting out to solve? A few developers who have gone before you, are available at the Gutenberg Developer Hours, on March 8th (tomorrow) and on March 22. Bring your problems, your questions, and your code, and discuss them with the expert panelists. There are more developer-centric events planned on the meetup group.

    Also, you might appreciate Ryan Welcher’s TwitchStream recording on YouTube with live coding session building blocks and other block editor related topics. I learned quite a bit from them.

    Thread Starter gsc89

    (@gsc89)

    The main problem developing in this new React JS based block system is the lack of usable feedback …

    You get an error in your block … no actual debug info is usable you get an absolutely massive meaningless JS error in console that tells you ZERO about the actual problem you have so your left to try and work out what in your JS is broken.

    At present im stuck in an “Attempt Block Recovery” loop on all blocks I’m developing where every time I load the editor I have to recover all blocks … the edit / save HTML match up with one another in code but still every editor reload requires me to recover all the blocks with zero usable feedback on “what” the actual issue is.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Absolutely hate it from developer POV’ is closed to new replies.