There are a lot of good responses here already, especially with respect to ROI, so here's just a different way to look at the situation:
Has your employer considered the LONG TERM licensing costs for Windows server several years down the road? Sure they might be buying licenses anyway, but as load and demand scale upward (depending on the size/ nature/audience/goals of the project), licensing cost does too. This is where FOSS really shines: cheap initial implementation, serious cost savings down the road. Another point: a TRULY purist technology stack, these days, is pretty much just a pipe dream, at least in my opinion. By getting fanatical about "stack A" vs "stack B", your employer is missing out on the leverage that a very cutting-edge and capable community driven FOSS stack can provide. And aside from that, you can really make your company's internal or external infrastructure incredibly fragile by putting all your eggs in one basket, especially that of a for-profit corporation who has proven time and again, by shipping crashtastic and buggy software, that their bottom line is more important than their customer's well-being. FOSS doesn't have the same conflict of interest. Additionally, it's certainly true that Rails is ONE of the most mature, tried and tested frameworks in existence - period. I don't know that we can hold ASP. NET MVC in the same regard. (Not saying it can't "hang" with the cool kids - just that I think that argument would be a much harder sell, even to some apparent Microsoft fanbois.) Good luck man! Unfortunately, it sounds like you may need it. :-) On Mar 29, 11:59 pm, Michael Pavling <[email protected]> wrote: > On 29 March 2011 19:57, Alpha Blue <[email protected]> wrote:> > > .. we strongly encourage the use of Microsoft IIS and using a product in > > the .NET family for the code base.. > > encourage != enforce > So say "We took your encouragement into consideration, but in the > absence of any suggested, measurable benefits, we've stayed with RoR" > > > ASP.NET and ASP.NET MVC - I can't > > stand them. I refuse to code in them. > > ah... well, you might need to update your CV and start looking for a > new job then, because if your company is orientated on .Net, and you > "refuse" to code in it, then you might be in the wrong company... -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
