Non-Cron method removal: don’t try to be smarter than your users!

  • Resolved mariankechlibar

    (@mariankechlibar)


    6 years ago

    Hi, I just read your official explanation why you removed the non-cron (immediate sending) method. Citing the relevant passage:

    Just want to update you that we have removed this option to just reduce the load from your server while publishing a post. So that, you can publish your post without any delay and your contacts can be notified in the background.

    This is such a bad decision! Why are you trying to second-guess someone else’s workflow? Have you asked anyone if they feel bothered by the pause needed to send e-mail notifications immediately?

    Well, I was ready to tolerate a 30 second pause for sending of e-mails when I knew that the simpler method just worked.

    By forcing me into your half-baked, buggy cron method, you wasted at least an hour of my time already.

    Please reconsider this decision. Removing options from your users because you find them suboptimal is second-guessing other people and would m make me personally unhappy even if your new method was spotless. Given that it does not even work as of 4.0.2, I am outright furious.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter mariankechlibar

    (@mariankechlibar)

    To add something.

    I used to develop software in C/C++/Java for almost 15 years.

    This is what happens if you release untested alpha version into the wild.

    Please introduce some “alpha”-“beta”-“RC” cycle into your development cycle, with internal AND external volunteers acting as testers/evaluators before you push your major code changes onto the rest of the planet.

    Hi,

    Please refer this article why we removed send emails immediately?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Non-Cron method removal: don’t try to be smarter than your users!’ is closed to new replies.