On Behalf
> Of Mark Talluto via use-livecode
> Sent: Thursday, June 14, 2018 5:09 PM
> To: How to use LiveCode
> Cc: Mark Talluto
> Subject: Re: Anything LiveCode Can Learn From GO
>
> I missed the local db part. It is clearly written in your original email.
> But, since I
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Tom Glod via use-livecode
Sent: Thursday, June 14, 2018 9:21 PM
To: How to use LiveCode
Cc: Tom Glod
Subject: Re: Anything LiveCode Can Learn From GO
Ralph, which part i
o: How to use LiveCode
> Cc: Mark Talluto
> Subject: Re: Anything LiveCode Can Learn From GO
>
> I missed the local db part. It is clearly written in your original email.
> But, since I am here typing these chars…pondering…how about running a local
> server that accesses your
, 2018 5:09 PM
To: How to use LiveCode
Cc: Mark Talluto
Subject: Re: Anything LiveCode Can Learn From GO
I missed the local db part. It is clearly written in your original email. But,
since I am here typing these chars…pondering…how about running a local server
that accesses your local db and use
nal Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
> Of Mark Talluto via use-livecode
> Sent: Thursday, June 14, 2018 2:21 PM
> To: How to use LiveCode
> Cc: Mark Talluto
> Subject: Re: Anything LiveCode Can Learn From GO
>
> tsNet with async
Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Mark Talluto via use-livecode
Sent: Thursday, June 14, 2018 2:21 PM
To: How to use LiveCode
Cc: Mark Talluto
Subject: Re: Anything LiveCode Can Learn From GO
-boun...@lists.runrev.com] On Behalf
> Of Bob Sneidar via use-livecode
> Sent: Thursday, June 14, 2018 10:56 AM
> To: How to use LiveCode
> Cc: Bob Sneidar
> Subject: Re: Anything LiveCode Can Learn From GO
>
> Multithreading sounds like a good idea until you realize most t
14, 2018 10:56 AM
To: How to use LiveCode
Cc: Bob Sneidar
Subject: Re: Anything LiveCode Can Learn From GO
Multithreading sounds like a good idea until you realize most things that have
to happen in Livecode due to the message heirarchy need to be single threaded.
It's only when you need to m
Multithreading sounds like a good idea until you realize most things that have
to happen in Livecode due to the message heirarchy need to be single threaded.
It's only when you need to make a server of some sort that multithreading
really needs to be implemented.
Bob S
> On Jun 11, 2018, at
but as i understand it ...changing a single threaded app to multi-threaded
at its core is a huge undertaking aand i'm not sure its even on the drawing
board for v 12 ...but i could be wrongmaybe its coming in v10 :D :D :D
On Mon, Jun 11, 2018 at 9:02 PM, Tom Glod wrote:
> i see what you mean
i see what you mean. the single threaded aspect of LC is a drag...
i'm actually trying my hand at some kind of workaround for this limitation
for the global conference in september i aim to do some multi-core
processing using LC and measure performance gain over specific workloads
...l
I wasn't thinking about high language per se. but more from an engine point
of view, specifically use of "Goroutines"
"But, most of the modern programming languages(like Java, Python etc.) are from
the ’90s single threaded environment. Most of those programming languages
supports multi-thread
LC and Go have entirely different target marketsbut since you can
easily make 1 application talk to another application using sockets .
or open process.. the LC and Go make a wonderful partnership if you
need to build UI ...but also do High Performance Computing.
The 2 can make a great
Hi Sannyasin,
I found a quick small snippet of some “Hello World” GO code and have listed it
below.
I much prefer LiveCode syntax over this stuff any day.
Stick with LiveCode, it’s just better!
Just my 2 cents for the day.
Cheers,
Rick
Add a test to the stringutil package by creating the
f
14 matches
Mail list logo
