W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

Re: [fullscreen] Problems with mouse-edge scrolling and games

From: Brendan Eich <brendan@secure.meer.net>
Date: Mon, 24 Feb 2014 18:47:18 +0100
Message-ID: <530B85A6.4050804@secure.meer.net>
To: Glenn Maynard <glenn@zewt.org>
CC: Florian Bösch <pyalot@gmail.com>, Thibaut Despoulain <thibaut@artillery.com>, Brandon Jones <bajones@google.com>, Ian Langworth <ian@artillery.com>, Webapps WG <public-webapps@w3.org>
Glenn Maynard wrote:
> It's not the application's job to keep the mouse cursor responsive, 
> it's the system's.  Hiding the system mouse cursor and drawing one 
> manually is always a bad idea.

Agreed!

In the same vein, programmers cannot avoid GC pauses without relying on 
pause-free or at least incremental GC (which BTW some browsers' JS 
engines have already, e.g., SpiderMonkey in Firefox), or as a real 
alternative, cross-compiling C or C++ for example via Emscripten, to 
allocate heap memory from a typed array.

Florian, your goals are good, but the means to those ends must involve 
better runtimes or compilers -- not on JS programmers working harder to 
avoid GC while still somehow allocating objects frequently and even 
implicitly.

/be
Received on Monday, 24 February 2014 17:47:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC