|
Thread Rules
1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution.
2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20)
3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible.
4. Use [code] tags to format code blocks. |
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 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.
I think the only logical conclusion is that Microsoft secretly bought your country. Are all cloud services running on Azure?
|
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.
.NET is an amazing framework that does pretty much have libraries for everything, from built-in webservers to the ability to set a single pin on the parallel port that you used to have on your PC 15 years ago. While it is held back by being not-that-good on Linux machines (though haven't checked that recently), it's still a very powerful framework.
C#, which is built around it, is also a very good language with all the features any modern language needs, packaged into a nice, short-but-readable syntax.
So C#/.NET is pretty much a better Java. Everything you can do in Java, apart from running smoothly on Linux, you can do better and more easily in C#. 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, but apart from that I'm not surprised that people are using it.
The only thing that is an abomination is ASP.NET.
Note that I say all of that as someone who very much dislikes Microsoft and Windows.
|
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
|
Hyrule18969 Posts
Biggest thing hurting .Net right now is its Linux compatibility. The few projects I've done (C# and VB.Net) were awesome.
|
Is this not appropriate for the thread, or does anyone have a good guide to reference for getting honest coding work online?
|
Hyrule18969 Posts
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 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
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 02:52 spinesheath wrote:Show nested quote +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 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.
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:Show nested quote +On March 19 2016 02:52 spinesheath wrote: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 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. 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?
Maybe check out what F# can do instead of C#?
|
On March 19 2016 03:05 Shield wrote:Show nested quote +On March 19 2016 02:52 spinesheath wrote: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 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. 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?
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.
|
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.
Okay, my first impression was contract/freelance sites often seemed dubious, but I'll dig deeper. Thanks.
|
On March 19 2016 05:23 spinesheath wrote:Show nested quote +On March 19 2016 03:05 Shield wrote:On March 19 2016 02:52 spinesheath wrote: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 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. 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? 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.
But the compiler knows what the type is at compile time, yet you can't do something like that:
void method<T>(T obj)
{
// can't call anything like obj.doSomething() while templates allow you to do it
}
Is this when you have to use reflection? Sorry if the method above doesn't compile, but I hope you get the idea.
|
On March 19 2016 06:57 Shield wrote:Show nested quote +On March 19 2016 05:23 spinesheath wrote:On March 19 2016 03:05 Shield wrote:On March 19 2016 02:52 spinesheath wrote: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 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. 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? 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. But the compiler knows what the type is at compile time, yet you can't do something like that:
void method<T>(T obj)
{
// can't call anything like obj.doSomething() while templates allow you to do it
}
Is this when you have to use reflection? Sorry if the method above doesn't compile, but I hope you get the idea.
I haven't used generics in a while, but IIRC you can do
void foo<T>(T obj) where T : SomeAbstractClass {
...
}
Syntax might not be completely correct, but you can define that T must have a specific interface or be derived from a specific class. If you don't know the type at compile time, then you can try casting it to that type or use reflection.
|
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.
No, you certainly don't use reflection here. As Morfildur said, you restrict the generic type parameter to a class, or better an interface and the compliler will allow you to call all the methods of the interface.
Obviously there is fairly little use in that if you only call a method of two on the interface and then don't return anything; you wouldn't need generics for that:
void Foo<T>(T t) where T : IBar { t.DoBar(); }
// is equivalent to
void Foo(IBar t) { t.DoBar(); }
However as soon as you return stuff or use the generic type parameter as a parameter for another generic type, things get more interesting:
// 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()); }
Notice that the last code example is stupid, I just needed an excuse to use a List<T> over an IEnumerable<T> because I think you can assign IEnumerable<Bar> to a variable of IEnumerable<IBar>, again covariance/contravariance shenanigans. Would have to check.
Anyways, in real C# code you don't need to write a whole lot of generics anyways, usually it's sufficient to have well designed interfaces.
|
On March 18 2016 20:31 Morfildur wrote:Show nested quote +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. ... 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...
The problem with Turkey is this: Everybody in Turkey would use node.js if they were going to be shackled to windows only and had to pay enormous amounts of licensing fees to Microsoft. Because IT'S FUCKING MICROSOFT DUDE. If Microsoft or Oracle built Titanic, my whole country would jump on that ship without thinking twice.
|
So, it seems this Monday I'll start working with projects written in ZF1. Checked it out online and boy, it's like traveling 10 years back in time... Absolutely crazy. And it seems they didn't even have hydration strategies for models back then. Will be hard to get used to this ancient way of doing things 
|
I'm working on an IoT project, started with the server side of things and trying to use MQTT with nodejs and boy writing unit tests has never been any harder. I fucking get lost in my own code despite my best effort (check the code for time after time after time, I don't understand shit but somehow it works without any error whatsoever, all my tests pass, but whenever I want to add new things, I check out my entire codebase just to have a slightest clue about the FUCK I've been doing. It's fucking impossible to keep track of what thing subscribes to what and publishes on what and gets callback on what and shit. I'm fucking going insane. Fuck this shit.
|
Is that because you ran into callback hell?
|
Hey does anyone know of a good place (online) to do some C++/Javascript programming practice?
I have a job interview next week so I want to brush up.
Also if anyone has some tips for a programming interview I'm all ears. They're going to have a practical set-up where I can demonstrate my coding abilities. Anyone know what I should expect?
|
|
|
|
|
|
EPT
