Karl Dahlke <[email protected]> writes: > It's also about 4 times as much code. > So I remain in the "implement it in js" camp,
Let me strengthen your case just a little bit. Every couple years, we get forced to make some sweeping changes to the edbrowse JS code, on account of API deprecation. Here's a little summary of history since adopting Spidermonkey. You started with Spidermonkey JS 1.5. That was around for a while, but it was dropped circa 2011. We had to port to 1.8.5, the new hotness. In early 2014, 1.8.5 was on the chopping block, and we had to port to version 24. Now, version 24 is on the way out. We have to make more changes. This is all a bunch of churn. Nobody seems too thrilled. What is going to happen two to three years from now? I'm tentatively in your camp. Problem is, I see both sides of this argument, so I can't make a clear stand either way. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
