Re: Java plugin phase out timeline
Mikael Haltali <[email protected]> Thu, 25 Feb 2016 16:23:31 +0100
| Newsgroups | gmane.comp.mozilla.devel.plugins |
|---|---|
| Message-ID | <CAP-khbh9OvtR=5E4_Yxog-G7OJpV7cR8qYJCKwGhunMt3aJLWA@mail.gmail.com> |
Ok my bad for pointing people in the wrong direction How come js-ctypes is not recommended but child_process is although it's marked as "Experimental" in the documentation. What does that even mean? A next update could break the API or could it be removed in a new build? Anyways thanks for the information On Thu, Feb 25, 2016 at 4:09 PM, Benjamin Smedberg <[email protected]> wrote: > > > On 2/24/2016 12:25 PM, Mikael Haltali wrote: > >> Hi, >> the best solution currently is js-ctypes which enables you to build an >> extension that calls a custom dll written in C >> > To repeat what Chris Peterson wrote, we strongly discourage use of > JS-ctypes is new code: it is very difficult to write code which is > memory-safe. We strongly encourage everyone to use a separate process and > communicate with pipes using system/child_process or the future > WebExtensions. > > --BDS > >