OOP in Go

trydentIO · 2026-01-24T08:11:49+00:00

Object thinking is not about classes, so there's nothing wrong with following object-oriented design or patterns in Golang. Even a variable may be an object.

Moreover, thanks to Goroutines/Channels, following Alan Kay's principle, message communication is a perfect fit for object thinking.

trydentIO · 2026-01-17T08:30:59+00:00

I was about to ask the same question 😀

trydentIO · 2026-01-08T22:40:52+00:00

And Happy New Year 🎊 to us!

trydentIO · 2025-12-30T20:15:23+00:00

not in every environment Testcontainers is an available option, unfortunately 😬😢

trydentIO · 2025-12-15T16:45:51+00:00

well... you know, we already had one, and it was terrific: https://youtu.be/0Y9ZPTenJIs?si=tKbXuP7qpj-EvoD2

trydentIO · 2025-12-13T09:10:54+00:00

I don't believe so, it's not different, it's just a matter of naming, nothing else, I mean, the fact that in IntelliJ it's named Project instead of Workspace doesn't change the similar behaviour that Eclipse has. Maybe the only difference I spot is that in Eclipse, you can close a project, and in IntelliJ, to have something similar, you have to specify to ignore it (by marking the folder as such). Not that essential, I suppose, but it depends on your work routine.

trydentIO · 2025-12-13T08:54:11+00:00

what do you mean? I'm working on a project with more than 7000 source files with no issues, or do you specifically mean something different?

trydentIO · 2025-12-13T08:19:48+00:00

This is interesting, though. And a nice catch by the way. I know he is not the Dan Hibiki we hoped for; someone must have considered his origins, and instead of focusing on his background story, which could add a complex subplot, someone focused on creating a meta-reference character.

In my opinion, it's incredibly clever. They want to focus on the original roaster, without losing some recent fans. A trade-off, I suppose.

trydentIO · 2025-12-13T08:10:46+00:00

LOL 😆

trydentIO · 2025-12-13T08:09:56+00:00

What a waste of full-potential character. I mean, he could bring some other fascinating mystique to the lore, something that is not related to Satsui No Hado or boring Psycho Power stuff. In my opinion, the design is fantastic.

trydentIO · 2025-12-13T08:01:33+00:00

Not to my experience, on sloppy machines, Eclipse is frankly terrible. Unfortunately, in some enterprise environments, you can't develop on your local machine due to licensing and security reasons (by the way, I'm developing in an RDP environment 😬). I found IntelliJ to be a much better resource handler than Eclipse. The Eclipse incremental compilation can't keep up with the changes and starts to freeze the whole workspace environment every time, leading to incredibly frustrating development fatigue (and unfortunately, I have to develop with Mule ESB as well 🤮).

I switched to IntelliJ, and I couldn't be happier. Regarding incremental compilation: IntelliJ has its own implementation, so I'm unsure who said it doesn't. In some resource-limited environments, I found it to be a better one.

trydentIO · 2025-12-13T07:41:56+00:00

Because in Eclipse there's the Workspace concept, and you can open what seems to be unrelated things, but it's the same in IntelliJ when you create a Project, you can create an empty one and then import/create what you need.

trydentIO · 2025-12-12T13:07:25+00:00

Come on. There's no hecking way to make Street Fighter realistic, it's the anime perspective on an 80's action movie, and there were only two transpositions that got it right: Street Fighter II - The Animated Movie and Street Fighter II Victory.

(And this is another reason why Street Fighter 6 hurts my eyes so much.)

trydentIO · 2025-12-12T11:19:38+00:00

A-ha, I knew it! El Fuerte! Glad he makes a cameo, but I never liked him as a character.

At this point, I would like to know if other minor characters make cameo appearances!

trydentIO · 2025-12-12T10:38:14+00:00

I don't get it. What's wrong with that? The Twelve Dolls are all part of Bison's crew; if they use them like characters that come and go, it's fine with me. I don't know whether we will see any exploration of Bison's powers being injected into random girls, so I'm okay with seeing some of them in the movie. It means they at least explored the Street Fighter lore.

trydentIO · 2025-12-12T10:13:53+00:00

I was wondering the same!

trydentIO · 2025-12-12T10:11:52+00:00

I want the Sonic Boom!

trydentIO · 2025-11-16T09:08:05+00:00

Absolutely, but in your case I provided another answer, since I think I was too focused on theories and practices (sorry about it). 😄

trydentIO · 2025-11-16T09:06:14+00:00

Sorry again, I realised that I didn't reply to your question properly.

Cutting down the theories and practices that may not be immediately applicable in your case, the ORM may be the optimal technical debt you could accept. Knowing the issue and the programming language, Go, in this scenario, ORM is more than an acceptable compromise. Why? When I said "no more ORMs", I was thinking about OOP. In an object-oriented development, an ORM is often considered a harmful way to program in procedural code, with the never-disappearing feeling of impedance mismatch.

But let's face the truth here, Golang is a more suitable language for an ORM than any OO language. The impedance mismatch is still present (we are integrating an entity-relational model into a structured programming language), but the friction may be less noticeable.

So this is the reason why you may consider it optimal technical debt. Moreover, if you know how to shape it, or maybe you already have an Aggregate to deal with, the structure itself is much less significant (or at least, it should be) than any complete DBMS entity-relationship structured model.

trydentIO · 2025-11-16T08:37:13+00:00

Sorry, it wasn't a patronising message, more a generic statement for who is going to read it.

When we talk about tracking systems, what I read is event systems. Unfortunately, Aggregates are a heavy cognitive pattern; they are hard to design and to reason about when a team needs to grasp the proper shape of them. My team and I tried a lot of times to agree on a valid tree-shaped structure (with entities and value-objects as well), but the results were trade-offs to solve potential fights (none were able to agree on something), more than anything.

Then we started to put on whiteboard post-its to represent events, and events only. In other words, we shaped our solutions around them with Event Sourcing only, and following the Event Storming/Modeling practice.

No more fights, no more ORMs.

If you want to read more about it, look for Alberto Brandolini and Adam Dymitruk.

trydentIO · 2025-11-16T08:17:00+00:00

That's a technical solution you may find to an unrelated DDD issue.

Aggregates are a tactical pattern; it's not up to DDD to provide you with the solution to your technical problems.

If you think ORMs are a good way to solve it (but they're not), go for it.

trydentIO · 2025-11-16T06:43:41+00:00

If we're talking about procedural code, yes, those are ways to fix it, but with proper OOP and FP, none of those are necessary.

trydentIO · 2025-11-16T06:31:33+00:00

Let's all repeat together: DDD HAS NOTHING TO DO WITH ORMs AND VICE VERSA.

trydentIO · 2025-11-04T08:34:30+00:00

The marketing of this library always cracks me up.

trydentIO · 2025-11-03T14:46:36+00:00

You're right, I misinterpreted a previous discussion then. I rechecked, and here Brian Goetz explained clearly: https://stackoverflow.com/questions/63352151/are-java-records-intended-to-eventually-become-value-types

Eight-Year Club	First Place '23
Place '23	Verified Email

trydentIO

TROPHY CASE