Hacker News new | ask | show | jobs
by roel_v 3770 days ago
If your project depends on saving $500 on a computer (the one thing you really need to do you job, as opposed to say a carpenter who needs $5000 in equipment just as a basis), is that project really worth doing?
3 comments

You willfully mixed up and misrepresented the 2 paragraphs of my post. I hope that wasn't with malicious intent, so I will clarify.

The first paragraph dealt with the 'poor college student in Eastern Europe' side of doing a project, where every dollar counts and must be scraped for. In that world, going for .NET was unheard of, but the situation is slowly changing with VSCode and vNext.

As for the second paragraph, even well-funded projects have limits. Sure, let's say the limit for cost is 50k EUR with 300 EUR/month expected hosting costs. How happy will your client be when your cloud provider changes their pricing scheme and hosting cost is now 10-100x as large? Or when the requirements change and you need to buy some $EXPENSIVE_PLUGIN for that and you are locked in with your technology stack to one provider?

Mainly speaking: why should someone make a company and build some website and fill applications and all that (always with the high possibility of rejection), when you can just do 'apt-get install <technology-stack>' or as an alternative, git-clone-configure-make-sudo-make-install for the same thing? It's all about barriers to entry.

No, but building your project in a language that currently costs 2-10x per production instance with licensing/hosting costs thrown in sure as heck can.

I love C# compared to Java but I write more Java today because I hate Windows and want no part of automating cloud deployments to Windows target servers. So maybe one day when (soon?) .Net Core gets production ready in Linux I'll make the jump- but I'm not going to vastly increase my hosting costs for a language when all of the others can be done on a cheaper, more well suited system.

x 5 developers, + unknown extras with an enterprise giant...

There's a good reason you don't hear of many new startups running on a .NET stack.