Go vs Node.JS vs PHP + Iris vs Express vs Laravel

You'd choose .NET core over Java, Node, Go or Python for cross platform development? Well I be damned.

And if you are the architect of the organization who's cock is on the block if this project fails (in other words - your the one held responsible and possibly fired should there be a fsck up), would you instruct your Dev team to use .NET Core over the others?

Worked with a couple of languages, regularly do tutorials. .Net seems always like a mission to work with. It seems you always have to download some or other fix.
 
I prefer Node or Java for cross platform
Just because you prefer Node or Java doesn't mean it will work for any and every project. Sometimes there is other options that works better. If you are just planning on implementing a simple app to capture a few text fields, node and java are both a waste of resources.

The question was "would you use the programming language if your head was on the chopping block if it failed?"
 
Worked with a couple of languages, regularly do tutorials. .Net seems always like a mission to work with. It seems you always have to download some or other fix.
Depending on the objective, .net will work fine. I'd however stay far away from .net core for now. It is still in its early stages. It will probably evolve to something that is awesome, but for now, the future of .net core is basically unpredictable.
 
Just because you prefer Node or Java doesn't mean it will work for any and every project. Sometimes there is other options that works better. If you are just planning on implementing a simple app to capture a few text fields, node and java are both a waste of resources.

The question was "would you use the programming language if your head was on the chopping block if it failed?"
No the question was would you use .net core for cross platform over the above mentioned languages and my answer was no I most certainly would not.
 
No the question was would you use .net core for cross platform over the above mentioned languages and my answer was no I most certainly would not.
I expanded on the question. It's all well and good for a dev with nothing to lose to make a quick decision on what he'd prefer to use, but when your head is on the chopping block things change.

When you are in that position you're not looking at it through the eyes of a dev that wants to use exciting new stuff and have the luxury of shrugging his shoulders and pointing fingers when scht hits the fan. Now you're looking at it through the eyes of somebody concerned with the future of the tech, support, available skills should a walkout happen, the stability and track record of the tech.

Suppose the size of one's gonads come in to play as well :p
 
Last edited:
I expanded on the question. It's all well and good for a dev with nothing to lose to make a quick decision on what he'd prefer to use, but when your head is on the chopping block things change.
Indeed. Once the pressure is on you to make it happen, the way you make the decisions change.
 
I expanded on the question. It's all well and good for a dev with nothing to lose to make a quick decision on what he'd prefer to use, but when your head is on the chopping block things change.

When you are in that position you're not looking at it through the eyes of a dev that wants to use exciting new stuff and have the luxury of shrugging his shoulders and pointing fingers when scht hits the fan. Now you're looking at it through the eyes of somebody concerned with the future of the tech, support, available skills should a walkout happen, the stability and track record of the tech.

Suppose the size of one's gonads come in to play as well :p
Hence Java.
 
Depending on the objective, .net will work fine. I'd however stay far away from .net core for now. It is still in its early stages. It will probably evolve to something that is awesome, but for now, the future of .net core is basically unpredictable.

The golden rule about new tools, tech. NEVER, NEVER, NEVER BE THE FIRST TO USE IT. Wait for the others to sort out its issues first.
 
So this thread has run its course, obviously.
 
As long as we can all agree that PHP sucks it's all good...
 
giphy.gif
 
Top
Sign up to the MyBroadband newsletter
X