How do you handle the poor performance of LC 7?

[Andrew Kluthe]

Of note, the only things wrong with the prototypes we did were that the
reports (pulling large amounts of data from a server, processing it,
generating html reports and outputting it) were noticeably slower (not like
what is often reported on this list, but slow enough for someone to notice
its slower). To be fair, they were fairly complex reports and they should
probably be offloaded to a reporting server that can process them in a
queue at its own pace. Which is what we did. To be fair, this new reporting
process was even slower than the slowness introduced by upgrading to newer
versions.

These issues are just the breaks with the engine changes. I get that you
guys are optimizing things, but by design, the entire thing is just
inherently a wee bit slower to your own admission. This wasn't good enough
for those who made the decision to pull the plug.  Basically, after
following along for the last few years my boss now considers LC to be good
for really robust prototypes at this point but would never let me do
another project that affects our production lines in LC, regardless of how
many things have been shot into space running livecode.

On Fri, May 29, 2015 at 2:50 PM Andrew Kluthe <andrew at ctech.me> wrote:

> Not a bad option for some, then. Unfortunately, decisions like that on the
> software in question are over my head. They have decided they would rather
> I just do it in something more mainstream, than spend time in that way. I
> fought tooth and nail to get permission to do it in livecode. It works, it
> still works. We'd been using it for close to 5 years and dealing with some
> small gotchas. People above me at the company I work for donated to the
> kickstarter and were as excited as the rest of us at the possibilities the
> future of livecode introduced. They have been watching new releases roll
> out and wanting to move forward on big improvements and the new features.
>
> We gave it a shot with some prototypes with the newer versions. My
> superiors were tired of waiting/dealing with it and decided to pull the
> plug on livecode. The decision was made to re-write most of it for .NET
> (some if it on my own dime) to compensate for that risk going ahead.
>
> Livcode will still be great again. I'll probably use it for freelance work
> at some point in the future, but around here. It's just not an option the
> company wishes to pursue any further.
>
>
> On Fri, May 29, 2015 at 2:28 PM Peter TB Brett <peter.brett at livecode.com>
> wrote:
>
>> On 2015-05-29 21:12, Andrew Kluthe wrote:
>> > Thanks for the reply, Richard.
>> >
>> > I totally understand what you're talking about there, but between a
>> > full
>> > time gig, very young children, and freelance work at night. I just
>> > don't
>> > know where I'd find the time to be effective at giving them the level
>> > of
>> > detail that they need. I can't give them the actual software that's
>> > suffered from these issues as it's all under NDA.
>>
>> Hi Andrew,
>>
>> Note that we are able to enter a NDA if that's necessary!  Please
>> contact support for more information.
>>
>>                                          Peter
>>
>> --
>> Dr Peter Brett <peter.brett at livecode.com>
>> LiveCode Engine Development Team
>>
>>
>> _______________________________________________
>> 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
>>
>