wycats

58 ms·

511.
by wycats 16y ago
Yipes. Maybe I can take solace in the fact that mine is "handlebars.js" (plural)?
512.
by wycats 16y ago
To be fair, Alan did most of the hard work after my initial prototype :)
513.
Announcing Handlebars.js (A Mustache Superset)(yehudakatz.com)
54 points by wycats 16y ago|14 comments
514.
by wycats 16y ago
I just wanted to say a few things. First of all, this is a huge milestone for Rails. From my perspective, this work is three or four years in the making, from the beginning of the Merb efforts, through the merge, and on until the final rele
515.
by wycats 16y ago
Sorry about that :) I explicitly referenced a chat server (lots of concurrent, mostly-idle requests) as a case where I'd personally use an async solution. There are certainly middle-ground cases where the question is muddier (and more relig
516.
by wycats 16y ago
As I tried to make clear throughout the post, I'm not really making an argument for a huge amount of threads, or programming that involves a lot of exposed shared state. I'm making an argument about how threads are used (in real life) in we
517.
by wycats 16y ago
The Rails Plugins site ( http://railsplugins.org ) that we built at Engine Yard has 406 registered plugins, and a criteria for thread safety ( http://railsplugins.org/plugins?criteria[]=2 ). The way it works is that the author can specify w
518.
by wycats 16y ago
Forking creates a new process, initially "sharing" memory via copy-on-write semantics (and therefore being eligible to run on another core). However, C Ruby's default mark-sweep garbage collector touches pretty much all memory immediately,
519.
by wycats 16y ago
If you use C Ruby, you'll need one Ruby process per core, managed by something like Passenger (mod_rails) or Unicorn. If you use JRuby, you'll need one Ruby process per machine (for N cores), managed by the JVM. For boxes with a lot of core
520.
Threads (in Ruby): Enough Already(yehudakatz.com)
116 points by wycats 16y ago|36 comments
521.
by wycats 16y ago
I thought a bit about how to title this. On the one hand, I'm talking about successfully switching to vim. On the other hand, the thrust of my argument is that I got very bad advice repeatedly over several years on the topic. Apologies if t
522.
What's New in Ruby's Bundler (1.0 RC1)(yehudakatz.com)
7 points by wycats 16y ago|0 comments
523.
by wycats 16y ago
I've been working on a rework on a branch that should be merged in this weekend. It takes a lot of the feedback I've gotten and existing forks into consideration, as well as lessons learned from Rack. It was originally an experiment, and I
524.
by wycats 16y ago
I should also add that it looks as though the bug has been put back into the 1.9.2 milestone and Shyouhei has asked to make it a 1.9.2 blocker. For the moment, I am cautiously optimistic.
525.
by wycats 16y ago
For reference, the open bug is http://redmine.ruby-lang.org/issues/show/3140
526.
by wycats 16y ago
An easier Ruby solution would be: ("letters in this sentence" + "and this one").chars.sort.reverse
527.
Customizing Rails 3 Applications With Plugins (Screencast)(railsdispatch.com)
8 points by wycats 16y ago|0 comments
528.
by wycats 16y ago
We very much are :)
529.
by wycats 16y ago
Also, http://yehudakatz.com/2010/05/17/encodings-unabridged/ My post is mostly about the ramifications of Ruby 1.9's encoding support on Rails (a similar topic), but I go into some detail about the problems of Japanese encodings on the we
530.
by wycats 16y ago
I'd be interested to learn where the BINARY data is coming from in the first place. For reasons I outlined in a recent blog post force_encoding is almost never a reliable general-purpose solution
531.
by wycats 16y ago
I've been doing a lot of the encoding work on Rails 3. Curious what your issues are so I can be sure we get it right for Rails 3
532.
All You Need to Know About Encodings and Ruby 1.9(yehudakatz.com)
38 points by wycats 16y ago|4 comments
533.
by wycats 16y ago
While there are quite a few different workflows, there are a number of similar operations (get a repository, get updates from a remote, push changes to the remote). My point was not to compare git (as a whole) to subversion, it was to demon
534.
by wycats 17y ago
@mbrubeck I totally agree that there is a real problem, but from all the responses, I think it's actually the opposite of what they're saying. People say "it's all well and good that Mobile Webkit has hardware accelerated transforms, but
535.
The Web Doesn't Suck. Browsers are Innovating.(yehudakatz.com)
111 points by wycats 17y ago|54 comments
536.
by wycats 17y ago
ExtJS has repeatedly claimed that their Open Source license does not apply to an application in which any part (including the backend) is proprietary. I don't personally agree that that's how the GPL works wrt JS, but if you can't afford th
537.
by wycats 17y ago
Rails default scaffolding and routing absolutely do use the full REST design, supporting both PUT and DELETE as well as inbound XML and JSON payloads
538.
Library Management Gets an Update in Rails 3(railsdispatch.com)
5 points by wycats 17y ago|1 comments
539.
Rails and Merb Merge: ORM Agnosticism (5 of 6)(engineyard.com)
47 points by wycats 17y ago|8 comments
540.
by wycats 17y ago
foo()() doesn't seem better than foo.call

More ›