Vlang

[slimeball]

Unfortunately coding body shops and other companies with developers will disagree because according to them if you can't OOP, you're worthless.

Unfortunately you couldn't be more right. OOP isn't the solution to everything...

 

[_kabal_]

OOP isn't the solution to anything

 

[cguy]

Unfortunately coding body shops and other companies with developers will disagree because according to them if you can't OOP, you're worthless.

You can write OOP code in C.

 

[semaphore]

You can write OOP code in C.

God it feels like we gonna be repeat ourselves like we did with Swa many years ago.

 

[PaulGherkin]

OOP isn't the solution to anything

Unfortunately you couldn't be more right. OOP isn't the solution to everything...

So before I left SA I had done a whole exhaustive job search.
I battled.
A lot of these software companies/service providers were enormously big on OOP, so if you can't explain in an interview what overloading is (even if you can do it in front of them) then you're stopped right there kthxbye, next please. I see this kind of arrogance a lot with the crowd who did comp.sci to the max, i.e. university level.
Recently I had a bit of an argument with one of them about Golang, and the thing is, we've been doing it a specific way from the start, and it works, it makes us a boat load of money each month and it's in production, but Mr-two-degrees (South African) wants to tell us it's wrong. Well, the developers of Golang beg to differ..
Where I am at, we're tired of class abuse in C++ which leads to code nobody wants to work on because it's so freaking difficult to understand and moreover, the whole OOP thing becomes an achilles' heel. With code as disposable as it is today, in 5 years what we do today would have been replaced.

I am going to tell you today, that folks like us, who rose up with C, and are great C programmers, we're looked down upon, and IDGAF anymore. The entire energy sector runs on C and baremetal C code, because C++ and fancy schmantzy inheritance and design patterns leads to problems when you end up with a PUTCO bus when a hang glider was in the specification

 

[cguy]

So before I left SA I had done a whole exhaustive job search.

Sure you did…

I battled.
A lot of these software companies/service providers were enormously big on OOP, so if you can't explain in an interview what overloading is (even if you can do it in front of them) then you're stopped right there kthxbye, next please. I see this kind of arrogance a lot with the crowd who did comp.sci to the max, i.e. university level.

It’s the kind of arrogance one sees when you don’t know what a car is and everyone looks down on you because of your metal chariot.

Recently I had a bit of an argument with one of them about Golang, and the thing is, we've been doing it a specific way from the start, and it works, it makes us a boat load of money each month and it's in production, but Mr-two-degrees (South African) wants to tell us it's wrong. Well, the developers of Golang beg to differ..

If you don’t know what overloading is, I doubt you would have understood his point.

Where I am at, we're tired of class abuse in C++ which leads to code nobody wants to work on because it's so freaking difficult to understand and moreover, the whole OOP thing becomes an achilles' heel. With code as disposable as it is today, in 5 years what we do today would have been replaced.

Perhaps, it’s because your company hires developers who don’t know what overloading is?

I am going to tell you today, that folks like us, who rose up with C, and are great C programmers, we're looked down upon, and IDGAF anymore. The entire energy sector runs on C and baremetal C code, because C++ and fancy schmantzy inheritance and design patterns leads to problems when you end up with a PUTCO bus when a hang glider was in the specification

There are many good reasons to use C, but you’ve listed none of them.

You would be so much more effective in life if you realized that it’s much more productive to learn a thing than to get angry at at.

 

[semaphore]

So before I left SA I had done a whole exhaustive job search.
I battled.
A lot of these software companies/service providers were enormously big on OOP, so if you can't explain in an interview what overloading is (even if you can do it in front of them) then you're stopped right there kthxbye, next please. I see this kind of arrogance a lot with the crowd who did comp.sci to the max, i.e. university level.
Recently I had a bit of an argument with one of them about Golang, and the thing is, we've been doing it a specific way from the start, and it works, it makes us a boat load of money each month and it's in production, but Mr-two-degrees (South African) wants to tell us it's wrong. Well, the developers of Golang beg to differ..
Where I am at, we're tired of class abuse in C++ which leads to code nobody wants to work on because it's so freaking difficult to understand and moreover, the whole OOP thing becomes an achilles' heel. With code as disposable as it is today, in 5 years what we do today would have been replaced.

I am going to tell you today, that folks like us, who rose up with C, and are great C programmers, we're looked down upon, and IDGAF anymore. The entire energy sector runs on C and baremetal C code, because C++ and fancy schmantzy inheritance and design patterns leads to problems when you end up with a PUTCO bus when a hang glider was in the specification

You are an utterly clueless idiot, a compulsive liar and extremely insecure about your abilities.

 

[semaphore]

Sure you did…

Maybe it’s positive affirmation, if he says it enough it’ll materialise, The Secret lol.

 

[_kabal_]

OOP isn't the solution to anything

Just to be clear though, I use C# and classes/objects every day, but classes/objects !== OOP

Happy C# 12/.NET 8 week