Why .NET? Why Java? Why Ruby? Why Whatever?

I came across a post the other day that asked Why .NET?, written from the¬†viewpoint of why, as a small startup, they used .NET when most startups tend to avoid that platform. The author goes on to give reasons for their decision, which is important given one of their principles is open source over closed source (you couldn’t say that about .NET a decade ago).

Reading that post got me wondering in the broader sense about why this still matters so much to some people. I mean, it’s been a long time since I’ve worked somewhere that was dedicated to a single technology stack, and even then there were always cracks and pockets of other “non-standard” technology trying to make its way into the mix.

We all have our preferences and comfort zones, but to only use one technology stack is an outdated notion, especially in this day and age where technology changes so quickly.

Naturally this got me thinking about our current technology stack at work:

.NET/C#
LESS
ASP.NET MVC
ASP.NET Web API
RabbitMQ
AWS EC2
AWS Elastic Beanstalk
AWS S3
AWS RDS
WordPress
PHP
MySQL
SQL Server
REST
JSON
CruiseControl.NET
PowerShell
JIRA
Subversion (soon to be git)

And this doesn’t include some of the things on our radar: Docker, SignalR, Lucene, AWS SQS, AWS VPC, React, and Node.

Like life in general, as technologists we should always have an open mind when it comes to things outside our norm. It’s that approach that allows us to come up with more cost effective and innovative solutions.

Featured image: Some rights reserved by Iman

 

Leave a Reply

Your email address will not be published. Required fields are marked *