980 karma · joined June 16, 2011
case
when user.blacklisted?
# ... code ...
when grouper.full?
# ... code ...
# ... and so on ...
endThe first is what I'll term the "Classic School" or "DHH School" characterized by full-blown utilization of all Rails magic such as AR/AC callbacks, pretty skinny but not obsessively skinny controllers, an eschewance of service objects and more.
The "Emerging School" relies less on some aspects of Rails magic, and introduces patterns like services/interactors/DCI and seems to be more focused on building a domain models which attempt to be less coupled to the framework.
I think the Grouper folks are in the second camp given their previous blog post about interactors which showed up here on HN. Also, I think the desire to encapsulate authorization into a reusable object seems slightly more in the spirit of the emerging school.
What I find odd is that they'd offer a solution for authorization which is so bound up in Rails magic. It seems to me authorization is really part of the domain model and as such you would expect to find that code in whatever gets called by the controller (which I would expect to be something like an interactor, but in this blog post is just plain old Rails code.)
* http://blog.chromium.org/2013/12/keeping-chrome-extensions-s...
1. Beautiful things 2. Things with emotional value 3. Functional things 4. Everything else
Here's a link to the Scripting News article which has got a link to Sterling's talk. Listen to the whole thing!
http://scripting.com/stories/2009/10/21/bruceSterlingAtReboo...
Apple Stores are starting to suffer the same problem as most wireless provider stores: It's just too hard to walk in and quickly buy the thing you want.
Anyway, he seems to have fixed whatever was wrong.
I share the same experience.
Hello! We're looking for bright, friendly and committed people to come help us do things like:
* Provide near-realtime analytics from 100,000s of IMAP mailboxes. * Decouple our large Rails app into smaller services. * Scale our system by an order of magnitude. * Whatever you think we should be doing.
We use Ruby, Rails, Sinatra, Postgres, Mongo, Redis, jQuery, backbone and more. YOU DON'T NEED TO KNOW ANY OF THAT, but you do need to be ready to figure it out on the job.
We're funded by Foundry Group and Google Ventures.
You can find details at the link below:
http://www.yesware.com/careers http://options-vs-salary.com
This is based on various blog entries I've read on the subject. http://www.launchbit.com/For example, in my (limited) experience, you have to draw the boundary between what's in Ruby and what's in C/C++ intelligently. If you're still doing most of your computation in C on Ruby Arrays and Hashes, you're not going to get much of a performance win at all.
I've done this before with Ruby and C. Two great tastes that go great together!
And each other.
Another such tool I've been thinking about would show you the relationship of the writer and quoted sources (people or institutions) to the material being covered.
For example, consider the case where spokesperson for a non-profit organization is quoted defending a particular industry. This tool might tell you that this person was once an executive at a for-profit corporation in that industry or have some other non-obvious relationship.
If anyone knows of anyone working on something like this, I'd love to learn about it.