matt_yoho

4 ms·

1.
by matt_yoho 14y ago
The Rails framework is written to reload (reevaluate) most application code between requests in development mode, so that changes during active dev are reflected. This is not the (default) behavior in production.
2.
by matt_yoho 14y ago
This is an example of a Socratic Dialog[1], and relies on metaphor. It's in that way a piece of art useful as a teaching tool, but as such it trades some precision for the end effect. 1. http://en.wikipedia.org/wiki/Socratic_dialogue
3.
by matt_yoho 14y ago
> Omitting the return statement is a good thing? How do you know if this method even returns anything? In Ruby, all methods return the value of the last expression executed in the method. > .size could be a method that doesn't retur
4.
by matt_yoho 14y ago
A combination a bootstrapping issues (arguably minor, of course) and the minor complexity of building the package, plus the workshop-friendly approach contribute to the zip directory distribution method.
5.
by matt_yoho 15y ago
Right, this would be very valuable as a teaching resource, and thus indirectly valuable to the, I believe, sizable chunk Ruby/Rails community at large who enjoy doing it as their "day job".
6.
by matt_yoho 15y ago
Though I'm quite thankful Engine Yard chose to fund his work, I'd categorize doing so as an investment than a generous act. Nothing wrong with either, of course.
7.
by matt_yoho 15y ago
I read the accent as being on his track record of delivering on open source software efforts. In other words, he's demonstrating the soundness of investing your money toward his goal. Regardless, count me in.
8.
by matt_yoho 15y ago
I interpret the statement as being closer to "function pointers are under-discussed".
9.
by matt_yoho 15y ago
Not really disagreeing with your contention, but there are probably different applicable definitions of "failure" here. It could be argued doing what one loves is inherently successful, etc. (I'm sure you're familiar with the sentiment.)
10.
by matt_yoho 15y ago
The reply seems immature from the perspective of project maintenance.
11.
by matt_yoho 15y ago
Do note, as is mentioned in the comment Thread for the gist, that Fibur is also fully Ruby 1.8 compatible...
12.
by matt_yoho 15y ago
I think you're being downvoted for poor reading comprehension and for the entirely unnecessary and contextually-inappropriate use of the term "bitching".
13.
by matt_yoho 15y ago
So perhaps it would be generally beneficial to simply oppose online "dickery" and bullying across the board, particularly in cases where there's a component of implied threat beyond the virtual world. "Men are treated unfairly" is an unsymp
14.
by matt_yoho 15y ago
"I am honestly surprised that she let her real email address be publicly available anyway" This is called "blaming the victim". It is bad, and you should consider researching it.
15.
by matt_yoho 16y ago
Bald-faced pimping of a resource the company I work for, EdgeCase, put together as well: http://gitimmersion.com/
16.
by matt_yoho 16y ago
This isn't really true, particularly with Rails 3. If you don't want to use the ActiveRecord database patter, don't use the default ActiveRecord ORM that ships with Rails. Drop in DataMapper instead, and use whatever pattern you wish. Rails
17.
by matt_yoho 16y ago
All of this "Rails makes you do X; or, well, you can do Y" is conflating Rails as a framework with Rails' ActiveRecord library, which is the default ORM. Since Rails 3, you can easily, and effectively transparently, use DataMapper instead,