.net
Out of context: Reply #3
- Started
- Last post
- 14 Responses
- madirish0
hey seed. i agree w/ you.... but also feel the vast majority of those decisions are based on a pre-existing 1) network architecture, 2) contractual obligations making an MS solution sound most efficient. these are done (IMO) from the position of cost basis, rather than a system, needs, data basis.
for what we are calling a 'midsize' project, i cannot see a better solution than either php or python from my expereince. specifically python as it's range, flexibility, and power is unmatched. now, php is very robust as well, no doubt, but when/if the need is to integrate w/ legacy and/or 3rd party vendors and their DB's, python is unmatched. this can also be rolled over into online application development (if the future of the dev sees that) and connecting with other systems outside the org.
truly though, any developer that says OS tech cannot match a .net solution is full of shite. they are a dyed-in-the-wool M$ head if that is the case and have drunk the kool-aid.... ;)