3 ms·

I don't care what engine they use; it's largely irrelevant to me. I mentioned that Mozilla is known for having NIH syndrome in response to the parent's questio

by icey 17y ago

I don't care what engine they use; it's largely irrelevant to me. I mentioned that Mozilla is known for having NIH syndrome in response to the parent's question as to why they would use their own JS engine instead of V8. jrockway's point about the timing of it is probably correct, but it doesn't change the fact that people have brought up Mozilla's NIH for years.

bad_user 17y ago
When wanting to use your own engine instead of V8 ... it's not always NIH. They have developers on board familiar with the TraceMonkey codebase. They have developers from Adobe helping out with the Tamarin codebase. That's inside knowledge they would lose and it's debatable if on the long term V8 will deliver ... yes, right now it's the fastest, but is it the fastest approach? Outsourcing a vital component of a project to another open-source project that's younger and hasn't proven its long-term viability should certainly be taken with a lot of care. Personally I'm pretty happy with Firefox. The only thing bothering me is the single-process model, versus the one process per tab of Chrome, but I'm pretty sure they'll fix that pretty soon.
- ewjordan 17y ago
  The only thing bothering me is the single-process model, versus the one process per tab of Chrome, but I'm pretty sure they'll fix that pretty soon. I really hope so. My average number of tabs open seems to be growing logarithmically over time (lately I've been weighing in at about 40, which is not even that many if you use Tree Style Tabs and put your tabs on the left), so I have a whole lot of tabs to reload every time I crash. And that happens quite a bit more often than it should, since I have so many tabs open. If and when Chrome gets a left-side tree tab extension that works on OS X (haven't checked lately, I should keep an eye out), I'll be switching over almost immediately, for this reason alone.

by icey 17y ago

bad_user 17y ago

When wanting to use your own engine instead of V8 ... it's not always NIH. They have developers on board familiar with the TraceMonkey codebase. They have developers from Adobe helping out with the Tamarin codebase. That's inside knowledge they would lose and it's debatable if on the long term V8 will deliver ... yes, right now it's the fastest, but is it the fastest approach? Outsourcing a vital component of a project to another open-source project that's younger and hasn't proven its long-term viability should certainly be taken with a lot of care. Personally I'm pretty happy with Firefox. The only thing bothering me is the single-process model, versus the one process per tab of Chrome, but I'm pretty sure they'll fix that pretty soon.

ewjordan 17y ago
The only thing bothering me is the single-process model, versus the one process per tab of Chrome, but I'm pretty sure they'll fix that pretty soon. I really hope so. My average number of tabs open seems to be growing logarithmically over time (lately I've been weighing in at about 40, which is not even that many if you use Tree Style Tabs and put your tabs on the left), so I have a whole lot of tabs to reload every time I crash. And that happens quite a bit more often than it should, since I have so many tabs open. If and when Chrome gets a left-side tree tab extension that works on OS X (haven't checked lately, I should keep an eye out), I'll be switching over almost immediately, for this reason alone.