The Big Programming Thread - Page 710

On March 18 2016 19:45 Djagulingu wrote:
Lately, I have been seeing a lot of "the company does its best to keep up with the cutting edge technology" and then I proceed to see that the aforementioned company uses .NET for everything.

Is there something that I don't know about .NET which makes it a super special awesome technology that is so super special awesome that the entire COUNTRY is using it? Does it have a good performance? Scalability? Platform agnosticity (it was windows only until very recently as far as I know)? Does it have libraries for practically everything? Is it suitable for data applications like Python or R? Or IoT? Or high frequency trading? Or any other application that needs tools to cover for an extremity? Is .NET jack of all trades, so like you can say "when in doubt, use .NET"?

I fucking sit here and wonder... why would all the companies that do software development in my entire dear country, which shares its name with a bird, use .NET over... everything else.

Then I check for job postings outside of my country and I don't see a single company looking for someone who can code in .NET (that's a bit overstatement but for x number of postings on .NET I saw, I also saw 2x number of postings on node.js, 3x on PHP, 5x on each of java and swift and fucking 10x number of postings on ruby on rails).

Some part of this is horribly wrong and I wonder which part that is.

On March 18 2016 21:12 Manit0u wrote:
I have to second Morfildur here. Despite my deep-running hatred for MS and Windows I have to agree that C# is a really nice language (did one project in it and it was a very pleasurable experience). .NET is pretty awesome too, will be much better in the future when more libraries are open-sourced: http://radar.oreilly.com/2015/06/net-open-source.html

On March 19 2016 02:52 spinesheath wrote:

C# has its downsides too (mainly because C#1.0 didn't have generics and some issues that originated from that still run deep in the language), but overall it is a good one among the pool of C++-like languages. Also I feel like Microsoft has been making a lot of good decisions in the .Net/VisualStudio area lately, so the future seems bright.

On March 19 2016 03:05 Shield wrote:


C# is a nice language indeed. However, I find generics so more restricted than templates in C++. Is it me or you sometimes can't call methods because T is just not resolved?

On March 19 2016 03:05 Shield wrote:


C# is a nice language indeed. However, I find generics so more restricted than templates in C++. Is it me or you sometimes can't call methods because T is just not resolved?

On March 19 2016 02:08 tofucake wrote:
There's not really a guide I know of. Put your resume up on job sites, try WhiteTruffle.com, try temp and recruitment agencies.

On March 19 2016 05:23 spinesheath wrote:

Templates are very different from generics. Templates can do pretty much anything geneics can do, but templates are also turing complete at compile time, so you can do much much more with them. The downside is that templates are also a lot more complex. C# - as an easy and convenient to use language - is better off without them, imo.

Sometimes I do miss templates in C#, but usually generics will do the trick just well enough. Occasionally you'll need to resort to using reflection, for example if you have to call a generic with a type parameter that is only known at runtime.

void method<T>(T obj)
{
    // can't call anything like obj.doSomething() while templates allow you to do it
}

On March 19 2016 06:57 Shield wrote:
Is this when you have to use reflection? Sorry if the method above doesn't compile, but I hope you get the idea.

void Foo<T>(T t) where T : IBar { t.DoBar(); }
// is equivalent to
void Foo(IBar t) { t.DoBar(); }

// this keeps the original type of t in the return value
// without generics it would be restricted to IBar
T Foo(T t) where T : IBar { return t; }

// You can't assign a List<Bar> to a variable of type List<IBar>
// covariance/contravariance shenanigans, I never quite remember the details
// So we need to use generics here
void Foo(List<T> t) where T : IBar { t.Reverse(); t.ForEach(b => b.DoBar()); }

On March 18 2016 20:31 Morfildur wrote:

...
It surprises me that Turkey is using it, since I didn't think that you'd have so much spare money that you could buy all the Windows licenses
...