Post #2519536

2026-04-12 09:51 UTC

@carlton@chaos.social disregarding specific libraries, there's definitely a rich discussion to be had around application architecture and complexity management here, and I think your entry here adds to it thoughtfully. I personally fall into the camp where I'll happily put the business logic meat into the "view", eschewing a service layer until the codepath needs to be shared. I have folks at $DAYJOB arguing otherwise, and not without merit.

Replies (3)

@carlton@chaos.social 2026-04-12 09:54

@tintvrtkovic@mastodon.social Ooh, good. Spicy 🌶️ I have OPINIONS about keep views bare... so I tend to have logic live in forms[*] — but people hate that too 😜 Glad you liked it. That you liked it before the cattrs reveal is extra nice, but you know I've been using it. (We can finally carry on our conversation: will you be in Bologna?) [*]: It sounds crazy but is remarkably clean, I promise.

Open ##2519537
@tintvrtkovic@mastodon.social 2026-04-12 09:55

@carlton@chaos.social the argument goes that refactoring into a more abstract service layer on-demand runs into the risk of it being done inexpertly and inconsistently. Which I understand. I guess, like many things in software engineering, the right call here depends on the people involved and not the technical arguments one way or another

Open ##2519540
@hynek@mastodon.social 2026-04-12 10:56

@tintvrtkovic@mastodon.social @carlton@chaos.social you’re going to hell for your singleton dependency module anyway so why not lean into it

Open ##2519542