I have to work with people who cant (for various reasons) use beta code, and so I tend not to do so myself. Just hope it doesn get ES4'ed before it goes live.
On Mar 22, 3:50 pm, johnjbarton <[email protected]> wrote: > Other than profiling (performance measurements) I don't expect any > issues from the introduction of a JIT (I guess that is what you mean > by tracemonkey). We've seen no problems or issues so far. JITs > generally work to be hidden behind the interpreter and Firebug works > above the interpreter, so they don't meet very often. > > I expect the JIT to have dramatic impact on a few cases, modest impact > on a lot of cases, and no impact on the majority of cases. This is > based on the character of programs -- most are limited by interaction > between components, not internal straight line code -- based on the > track record of JITs in Java. BTW, Firefox has an excellent > interpreter, making the JIT folks work hard to beat it. But by now you > can use FF3.1 and find out for yourself how it will work on your code. > > jjb > > On Mar 22, 3:06 am, Tom Potts <[email protected]> wrote: > > > Wondering if Firebug will cope OK with tracemonkey (assuming its still > > due for FF3.1) > > I'm going to embark on a large projects and if Firebug and Tracmonkey > > get on well then that will move a lot of code to clientside in the > > browser. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
