In his article “Software in 2014” Tim Bray says about the present state of front-end development:<\/p>\n
\nThus, for ac\u00adtu\u00adally build\u00ading ap\u00adpli\u00adca\u00adtions, you\u2019re going to have to pick a higher-level frame\u00adwork. There are lots of them and they com\u00adpete vig\u00ador\u00adously, it\u2019s easy to poke around the Web and find knock\u00adouts and cage matches; one good high-level com\u00adparo is Rich JavaScript Ap\u00adpli\u00adca\u00adtions \u2013 the Seven Frame\u00adworks (Throne of JS, 2012)<\/a> but wait it\u2019s eigh\u00adteen months old thus prob\u00ada\u00adbly now wrong, which is a symp\u00adtom of the prob\u00adlem. \u201cWhat prob\u00adlem,\u201d you ask, \u201cchoice is good, right?\u201d It is, but this isn\u2019t an or\u00adderly choice, it\u2019s a Cam\u00adbrian Ex\u00adplo\u00adsion. I\u2019m sure the soft\u00adware arche\u00adol\u00ado\u00adgists of 2113 will enjoy study\u00ading it, but it\u2019s a prob\u00adlem.<\/p>\n
ongoing by Tim Bray \u00b7 Software in 2014<\/a>.<\/p>\n<\/blockquote>\n
I completely agree, right down to the term “Cambrian Explosion”, and I ranted a bit about it in one of the few posts I wrote last year<\/a>. Client-side development is a scary mess right now, where almost every choice you make stands a chance of blowing up in your face a year down the line.<\/p>\n","protected":false},"excerpt":{"rendered":"
In his article “Software in 2014” Tim Bray says about the present state of front-end development: Thus, for ac\u00adtu\u00adally build\u00ading ap\u00adpli\u00adca\u00adtions, you\u2019re going to have to pick a higher-level frame\u00adwork. There are lots of them and they com\u00adpete vig\u00ador\u00adously, it\u2019s easy to poke around the Web and find knock\u00adouts and cage matches; one good high-level … <\/p>\n