The OFFICIAL programming thread

Kilemall

This post is deleted!

Hog

If you can put aside maybe some unfamiliarity with his core argument, the below was a really interesting talk on computer history going back to the 50’s and how we got to where we are with OOP programming as it is mostly practiced today:

Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025

Trigger warning: he comes out swinging against C++ pretty early so if you like C++ it might piss you off but the core of his argument is really against what calls something like compile time domain modelling of hierarchies - basically deep class hierarchies that model how we think of the world (Vehicle -> Car -> Sports Car). I don’t think the latter is really very controversial anymore since I’ve been hearing “favor composition over inheritance” as being the prevailing wisdom for maybe a decade or longer.

Edit: Gemini tells me the “favor composition” advice was in Design Patterns so that goes way back.

oyaji

2½ hour video? Maybe a DL on WiFi in town, sometime.

Cliff notes, anyone?

Hog

YouTube shorts: something magical happens

Kilemall

@Hog said in The OFFICIAL programming thread:

If you can put aside maybe some unfamiliarity with his core argument, the below was a really interesting talk on computer history going back to the 50’s and how we got to where we are with OOP programming as it is mostly practiced today:

Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025

Trigger warning: he comes out swinging against C++ pretty early so if you like C++ it might piss you off but the core of his argument is really against what calls something like compile time domain modelling of hierarchies - basically deep class hierarchies that model how we think of the world (Vehicle -> Car -> Sports Car). I don’t think the latter is really very controversial anymore since I’ve been hearing “favor composition over inheritance” as being the prevailing wisdom for maybe a decade or longer.

Edit: Gemini tells me the “favor composition” advice was in Design Patterns so that goes way back.

Reminds me of the logic behind zero trust- define your security structure and methods/efforts geared towards actual need, not lazy ass assumptions about what box gets whose access.

Gators1

I guess Amazon will have to hire back those 30K people now…

Alexander T. Williams / Oct 31

Vibe Coding, Six Months Later: The Honeymoon’s Over

Six months after the hype began, is vibe coding sustainable? We look at the pros and cons, and why blending vibes with structure is key.

Hog

@Gators1

Vibe coding’s strength lies in helping you find direction quickly, but vibe engineering simply isn’t there yet.

“Vibe engineering” being a contradiction in terms might shed some light there.

Blanks

@Hog said in The OFFICIAL programming thread:

@Gators1

Vibe coding’s strength lies in helping you find direction quickly, but vibe engineering simply isn’t there yet.

“Vibe engineering” being a contradiction in terms might shed some light there.

Stop trying to harsh our vibe dude

Kilemall

@Blanks said in The OFFICIAL programming thread:

@Hog said in The OFFICIAL programming thread:

@Gators1

Vibe coding’s strength lies in helping you find direction quickly, but vibe engineering simply isn’t there yet.

“Vibe engineering” being a contradiction in terms might shed some light there.

Stop trying to harsh our vibe dude

Another gaddam user.

Hog

Oct 30

Odin Programming Language

I’m learning the Odin programming language. By default, when you save your source code the LSP reformats your code to the Odin recommended style. OK. I don’t love it when languages come with highly opinionated programming styles but I can learn to swallow my bile when it does things like replace my spaces with tabs. But then it goes and does this:

What kind of un-gohly fucking terrorist aligns the case conditions with the switch?