wycats

74 ms·

391.
by wycats 15y ago
Stuff like this makes me seriously doubt whether Python critiques of Ruby's "blocks and methods" (SO MANY CALLABLES; ONE AND ONLY ONE) are actually made in good faith.
392.
by wycats 15y ago
In Ruby, the Ruby Toolbox does a good job of providing reasonable, automatable metrics. https://www.ruby-toolbox.com/
393.
by wycats 15y ago
In ruby 1.8, I/O is asynchronous in threads too...
394.
by wycats 15y ago
We can use the technique first described here https://github.com/glenjamin/node-fib by using Fibur.pass. def fib(n) Fibur.pass return n if (0..1).include? n fib(n-1) + fib(n-2) if n > 1 end Now, if you wrap this i
395.
Fibur gives you full concurrency during your I/O calls in Ruby 1.9(gist.github.com)
53 points by wycats 15y ago|20 comments
396.
by wycats 15y ago
blocks may map onto function passing in JavaScript at a high level, but they also do some things that are different in important ways. Most notably, all code in Ruby blocks, including return, super, and yield, execute as if in the original
397.
by wycats 15y ago
Aren't there scenarios where this would be ok? Say 1,000 people are subscribing each week, 100 are opting out and 90 are clicking links. What matters is opt outs per subscriber, not opt outs per link clicked.
398.
by wycats 15y ago
Apple wasn't a "design startup". Sure, Jobs valued design, but none of Apple's founders were designers.
399.
by wycats 15y ago
SPDY is not a good example. Google published the SPDY protocol before they rolled it out across all their properties, and Firefox has implemented it: https://bugzilla.mozilla.org/show_bug.cgi?id=528288
400.
by wycats 15y ago
There is a chipotle ad playing in the movies to the tune of "back to the start" that has a similar effect. The first time I saw it, I was blown away by the Chipotle logo in the closing seconds.
401.
by wycats 15y ago
Man... this is full of crazy talk: For better performance you can use direct functions like $.ajax() than $.get(), $.getJSON(), $.post() because the last ones are shortcuts that call the $.ajax() function. I've never written an app where
402.
by wycats 15y ago
I think the point of this article is that because of Coffee's wide use, developers will often find themselves in a situation where they can't "just don't use it". You could say "don't take that job", but I think the point of the article is
403.
by wycats 15y ago
First-class functions have the `this` problem in every language, and the fat arrow is very nice syntactic sugar for what you have to do anyway Not true. JavaScript's `this` binding is absolutely not the only way to do it. In Ruby: c
404.
by wycats 15y ago
Nope. We just didn't feel good about the naming conflict. See http://yehudakatz.com/2011/12/12/amber-js-formerly-sproutcor...
405.
Amber.js (formerly SproutCore 2.0) is now Ember.js (and released)(yehudakatz.com)
134 points by wycats 15y ago|53 comments
406.
by wycats 15y ago
Guessing http://en.wikipedia.org/wiki/Pug_(fictional_character) :P
407.
by wycats 15y ago
We emailed them immediately once we realized and they (of course) said they would prefer if we rename to something else. Because we had been using the name publicly for so long, we decided to lay out the relevant details and ask Hacker News
408.
by wycats 15y ago
Amber is not affiliated with SproutCore at all anymore.
409.
Poll: Should we rename Amber.js?
50 points by wycats 15y ago|65 comments
410.
by wycats 15y ago
Go back to "SproutCore 2.0"
411.
by wycats 15y ago
Stick with "Amber.js" with a prominent link to Amber Smalltalk
412.
by wycats 15y ago
Come up with a different name
413.
by wycats 15y ago
Amber supports one-way bindings: App.Post = SC.Object.extend({ fooBinding: SC.oneWay("Bar.baz") })
414.
by wycats 15y ago
Amber's runtime component runs in node without any special browser shims.
415.
by wycats 15y ago
"Blossom will use the GPLv3 license, with commercial licensing similar to the Sencha model." I don't have a clear idea about what's going on in the SproutCore community, but I don't think this has universal support. One of the reasons we re
416.
by wycats 15y ago
"Fortunately, SproutCore 2.0 was going to fix a lot of that. Only now it isn't. Do we have two half-baked, related frameworks? Are they kinda ports of each other? Is SproutCore 1.x now deprecated? And how confusing will it be when SproutCor
417.
by wycats 15y ago
A few months ago I showed a demo at a meetup of using Amber in node. The main benefit of Amber in a node environment is the way it abstracts asynchronous behavior through bindings and observers. I could easily imagine an Amber object repres
418.
Announcing Amber.js(yehudakatz.com)
311 points by wycats 15y ago|112 comments
419.
by wycats 15y ago
Apache already has a mod-spdy ( https://code.google.com/p/mod-spdy/ ), and varnish is in wait-and-see mode ( https://www.varnish-cache.org/lists/pipermail/varnish-misc/2... "SPDY isn't even an official IETF draft yet") I agree. Getting SPD
420.
by wycats 15y ago
SPDY absolutely was intensively specified: http://mbelshe.github.com/SPDY-Specification/draft-mbelshe-s...

More ›