Things are not that bad. (See Shadow DOM for instance where people begged for it to become a standard)
You should definitely write something up and have a working prototype that demonstrates how your solution improves performance, cleaner implementations, etc. You will also have to prove that this won't introduce security issues. Any new feature will face a lot of scrutiny since it impacts everything that runs a web browser so be prepared for negative feedback. You will spend much more time replying on mailing list than actually implementing it. :-) Even if your proposal fails, it will still be used as a reference for a future solution. On Sat, Apr 13, 2013 at 12:35 PM, Dirk Pranke <[email protected]> wrote: > > On Fri, Apr 12, 2013 at 10:44 PM, Filip Pizlo <[email protected]> wrote: > >> >> On Apr 12, 2013, at 10:43 PM, Ryosuke Niwa <[email protected]> wrote: >> >> Perhaps we can come up with some JS API for shared memory & lock and >> propose it in TC39 or WebApps WG? >> >> >> I think that would be wonderful. Anyone else interested? >> >> > Feel free to write something up, but as I said before, I suspect any such > proposal is DOA in either group. If you wanted to get something adopted > here, I think you would have to build something, ship it, and then have it > become so successful that the standards groups would be forced to > reconsider their positions. > > -- Dirk > > > _______________________________________________ > webkit-dev mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
