Hacker News Reader

Comment by rjbwork | Hacker News Reader

Caching, managing object life times in IOC containers, input validation, are some common uses I've seen.

Transaction coordination, Error management (retry, backoff, fallback).

In the end, aspects were always used for the same transversal concerns, which any serious framework would provide explicit support for anyway.

Going beyond these to use aspects for application domain modeling is popping open an immense can of carnivorous worms on the dev team.

Thanks - I'm sure there are other uses cases, I didn't mean to imply there weren't, just for me I always associate AOP with a time in my career where nothing useful was ever shipped, but there was lots of pontificating and philosophising about rather abstract things like this.

Lol. I associate C++ with that. Turns out the first big C++ project I was involved with had a lot of research types. To their credit, when they did something it was almost always the best thing to do. But there was A LOT of thought and discussion put into each line of code.

For a decade I thought about C++ as being "the language for people who are forced to think long and hard about every line of code."

And then I saw "normal" C++ code everyone else was writing...

I now sort of like it (C++), especially after recent language additions.

It seems to me a lot of these things are handled more plainly by delegation and composition.

Reply on news.ycombinator.com