- Did no deliver the promise of code reuse, reusable component marketplaces and frameworks that would take the drudgery out of programming
- Inability to communicate intent clearly amongst themselves
- Insisting on intimately encapsulating behaviour and mutable state, and by having paid inadequate attention to concurrent, have left the industry vulnerable to what some have dubbed an ill-conceived "Neo-Functional Renaissance"
- Eschewing static type information forcing implementers to sacrifice performance in the name of linguistic simplicity
- High skill and education required to adequately craft state-of-the-art code to a level that is beyond what the industry is prepared to pay for
In the accused box are the following:
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.