Programming thread

  • 🔎 If you see an alert for analytics.usips.org, this is a self-hosted system I am running as a test. It is GDPR compliant and collects no invasive information.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
OOP is fucking retarded
I hate it so much.
The company I currently work at decided that we need to rewrite one of our projects to address some problems with it. This is a good thing to do, because the architecture of said project is retarded and broken.
But what I didn't know is that they also decided to scrap C and rewrite everything in C++ instead. And no orthodox C++, mind you. They use everything. Templates, multiple inheritance. Fuck this shit.

My ass has been burning ever since I was made aware of this fact, and there is no stopping it.
 
Last edited:
OOP is fucking retarded. It's just a way to add ceremony to plumbing properties to look busy.
No. Whenever I see these stupid OOP complaints by people, I know they don't understand it, or they are repeating shit off of YouTube (and I know the presentation you've watched).

I understand some go overboard with OOP and the abstractions. But OOP is often a good tool for modelling a problem.
Reminds me of this video that I’ve watched years ago.
https://youtube.com/watch?v=QM1iUe6IofM
It is another one of the videos where the "I've seen retards using it; therefore, it must be bad" type of video.
I vaguely remember watching it years ago.

Most of the developers making these sorts of videos normally work in particular domains where OOP is a bad choice or they've seen the end state of a poorly managed project.

The fact is that any language, pattern or whatever will be abused by morons.

I've been presented with 80,000 lines in every function procedural mess in archaic programming languages, and after about 4 days I found myself another job and walked out the door.
I've seen people abuse functional programming and make something that was super easy to understand in OOP difficult to understand because they added a bunch of new concepts.

People write shit code in every programming language.

If someone is doing loads of interviews/blog posts and other bollocks. They probably aren't actually writing that much code. So I don't take their opinion seriously.
 
Last edited:
Whenever I run into someone who says stuff like "everyone needs to learn Java first because I did and it sucks" (seen this a few times irl, usually coworkers or someone at a meetup/conference) I don't take them seriously. It sucks, but the especially shitty parts of it that you have to struggle with in CSE 111 don't teach you anything useful about computers or how to solve problems with them.

“What’s the best first language?” IMO most anything but java.
 
This is a based and correct fact.
And yet when people post code in a Based and Trad braces language, they add python-style indents for formatting, even though the natural thing to do would be to put the closing brace on the same level as the opening one. Nooooo, python-style triangles all the way.
 
I shudder whenever Java is mentioned.
Real talk: I'm nowhere near the smartest or most experienced in this thread, but I've been in and adjacent to programming jobs for >10 years now. This has meant that a few friends have asked me how to learn programming. Their reasons are varied: maybe $, maybe they interact with programmers at their job and want the nerds to like them, whatever. The one or two of them who wanted to learn Java wrestled with it: what's static? Why do you have to use a constructor for some things but not others? Point them at... basically anything else, and the problems they've got become meaningful.
 
OOP is fucking retarded. It's just a way to add ceremony to plumbing properties to look busy.
Objects are fantastic, OOP is indeed retarded.

No. Whenever I see these stupid OOP complaints by people, I know they don't understand it, or they are repeating shit off of YouTube (and I know the presentation you've watched).

I understand some go overboard with OOP and the abstractions. But OOP is often a good tool for modelling a problem.
see above

Real talk: I'm nowhere near the smartest or most experienced in this thread, but I've been in and adjacent to programming jobs for >10 years now. This has meant that a few friends have asked me how to learn programming. Their reasons are varied: maybe $, maybe they interact with programmers at their job and want the nerds to like them, whatever. The one or two of them who wanted to learn Java wrestled with it: what's static? Why do you have to use a constructor for some things but not others? Point them at... basically anything else, and the problems they've got become meaningful.
as a certified idiot, I think an OOP based language as a first one is the single worst choice you can make. It's almost impossible to learn other paradigms for a normal person after being poisoned by OOP, while the other way is relatively easy.
 
I really do indeed like having type enforcement for property bags, and bags of properties, and bags of methods and methods that are in bags.

But I don’t want squirrel to extend animal.

And when I actually do data transforms, I’m just fucking transforming data.

I’ve never had proper Martin Fowler level message passing or gang of four abstract proxy visitors help anything.
 
And yet when people post code in a Based and Trad braces language, they add python-style indents for formatting, even though the natural thing to do would be to put the closing brace on the same level as the opening one. Nooooo, python-style triangles all the way.
To protest Python, all my lines of code will be left aligned now.

I tell people to start with either Java or C. preferably C. Anything that isn't Python.
 
C with a de-compiler/assembly explorer doohicky would probably be ideal for people getting a proper how2computer education.

The point isn't endless gotcha bullshit or **(*(pointer to struct of pointer to member of pointer lbah blah blah))->niggerfaggot speed reading. The point is write code, get AST (and yes your hot, steamy sexpressions) get machine code. The point is "type is data width PLUS SEMANTICS".

You can even do things like "use data structures that manage their own memory" RIGHT IN THE C CODE!!!11one and compare that to having to malloc and free.

Instead of this people just get hung up on ideology.
 
To protest Python, all my lines of code will be left aligned now.
Everyone knows this is the best:

jxNOS5G.png
 
C with a de-compiler/assembly explorer doohicky would probably be ideal for people getting a proper how2computer education.
I also think that this would be aided by the use of a non-optimizing compiler to make the translation clearer.

It still had some niche uses, as previously mentioned Naughty Dog wrote the Crash Bandicoot Series and Jak and Daxter series in LISP for Playstation. I doubt they use it now because jeets Unreal Engine doesn’t use LISP. As for why I started learning it, someone was mentioning it in the thread and I wanted to see what the fuss was about. The discovery that my childhood games were written in LISP helped too.
Game Oriented Assembly Lisp was replaced with C++ around Uncharted 1, I believe for resource constraint reasons. I think they still use a kind of lisp today for data definition. Here's a video on the topic you might find interesting:
I know people have posted before about scheme to asm compilers which is what GOAL was doing with PS1 asm and where it derives the assembly in its name.
 
Be a real men and start with logic gates and flip-flops.
Who cares about this sissy SOFTware bullshit, real men deal with HARDware.
The Lord has bestowed upon us minds that are as sharp as razorblades and as bright as supernovas, and yet all we do is build demonic machines that do the blessed act of thinking for us.
Doomed and retarded we are.
 
Game Oriented Assembly Lisp was replaced with C++ around Uncharted 1, I believe for resource constraint reasons. I think they still use a kind of lisp today for data definition. Here's a video on the topic you might find interesting:
I believe main reason was SONY acquisition, and subsequent desire for all teams to share resources.
 
Back
Top Bottom