Don’t fix what’s not broken

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

  • Seems like that’s the goal. Wondering what kind of conflicts of interest on the WP team that led to something just being shoved own our throats.

    • This reply was modified 6 years, 2 months ago by Andrew Nevins. Reason: Expletive removed

    Of course not. For many of us already using WordPress, it can be easy to forget the learning curve that exists for people being introduced to it for the first time. The end goal is to make things like customizing the look, adding shortcodes, and editing widgets and menus easier for first-time users by using blocks to make the editing interface consistent across the whole platform. That is still in progress starting with the block editor for creating post and pages that came out in WordPress 5.0.

    “… it can be easy to forget the learning curve that exists for people being introduced to it for the first time”

    I remember a long time ago when MSFT tried that with .NET. A big, bloated piece of crap with unbelievably large runtime layers that replaced the ‘classic’ VB6. Didn’t work well for them. I don’t believe they really recovered from it fully, all in the name of ‘bigger and better’ (allegedly) and ‘innovation’.

    I said last year that WP was making the same mistake. No one learns from the past.

    I guess we’ll see what happens, huh?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Don’t fix what’s not broken’ is closed to new replies.