What drives me insane about this discussion is fact that people are trying to shoehorn features into Rails to support stuff like this and keep their libraries. If you have a desire to do socket based work in ruby, its doable, but only if you drop the Rails stack.
Of course they are. We’re very good at loss aversion.
This is the trap of worse is better: all the hacks, workarounds and minor bug fixes are preferable because we already have this thing, and we need to keep it going.
There’s no way libraries could have anticipated the way WebSockets breaks things in the Ruby world. Most major languages, in fact, are being split at the library-level to handle the demands of concurrency well (or they foist it on you, like node does).
What drives me insane about this discussion is fact that people are trying to shoehorn features into Rails to support stuff like this and keep their libraries. If you have a desire to do socket based work in ruby, its doable, but only if you drop the Rails stack.
Of course they are. We’re very good at loss aversion.
This is the trap of worse is better: all the hacks, workarounds and minor bug fixes are preferable because we already have this thing, and we need to keep it going.
There’s no way libraries could have anticipated the way WebSockets breaks things in the Ruby world. Most major languages, in fact, are being split at the library-level to handle the demands of concurrency well (or they foist it on you, like node does).