Why Wizards Hate Dependency Injection with Aspects

An airhacks.fm conversation with Jarek Ratajski (@jarek000000)
about: Starting programming immediately with C 64, mysterious
machines, touching the ZX spectrum once, amazing TV show about
science Sonda, unofficial access to adults library, learning C64
basic with Atari ST manual, learning assembly because of: SYS 2064,
GOTO and sisters, writing encryption software, writing the Snake
game, writing Pong in Haskell, reinventing the C by writing
assembly macros on Amiga 500, writing simulation for the stock
market with Windows 95 and C, the Trumpet Winsock, first good
experience with Swing programming and Forte for Java, problem with
Borland C++ licenses, publishing software with Java, linux had
great C-compilers but no mainstream UI libraries, "Java must go
away", Java Vectors and Hashtables, writing Content Management
Systems with Java, converted JavaScript developers, JSP-only
projects, fear of reuse, the HashTable pattern, probably Java won't
disappear, becoming Java advocate, first projects with JServ,
WebSphere 1, W3C Jigsaw, Tomcat 3 was better behaving, than jserv,
Caucho's Resin, migrating to EJB 3 and Java EE, writing commercial
Java game with JMonkey Engine and JBoss backend, fighting with
interfaces and over-engineering, the wizard look and feel,
appearing in a bank as wizard, container injection is not needed,
constructors are the perfect replacement for dependency injection,
aspects are problematic, try and error programming leads to mess,
@PostConstruct is one of the most insane constructs, writing just
POJOs, Slaying Sacred Cows: Deconstructing Dependency Injection by
Tomer Gabel, the real problem are aspects, CDI on Tomcat, Java's
dynamic proxy, ratpack and jooq, building servers with libraries
without classpath scanning, Time Injection would be useful,

Jarek Ratajski on twitter: @jarek000000 and on github