This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm having a large number of freezing issues with a file of more than 250 lines. It seems to get worse and worse with the size of the file. Is this a known issue? Any workarounds? |
|
|
Any idea on this guys? I've had to disable the plugin to continue my work, but I really would love to be able to use it. |
|
|
Mindscape is using a managed Javascript parser (Jurassic) which is simply too slow. Google's V8 will dramatically improve the parsing. I'm not sure why mindscape isn't prioritising the performance issues. I like the focus on correcting syntax and highlighting errors, it makes writing coffeescript enjoyable and a tad more readable. But I think it's time to switch to the most performant Javascript engine at the moment. |
|
|
Thanks for the feedback guys. We did briefly look at hosting V8 instead of Jurassic but we felt the extra effort required would be prohibitive. But it sounds like we need to review that. It is simply a matter of resourcing -- finding the time to research and implement V8 hosting. So anything that can cut down this time makes the switch more likely. I've found a .NET wrapper, V8Sharp, on CodePlex which might facilitate this, but the project is marked as 'research' and appears inactive. If you know of any more current .NET-friendly wrappers for V8, do let us know. |
|
|
It looks as if some other people attempting to do the same have created V8 Bridges https://github.com/xpaulbettsx/SassAndCoffee and http://coffeemonitor.codeplex.com/ I'm not sure if these are implementing exactly what you are trying to do with the V8 engine, but it looks as if the coffeemonitor can utilize both a V8 or Jurassic compiler
Also, the slowness is not necessarily in the compilation of the coffeescript, but rather just navigating the file, moving the cursor from line to line, etc.
|
|
|
Thanks for the pointers. The highlighting stuff (which is what is slowing navigation) also uses the real CoffeeScript code, and therefore also currently runs on Jurassic -- if we can drop in a faster engine then that will benefit navigation as well as compilation. |
|
|
Please take the time to do so, as the performance issue is prohibitive on larger scale projects. If making workbench a paid product would grant it more priority, I would suggest doing so, as it is great software but mostly unusable at the momment. Maybe a temporary fix would be to keep highlighting from running at all times, instead re-highlight at fixed intervals plus at save-time. As it is, I can't even add a space without visualstudio hanging for a few momments. |
|
|
I agree 100% with bagosm. I really do not want to turn off the extension because I also use it for my scss files, but this performance issue is forcing me to do so. If there is any simple fix in the meantime, I would also appreciate that. |
|
|
Hi chaps, Thanks for the feedback. Just to let you know that we have started work on migrating to V8, but it looks like it will not be a trivial change (unfortunately, to support live highlighting, we need to implement some Node.js-alike extensions, which was easy on Jurassic but is causing us some problems on V8). We hope to have something for you soon -- thanks for your patience and your suggestions! |
|
|
Thanks for the progress update, this will be highly appreciated. Running with ~300 lines right now and I am starting to feel the slowness. Great tool and this fix will make it much better. |
|
|
Hey folks, I'm pleased to announce that we now have an experimental build of Web Workbench that runs the CoffeeScript highlighter and compiler using V8. In our internal tests it's a lot faster but we'd really appreciate you guys taking it for a spin, partly just to check that it does make enough of a difference for you but also to give it a bit of a hammering in real-world environments. (The reason this is a concern for us is that native code like V8 could be more brittle to different OS versions, 32/64 bit etc. than pure .NET code.) If you're willing to give it a go you can get it from: http://assets.mindscape.co.nz/Downloads/Mindscape.WebWorkbench.Integration.10.vsix Please do let us know how it goes for you -- whether it works or not! Barring problems we'll push it out through the Visual Studio gallery sometime next week. |
|
|
Hi there, I am using win7 x64 - I just applied the update and I am seeing a great improvement! Woohoo! Thanks!! -Dan |
|
|
10 words: "Awesome job"!
So far soo good, on VS2010 win7 64bit, will try to test it also on vs2011 during the weekend. Compilation doesnt seem to produce bogus results and highlighting is superfast, even on a ~1000 line file! |
|
|
What is the recommended way of reporting bugs? For the momment the only one I have come accross is that the existencial operator: variable? only translates to variable != null
(it should also check for typeof != undefined |
|
|
Hi bagosm, For bugs in Web Workbench, such as incorrect highlighting or failing to generate JavaScript, report them via the forums here. For incorrect compiler output, check against the standalone CoffeeScript compiler (e.g. paste the code into the Try CoffeeScript window at the CoffeeScript site). If the standalone CoffeeScript compiler gets it wrong, report the bug there. If the standalone compiler gets it right but we get it wrong, it probably means we need to upgrade our copy of the compiler, so report the bug here. |
|
|
Hello, Thanks for this clarification. As it turned out coffeescript likes to check for existence only using null in the case its a method call. IE:
iexist = afunc? Compiles to: var iexist; iexist = typeof afunc !== "undefined" && afunc !== null; iexist = afunc.amethod != null; |
|