Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Technology choices for the majority of programmers are often not based on technical merit alone, but rather are based on historical influence (legacy systems, existing libraries, interoperability, et cetera,) managerial perceptions (nobody gets fired for picking Java, it is too hard to hire good Rubyists, the smalltalk vendors are unstable, et cetera) and cost.


What does "technical merit" even mean, without a context like the problem to be solved and the ressources available to solve it?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: