From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:af6e:e500::35bb:7ca9]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id EA688791FB for ; Wed, 5 Jul 2017 08:00:37 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20170605095053.eklhad@comcast.net> Date: Wed, 05 Jul 2017 08:01:12 -0700 In-Reply-To: <20170605095053.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 05 Jul 2017 09:50:53 -0400") Message-ID: <87bmozyll3.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] obj = new Foo() X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.24 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 15:00:38 -0000 Karl Dahlke writes: > If we get duktape working, and if jsrt passes, and it meets our needs, I don't think we'll ever go back to mozilla. > I can't imagine going back to mozilla. I can't imagine a really compelling reason to switch again, either. > but if you-all can convince me that's a bad idea, then I guess I could > leave a bunch of classes in C, where they are now, even though they're > pure and simple and could easily be in js instead. The main arguments for and against moving classes into JS have already been made on this list. And if we ever do have to switch away from Duktape for some reason, that switch is going to be painful, regardless of whether the code is in C or JS. So I don't think I can convince you. -- Chris