Yes, it has, and it's always trending towards more complexity.
There's always hope for things to reverse course and get better. Ruby on Rails was a moment like this in web development history. Rails came at a time when things were unnecessarily complex and introduced a much simpler way, which people accepted. Rails' influence extended far beyond Rubyists and introduced design patterns that became part of web frameworks in every language.
Rails had a bigger impact than anyone cwould have anticipated from a quirky new framework in an unknown academic language at that stage in the industry's maturation. Computer scientists had expected that by 2000 every task in software development would be catalogued and assigned a standard labor estimate like in auto repair. It was highly improbable that an entirely new paradigm would take hold after that. I think part of this was because of the technical ingenuity of the solution, part of it was because of the charm and personality of the Ruby community, and part of it was synchronicity with other movements like Web 2.0 and Agile.
It takes leaders with strong personalities who can attract people and present new ideas in a way that people will accept. They also have to have insight into what people actually need in their time and willing to compromise.
Comments
Yes, it has, and it's always trending towards more complexity.
There's always hope for things to reverse course and get better. Ruby on Rails was a moment like this in web development history. Rails came at a time when things were unnecessarily complex and introduced a much simpler way, which people accepted. Rails' influence extended far beyond Rubyists and introduced design patterns that became part of web frameworks in every language.
Rails had a bigger impact than anyone cwould have anticipated from a quirky new framework in an unknown academic language at that stage in the industry's maturation. Computer scientists had expected that by 2000 every task in software development would be catalogued and assigned a standard labor estimate like in auto repair. It was highly improbable that an entirely new paradigm would take hold after that. I think part of this was because of the technical ingenuity of the solution, part of it was because of the charm and personality of the Ruby community, and part of it was synchronicity with other movements like Web 2.0 and Agile.
It takes leaders with strong personalities who can attract people and present new ideas in a way that people will accept. They also have to have insight into what people actually need in their time and willing to compromise.