Earlier quoted context omitted.
Huh: https://kraken.io/
Huh: http://asana.github.io/kraken/
Yeah, these days people don't seem to give a shit to preceding OS projects with the same name. "Ours will be much bigger".
PayPal releases Kraken, Node.js framework
11–20 of 30 posts
Re: PayPal releases Kraken, Node.js framework
#12==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
[deleted]
Re: PayPal releases Kraken, Node.js framework
#13Earlier quoted context omitted.
You are not their target market.
Explain?
This might provide you some insight: http://thedailywtf.com/Articles/The-Slow-Down-Loop.aspx
In all seriousness, adding interstitials can provide value. If the login performance has high variance, it's better to set an expectation that it will take 5 seconds than leave the user wondering if the click actually worked. Similarly, Apple has done an amazing job with UI transitions in iOS to mask the actual load time.
Re: PayPal releases Kraken, Node.js framework
#14==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
I'd be interested to hear what you don't like about Object.keys or Array#forEach. Not looking to start an argument, just genuinely curious why you prefer a utility library over native methods -- especially in Node, where you have guaranteed ES5 compatibility.
Also: self = this can be avoided in a lot of cases with Function#bind, but not always. Seems like a weird criticism to me.
Re: PayPal releases Kraken, Node.js framework
#15I was honestly expecting something with more added value to warrant it's own name, maybe a viable competitor to Sails.js, Derby, etc. Lusca is nice, everything else is more or less what everyone is already doing - runtime config, controllers, grouped routes, etc, more of a template than a framework. Good thing they are not reinventing the wheel.
Re: PayPal releases Kraken, Node.js framework
#16==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
I'd be interested to hear what you don't like about Object.keys or Array#forEach. Not looking to start an argument, just genuinely curious why you prefer a utility library over native methods -- especially in Node, where you have guaranteed ES5 compatibility. Also: self = this can be avoided in a lot of cases with Function#bind, but not always. Seems like a weird criticism to me.
[deleted]
Re: PayPal releases Kraken, Node.js framework
#17==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
A framework should at least be template engine agnostic. I hate handlebars and dust.js , why should i use that? I want to use a jinja like templating language.
Seems even their i18n component is tied to their view layer. And 0 doc comments in the scripts? how do they document their own code ?
Re: PayPal releases Kraken, Node.js framework
#18==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
I'd be interested to hear what you don't like about Object.keys or Array#forEach. Not looking to start an argument, just genuinely curious why you prefer a utility library over native methods -- especially in Node, where you have guaranteed ES5 compatibility. Also: self = this can be avoided in a lot of cases with Function#bind, but not always. Seems like a weird criticism to me.
Native methods can be slower than simply using a for (Edit: while) loop:
http://allyoucanleet.com/post/21624742336/jsconf-us-12-slide...
self = this is error prone because it relies on JavaScript's lexical scope to share a variable across nested functions. It's a gross abuse of closures. It invalidates the ability to bind or use apply later, since everything is bound to that local variable self, and it's simply not needed and is probably used to avoid considerable use of bind, but using bind is only an issue when you write flock of seagull style nested function code. using self = this is not the right solution, writing more modular code with smaller functions is.
Re: PayPal releases Kraken, Node.js framework
#19==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
A framework should at least be template engine agnostic. I hate handlebars and dust.js , why should i use that? I want to use a jinja like templating language. Seems even their i18n component is tied to their view layer. And 0 doc comments in the scripts? how do they document their own code ?
Yeah didn't notice the lack of doc comments. That is nice to have for a library.
Re: PayPal releases Kraken, Node.js framework
#20==== Don't like: dust.js templates instead of handlebars self = this all over the place native use of forEach and Object.keys instead of underscore or lowdash ==== I like: that you can change the template system grouping routes, I always add this myself, makes it more django like security stuff like csrf dev and prod environment awareness directory layout is cool apache license uses grunt they use Object.create! one…
What's wrong with using .forEach or Object.keys? Underscore will fallback to that if it's supported (which is always in nodejs).
Someone else asked this too, check out my answer there.