[ANN] Release 10.0.0 DP-1

William de Smet williamdesmet at gmail.com
Tue Nov 23 13:02:36 EST 2021


Been playing all day with LC 10 DP-1 and mostly testing Web/html5 and I can
confirm Firefox is also the fastest in WASM on a remote webserver.
Safari is the slowest. Most people I know use the Chrome browser however.
On Chrome OS speed varies depending on the state of the Chromebook (age).


Op di 23 nov. 2021 om 14:14 schreef Andre Garzia via use-livecode <
use-livecode at lists.runrev.com>:

> Brave, Edge, and Chrome are all using the same engine. They should perform
> the same. IIRC Firefox still has the best WASM performance, mostly because
> it was invented there and they had more time to optimize.
>
> That the way the web browsers works is that "they really hate opening local
> HTML files with file:// protocol". Opening a file like that will switch on
> a lot of protection in the browser and restrict many APIs. The correct way
> to test WASM files is by running a local web server and opening it using
> HTTPS (or HTTP if you must).
>
> Be aware that the most important change regarding performance between WASM
> and the previous ASM.JS based engine will not be visible when running a
> local server. To load an ASM.JS based webapp, the browser needs to fetch
> all the files before loading them into memory and parsing them. The new
> WASM technology allows a browser to load the files while the transfer still
> happening. It is a streaming kind of tech. This means that besides all the
> other benefits, you don't need to deal with the latency of waiting for
> transfers to complete before the app starts to load. When running locally,
> the transfer is so fast that you can see this benefit, but try placing
> those files in a remote server and the difference should be night and day,
> specially for really large builds.
>
> On Tue, 23 Nov 2021 at 09:34, Bernard Devlin via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
> > Thanks Panos. That kind of works. It always opens in the default browser
> > i.e. trying to select another browser as the test target has no effect.
> Is
> > this a known bug?
> >
> > From test/save with browser closed (compile to standalone, then let IDE
> > launch browser):
> > Load time LC 10 - 5 secs
> > Load time LC 9.6.1 - 7 secs
> >
> > Loading same saved stack with browser already open (re-using URL):
> > Load time LC 10 - 2 secs
> > Load time LC 9.6.1 - 5 secs
> >
> > I tested with both Brave and Edge, but couldn't detect any difference in
> > load speed between them.
> >
> > These tests were just wall clock time.
> >
> > On Mon, Nov 22, 2021 at 3:48 PM panagiotis m via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> >
> > > Hello Bernard,
> > >
> > > Trying to open the local html file will fail due to CORS - Firefox may
> or
> > > may not work - I think it needs some tweaks, and not sure if this is
> > still
> > > possible in the latest versions. We probably need to update this
> lesson.
> > >
> > > The correct way to test is to use the Development -> Test Target ->
> > <Choose
> > > your browser> and then Development -> Test
> > >
> > > Hope this helps.
> > >
> > > Panos
> > > --
> > >
> > >
> > _______________________________________________
> > 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
> >
>
>
> --
> https://www.andregarzia.com <http://www.andregarzia.com>
> Want to support me? Buy me a coffee at https://ko-fi.com/andregarzia
> _______________________________________________
> 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