Programming thread

Could someone explain what LINQ and ASP.NET are used for in C#?
LINQ is standardized way of querying structured data, whether it comes from some kind of abstract data structure in-memory, a file, a database etc. It's usually used for databases though and it gives you a portable way to query data no matter what your underlying database is.

ASP.NET is the standard framework for web applications in C#. It does things like MVC, dependency injection, cloud configuration etc.

Basically if you're a backend web dev in C# land, you'll be writing web services in ASP.NET and using LINQ in those codebases to talk to some kind of persistence layer like a database.
 
Last edited:
LINQ is standardized way of querying structured data, whether it comes from kind of abstract data structure in-memory, a file, a database etc. It's usually used for databases though and it gives you a portable way to query data no matter what your underlying database is.

ASP.NET is the standard framework for web applications in C#. It does things like MVC, dependency injection, cloud configuration etc.

Basically if you're a backend web dev in C# land, you'll be writing web services in ASP.NET and using LINQ in those codebases to talk to some kind of persistence layer like a database.
Thanks man
 
And I'll need to find a For Retards guide on generics and Optional<T>, because it's just better to not trust myself to not make stupid mistakes all the time. And unit testing (because not taking this opportunity to try to learn it is dumb).
Once you've messed around with Java for a few weeks give Kotlin a try.

There's a whole tutorial where you have to make unit tests pass, so you get to see how they're written and stuff.
 
  • Like
Reactions: pursuitsnail
Once you've messed around with Java for a few weeks give Kotlin a try.

There's a whole tutorial where you have to make unit tests pass, so you get to see how they're written and stuff.
I definitely second Kotlin for anything new you're writing on the JVM. Java still has some advantages in terms of raw performance, but kotlin makes writing retard-proof code a breeze. And it also filters low-tier pajeets so that's a bonus.
 
LINQ is standardized way of querying structured data, whether it comes from some kind of abstract data structure in-memory, a file, a database etc. It's usually used for databases though and it gives you a portable way to query data no matter what your underlying database is.

ASP.NET is the standard framework for web applications in C#. It does things like MVC, dependency injection, cloud configuration etc.

Basically if you're a backend web dev in C# land, you'll be writing web services in ASP.NET and using LINQ in those codebases to talk to some kind of persistence layer like a database.
So basically html, css, and JavaScript are used for front end stuff and LINQ and ASP.NET are used for backend stuff right?
 
So basically html, css, and JavaScript are used for front end stuff and LINQ and ASP.NET are used for backend stuff right?
Not a C# programmer, but it looks to me like LINQ is a functional interface for abstracting away query languages, your ORM just needs to implement IEnumerable and you can use it. Back in university we used C# and I remember just using LINQ as the map/filter/reduce (Select/Where/Aggregate) functional apis of that language, coz all the generic collection data structures implement IEnumerable too.
 
So basically html, css, and JavaScript are used for front end stuff and LINQ and ASP.NET are used for backend stuff right?
Basically, although Javascript can be used to write back-end services using something like node+express.js and I'm pretty sure ASP.NET can still do dynamic HTML generation even though it's not as popular these days.
 
Basically, although Javascript can be used to write back-end services using something like node+express.js and I'm pretty sure ASP.NET can still do dynamic HTML generation even though it's not as popular these days.
while ASP.NET can do dynamic html generation, I would prefer to use Blazor for generating dynamic HTML content instead of ASP.NET. especially with webassembly, which makes it easier to integrate the front-end and back-end of the application.
 
  • Feels
  • Agree
Reactions: glow and Fcret
Any of you guys used Next.js? I've been gone off these threads for nearly a year and learned an absolute shit-ton about web development and am building my own forum using it.

If you guys have used Next.js, what are your thoughts compared to other frameworks?
 
Not a C# programmer, but it looks to me like LINQ is a functional interface for abstracting away query languages, your ORM just needs to implement IEnumerable and you can use it. Back in university we used C# and I remember just using LINQ as the map/filter/reduce (Select/Where/Aggregate) functional apis of that language, coz all the generic collection data structures implement IEnumerable too.
It can be used in this way but this is not an excuse to not know SQL as frequently the generated SQL for complex queries is utterly bizarre despite being logically correct and can result in unexpected performance problems. I haven't used EF in a while but a few years back almost any performance problem was invariably caused by some demented sub-sub-sub query generated by EF and it had to be rewritten as regular SQL. My current team violently opposes ORMs and while I think they can still save some time, especially in DB migrations I can't deny that we just don't have problems of this type because everyone must know SQL to a strong level to be able to contribute.
 
It can be used in this way but this is not an excuse to not know SQL as frequently the generated SQL for complex queries is utterly bizarre despite being logically correct and can result in unexpected performance problems. I haven't used EF in a while but a few years back almost any performance problem was invariably caused by some demented sub-sub-sub query generated by EF and it had to be rewritten as regular SQL. My current team violently opposes ORMs and while I think they can still save some time, especially in DB migrations I can't deny that we just don't have problems of this type because everyone must know SQL to a strong level to be able to contribute.
I typically go back and forth. For like 90% of my database shit I'll use an ORM but there's a few method calls where I'll handroll SQL if it's particularly gnarly and I know Spring JPA is going to shit itself.
 
  • Like
Reactions: PedoSec
Once you've messed around with Java for a few weeks give Kotlin a try.

There's a whole tutorial where you have to make unit tests pass, so you get to see how they're written and stuff.

I definitely second Kotlin for anything new you're writing on the JVM. Java still has some advantages in terms of raw performance, but kotlin makes writing retard-proof code a breeze.
TY guys! I'll definately look into Kotlin when I'm ready to dip my toes into something a little different- especially when that flavor of different can help protect me from my own stupid. Right now a lot of my retard problems likely stem from trying to treat a hashmap as if it were a database. After playing around with Junit to get the gist of unit testing, it'll probably be best if I just bite the bullet and dive into SQL.

And it also filters low-tier pajeets so that's a bonus.
Being a low-tier amerimutt, I'm not sure I'm any less retarded or obnoxious.
 
Oh. I mostly assumed the retraining to be application developers industry was a thing because it was just easier than fucking around with visas.
You have already demonstrated you are not as retarded or as obnoxious.
Low-tier pajeets, which are all too common, lie about their capability and rely on these lies to get anywhere. Ask them to do anything without copying and pasting from the internet and they melt down. You will rarely find a pajeet techy with desk references or bookmarks to documentation.

It's mind blowing how inept they are all while saying they can do anything anyone asks of them. They will say they know languages while having never heard of them.
 
Oh. I mostly assumed the retraining to be application developers industry was a thing because it was just easier than fucking around with visas.
Large corporations love H-1Bs because they can hold the threat of deportation over their heads.

Yeah were you thinking about complaining, Rajiv? You'll be back in the slums of Mumbai and we'll just find another Rajiv.
 
You will rarely find a pajeet techy with desk references or bookmarks to documentation.
Speaking of, how useful do you find desk references? Personal copy useful, or office copy useful? Reference booklets for stuff like SQL, bash, powershell and maybe Python seem like they'd be handy regardless of the language you're working in.
 
Speaking of, how useful do you find desk references? Personal copy useful, or office copy useful? Reference booklets for stuff like SQL, bash, powershell and maybe Python seem like they'd be handy regardless of the language you're working in.
I like having them but realistically I peruse through them, learn some things and rarely dig into them for something in the moment. Do whatever works for you, documentation being online is plenty if the documentation doesn't suck.
 
Being a low-tier amerimutt, I'm not sure I'm any less retarded or obnoxious.
The true low-tier pajeets have absolutely zero fucking humility and will be dangerously incompetent while still pretending to be better than you.

Speaking of, how useful do you find desk references? Personal copy useful, or office copy useful? Reference booklets for stuff like SQL, bash, powershell and maybe Python seem like they'd be handy regardless of the language you're working in.
I just google stuff. Books are generally much slower than online help and using them breaks my flow. The ideal is to reach the point where you don't need to reference anything much and can just work inside your development environment uninterrupted.
 
Back