enough code to shoot yourself in the foot
my main litmus for selecting programming languages is ‘tool best fit for the job’
- within BW we use Flex, AJAX via Dojo, Groovy/Grails ( i hope soon jRoR).
this turns into a problem when people don’t project deep enough their overall needs and go for quick, early, visible gains and face pitfalls later
this is what i call dirty coding and that’s how inadequate languages (like PHP or VB) thrives on, easy for individuals to pick up, meet early needs, skip time-wasting steps like patterns, abstraction, reuse and domain design.
having said that, frameworks have a huge overhead to overcome
- the learning curve < what? i just want to copy-paste code scraps>
- cost and use of extensive toolsets < what? all i should need is a text editor>
- adhering to conventions, configurations < no. everyone else should adhere to my cowboy style>
People -being people- don’t see beyond visible benefits until they eventually have to and pay eventually a larger price - entrenched software