Three years after Rails was introduced in 2005, InfoWorld asked whether it might the successor to Java.
That didn’t happen. So this week InfoWorld “spoke to current and former Ruby programmers to try to trace the language’s rise and fall.” Some responses:
“Rails came along at the cusp of a period of transformation and growth for the web,” says Matthew Boeh, a Ruby developer since 2006. “It both benefited from and fueled that growth, but it was a foregone conclusion that it wasn’t going to be the only success story.” Boeh recently took a job as a senior staff software engineer at Lattice, a TypeScript shop. “You could say that Ruby has been a victim of its own success, in that its community was a major driving force in the command-line renaissance of recent years,” he says. “In the early ’00s it was introducing REPL-driven development to people who had never