Licensing model change

Kevin Miller kevin at livecode.com
Wed Sep 1 04:37:26 EDT 2021


Thanks Curry, we appreciate the feedback. Hope you feel better soon!

Kind regards,

Kevin

Kevin Miller ~ kevin at livecode.com ~ http://www.livecode.com/
LiveCode: Develop Yourself

On 31/08/2021, 22:28, "use-livecode on behalf of Curry Kenworthy via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:


    Kevin:

     > After 8 years with an open source offering we have come to
     > the conclusion this is not the way forward for LiveCode.

    I agree. In 2013 I was on-the-record as an OSSLC skeptic.
    I urged caution, but my input was summarily brushed aside;
    "we've already decided with our VIPs" was the mindset.
    There were many cheerleaders and nobody wanted analysis.

    I seem to be vindicated, by time and facts.
    My logic was not clouded by cliques or politiques.
    Some of my worries came true, despite popular mantras.

    Now as then, I offer some clear-headed thoughts in kindness.
    Feel free to accept or ignore them; again time will tell.

    To save us all another 8 years of issues, my advice now is:

    1. Get the pricing right!

    Dropping open-source is the first step, and that's right.
    Pricing per platform is probably right, but needs tweaking.
    Standard plan starts off right, but ends up too expensive.
    The discount should increase per addon platform.

    You will find that many people can't afford what they need.
    Probably +1 platform per price tier would be nearer the mark.
    Neither extreme is good; all freeloaders or all Cadillac.
    Let's not jump from one mistake right to the other.

    2. Get the code right!

    A. We build software on LiveCode.
    B. Foundations must be stable and solid.
    C. The goal is to be easier and save dev time.
    D. Therefore LiveCode must offer a solid foundation,
    that is quite stable over time. (Moreso than Apple.)

    LC 7 and 8 introduced tons of bugs. Buggy is bad.
    Performance also dropped dramatically. Not good.

    Today's roadmap looks like a step the right direction.
    Some solid engine improvements.

    For many years I've seen newbies unable to tell
    whether a bug was LC's fault or their own.
    That usually shouldn't be a tossup; firm foundation!
    And LC needs to perform well to be competitive.

    When an underlying API changes, our top-level code shouldn't.
    Sometimes maybe, but usually not. Understand LC's paradigm.
    Think how expensive client-side code changes were from 7 to 9.

    3. Get the listening right!

    I've warned about cliques and ever-changing inner circles.
    Yep, there's a reason why group-think has a bad reputation. :)

    Also about pre-biased poll designs and cherry picked focus groups.
    Yep, you hear what you expect, but you don't get true feedback.

    Diversity of opinion is good, and objectivity is rare.
    But logic is a firm foundation, and emotion is not.
    You won't recruit a new user generation by limiting the narrative.
    Listen and learn. It always goes both ways. That's the beauty of it.

    4. Happy coding!

    I'm stick sick (fever too at the moment) so just pitching in
    right now with my observations out of kind timely consideration.
    So no flame wars at me please; time will verify what I've said.

    Looks like we're entering a promising new chapter. Back to rest!
    (More news of my own eventually, after I shake this illness....)

    Best wishes,

    Curry Kenworthy

    Custom Software Development
    "Better Methods, Better Results"
    LiveCode Training and Consulting
    http://livecodeconsulting.com/

    _______________________________________________
    use-livecode mailing list
    use-livecode at lists.runrev.com
    Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
    http://lists.runrev.com/mailman/listinfo/use-livecode






More information about the use-livecode mailing list