Magmatron Alpha

izs:

As usual, this year’s JSConf did not fail to deliver. The parties, the location, the talks, the food, it was incredible. Chris Williams (and the rest of the JSConf family) really put together an incredible event.

By far, the most controversial talk was Brian Ford’s “Is Node.js Better”. I must…

(Source: chicwriter)

daltoncaldwell:

The Stanford Prison Experiment is one of the two most famous and influential psychological experiments ever conducted. (It’s thanks to this disastrous experiment that researchers everywhere have to fill out Human Subjects Approval forms to conduct any kind of experiment on people.)

In the…

yongfook:

In direct response to: http://designerfund.com/infographic

I’ve created products / services in the past that have garnered praise for their design. I love good design and I am good at design. But I’ve never called myself a designer.

Here’s my pitch. This talk of designers as the new…

thechangelog:

Sinatra 1.3.0 is out with two big news items. The Chairman is now traveling with his own band. Sinatra Contrib, the community-sourced collection of extensions, is now versioned with Sinatra itself, ensuring compatibility. Sinatra Contrib provides some niceties on top of Sinatra for common tasks like config files, content_for, respond_with and other things you might miss from Rails.

Perhaps the bigger news is that Sinatra gigs can be streamed. No matter if you run evented servers like Thin, Rainbows! or Ebb or sequential servers like Unicorn, Passenger, or Mongrel, you have a single API:

get '/' do
 stream do |out|
   out << "It's gonna be legen -\n"
   sleep 0.5
   out << " (wait for it) \n"
   sleep 1
   out << "- dary!\n"
 end
end

Of course, you’ll need an evented server to keep connections open to things like:

set :server, :thin
connections = []

get '/' do
 # keep stream open
 stream(:keep_open) { |out| connections << out }
end

post '/' do
 # write to all open streams
 connections.each { |out| out << params[:message] << "\n" }
 "message sent"
end

Smaller but just as cool changes include:

• request.accept? for Accept headers
• informal?, success?, redirect? and client_error? based on HTTP status code.
• Support for If-Unmodified-Since header

Check out the official announcement or the changelog for a complete list of updates. Congrats to Konstantin Haase and the other contributors who made this happen.

izs:

It’s fairly common these days to think of JavaScript as a sort of “assembly language for the web”. After all, it’s the language that is natively supported by web browsers, making it the most widely deployed runtime in history. With Node, we have a very relevant general purpose non-browser stack…