Alex, no worries -- not everyone is optimizing for the same things. For our 
team, things like async stack traces have proven valuable to speed up 
debugging. 

The way we use streamline, we never have to explicitly compile. We just 
call require('streamline').register(...) at the top of our main module, and 
then the streamline runtime automatically re-compiles any streamline source 
files if needed (and persistently caches the results) as they are 
require()'d along the way. so while technically there is compilation going 
on, it's a JIT process, completely transparent and painless in my 
experience. In other words, the streamline language still feels like 
javascript, the streamline dev experience still feels like javascript (no 
explicit compile). 

Generators certainly seem to be the future for javascript. Streamline can 
target generators as one of its backends btw. However, as you point out, 
generators are still pretty early. As part of that, if you look at the 
performance tests (https://gist.github.com/bjouhier/5554200) that i 
referenced in the blog post, you can see that the results with generators 
lagged behind, at least as of when these tests were done. 

Seth


On Wednesday, January 8, 2014 12:13:42 AM UTC-8, Alex Kocharin wrote:
>
>  
> I'm not looking for async stack trace. If I were, I'd probably pick up 
> "trycatch" module instead.
>  
> What I'm asking is that what is the point of writing javascript if you 
> can't use it without compiling?
>  
> If you can use a compiler, you can use typescript, iced coffee and a dozen 
> languages better than javascript. If you don't want to use a compiler, 
> fibers and generators will help without any streamline stuff. So what is 
> the point...
>  
> -----
>  
> I'm using callbacks only. People who don't understand them just can't work 
> with node, so I have no regrets about that. The biggest drawback so far was 
> that debugger can't step in async calls, don't know what to do about it.
>  
> If I wanted to write sync-like code, I'd probably turn to generators and 
> "co" module. It looks nice, but I didn't actually manage to try it, since 
> generators aren't on by default even in 0.11.x...
>  
>  
> // alex
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" 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/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to