wycats

39 ms·

331.
by wycats 15y ago
I don't necessarily like having to have every ORM/data library have to know about this concern...
332.
by wycats 15y ago
Not all security vulnerabilities can be protected automatically by a web framework. In many cases, frameworks provide features that developers can use themselves to secure their applications. Example: XSS is a common web security problem. I
333.
by wycats 15y ago
For what it's worth, we'd like it if security vulnerabilities in Rails were disclosed to http://rubyonrails.org/security . Obviously this situation is a bit more complicated, as a ticket was opened up, and a lot of community discussion occ
334.
by wycats 15y ago
Not every idea from Merb made it into Rails. Especially when an idea would cause significant backwards-compatibility breakage (return string from action vs. implicit rendering), we stuck with the Rails approach. I always felt that "it's up
335.
by wycats 15y ago
Here's my proposal for improving the situation: https://gist.github.com/1974187 Merb's approach was to have mass assignment protection in the controller, and I personally think it's self-evident that it belongs there. Moving it into the c
336.
by wycats 15y ago
Interestingly, not really, because the Ember run loop implementation coalesces multiple calls to set, so using setProperties (which allows you to pass in multiple properties at once) doesn't really affect performance much. It's one of the f
337.
by wycats 15y ago
I can address some of these, as I've been staring at the profile quite a bit: "bulk innerHTML updates vs. granular DOM twiddling (especially in different browsers)." A part of the cost is definitely in making these small changes, but not a
338.
by wycats 15y ago
I've been looking at the profiler (both Chrome and Safari) a bunch and it is emphatically not an issue with handlebars template. A number of things show up, but templates don't really show up as a major factor at all. There are a number of
339.
by wycats 15y ago
I absolutely agree that comparing actual apps is a very useful point of comparison. Ember itself is actually relatively new. The fact that Ember inherited some of its runtime semantics from SproutCore might give the mistaken impression that
340.
by wycats 15y ago
Bro come on :( Ember is a total, ground-up rewrite of some of SproutCore's ideas and you know it. I don't count any SproutCore examples as Ember examples, and saying that Ember is anything other than plain 'ol open source is unfair. I don't
341.
by wycats 15y ago
Doesn't making a new X because it's easy violate the "There should be one-- and preferably only one --obvious way to do it" rule? From the way the Python community talks about its strengths, I'd expect there to be pressure against creating
342.
by wycats 15y ago
Hilariously, while it's true about JavaScript, it is not true about Ruby.
343.
by wycats 15y ago
You're looking for "ex post facto law": http://en.wikipedia.org/wiki/Ex_post_facto_law "In the United States, the federal government is prohibited from passing ex post facto laws by clause 3 of Article I, section 9 of the U.S. Constitutio
344.
by wycats 15y ago
This headline is a good example of the problem with the passive voice. My first assumption when reading the headline was that an Apple lawyer told him that. A better headline would be something like: "Palm CEO Told Jobs Anti-Poaching Pact '
345.
by wycats 15y ago
I recently released a JavaScript parser for Ruby that uses Evan Phoenix's kpeg library: https://github.com/wycats/parsejs
346.
by wycats 15y ago
They are proposed standards. See my comment at http://news.ycombinator.com/item?id=3456815 . Standards don't appear out of the ether, fully formed and ready to be implemented. Properly developed standards are built precisely the way Goog
347.
by wycats 15y ago
Google's implementations in Chrome are virtually always released as open specifications. Dart: http://www.dartlang.org/docs/spec/ SPDY: http://dev.chromium.org/spdy/spdy-protocol WebRTC: http://dev.w3.org/2011/webrtc/editor/webrtc.html
348.
by wycats 15y ago
Fixed in the original post. Thanks for letting me know about the typo!
349.
by wycats 15y ago
For what it's worth, I've been writing JavaScript for longer than I've been writing Ruby, and have contributed rather extensively to JavaScript libraries over a number of years.
350.
by wycats 15y ago
Nah. Ruby just raises an exception in this case: class BlockInvoker def initialize(&block) @block = block end def invoke @block.call end end BlockInvoker.new { puts 1 }.invoke def get_block_invok
351.
by wycats 15y ago
Just to clarify, here's my original comment: In order to have a language with return (and possibly super and other similar keywords) that satisfies the correspondence principle, the language must, like Ruby and Smalltalk before it, have a
352.
by wycats 15y ago
He then proposes a wholesale change to function semantics in the language. Actually, I linked to a proposal by Brendan Eich, the creator of JavaScript. I mean, come on, this is the same guy who wrote a reopenClass function in Ember.js J
353.
by wycats 15y ago
Yes.
354.
JavaScript Needs Blocks(yehudakatz.com)
227 points by wycats 15y ago|91 comments
355.
by wycats 15y ago
The "well-defined purpose" is actually: "To promote the Progress of Science and useful Arts" And the only reason nothing entered the public domain is that due to a copyright extension, there's a gap during which time nothing will enter the
356.
by wycats 15y ago
There's mod-spdy for Apache, and that's the future of SPDY adoption.
357.
by wycats 15y ago
All the people talking about whether HBO wants to "piss off the cable companies": you do know that HBO is owned by Time Warner, a cable company, right?
358.
Yak Shaving(blog.hasmanythrough.com)
15 points by wycats 15y ago|0 comments
359.
by wycats 15y ago
As a Ruby developer, I'm glad I won't need to deal with a "All Rails Servers are Vulnerable to DoS" FUD post in the next few days.
360.
by wycats 15y ago
Ruby 1.9, the current production version of Ruby, is not vulnerable. Rails 4, the next version of Rails, will require Ruby 1.9.

More ›