Here in Morocco, the dominant web technology is... PHP. Tadaaa ! The're not even considering Raills or anything more 'advanced' for that matter.
It's really an evolution ladder. People got on the 'framework' 'one fit for all band after trying things like PHP, JSP, ... and now realizing that it does not solve the issues they just leave. It will certainly happened with PHP and Rails. These solutions are geared toward some specific problem scopes. As soon as the business needs outrun what they can easily solve you are short of something else. The industry has been searching for a silver bullet solution for decades. In the early 80s, late 70s, CASE tools were suppose to be that bullet, (basic stuff in today's world, git, ant, ....). Open systems then picked up, blabla, .... None of that fully delivered their promises. Ever. They helped climb the ladder however. In small steps... And now we have these frameworks that supposedly can ease the pain in any circumstances. They do fill the role up to a certain glass ceiling, the unforeseen business needs that make them blow in pieces because they can't be easily stretched, twisted, bended, ... Each of these initiatives were motivated by software creation automating and supposedly shrinking the costs while trying to downplay the need for an essential ingredient... Us. Wetware. I think it's a mirage. Maybe the solution has been there for decades under our eyes. Human beings. Capable of assembling solutions grater than the sum of their parts. Capable of bending the software as needed to do new stuff instead of having to fully rewrite stuff because shoes are becoming to tight. In one word adapt. This assumes that you have components to build from and people that can compose them as needed. Not some kind of frozen approach in time to software development were roles are pre-assigned and any change outside of this limited scope becomes a challenge by itself. The 'structure' needed here has nothing to do with walls and concrete. We need brain power to tear down/recompose things and stop thinking that processes, normalization, herd tagging, etc can lead us to work more efficiently. Processes, conventions, ... may help but at a low scale. Not pushed by at the scale of the whole software industry like these days Variety is the key. Luc P. > On 03/05/2015 14:39, larry google groups wrote: > > The industry has been moving against frameworks for 15 years now. The > > peak of the monolithic framework craze was Struts, back in 2000. After > > that, people started craving something less bloated. That's why the > > whole industry was so excited when Rails emerged in 2004. Bruce Eckel > > summed up the sudden change of mood in his essay "The departure of the > > hyper-enthusiasts": > > > > http://www.artima.com/weblogs/viewpost.jsp?thread=141312 > > > > But after awhile, people began to feel that even Rails was bloated, > > which lead to the emergence of micro-frameworks like Sinatra. > > > > And then, continuing with the trend, we've seen the emergence of > > eco-systems, such as Clojure, that allow the trend to go further: > > Clojure supports such high levels composition that frameworks are no > > longer needed. And this is the direction the industry has been moving > > for the last 15 years. Clojure is simply out in front. Most languages > > don't allow this level of composition. > > > > The web development industry as reflected in job postings at > Indeed.co.uk is still dominated by the likes of Rails, Django, Laravel, > Zend, Symfony & Spring so I'm not sure how you've concluded that there's > been a 15-year trend towards composition. Ruby and Python have had > lightweight composable alternatives for many years but Rails and Django > still dominate. I'm not against the composition at all. I just think we > need more structured alternatives that we can at least brand and market > as well as teach to Clojure beginners. > > gvim > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Luc Préfontaine<lprefonta...@softaddicts.ca> sent by ibisMail! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
