| Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 |
Browse archives
|
Untitled
Submitted by reeses on Fri, 2003-02-14 02:43.
This is one of the funnier postings I've seen in a while. This is my favorite part: The AspectJ notion of AOP lacks discipline: it resembles the COMEFROM I like aspects, and I like the opportunities afforded by the freewheeling aspects (ahem) of AspectJ, but I freely admit that I am terrified of dealing with someone else's code that relies heavily upon it. Can you imagine the side effects of hidden code that you don't call, don't know is being called, and have never seen? Yeech. Calling strange libraries and multithreaded quasinondeterminism are bad? You ain't seen nothing yet! Post new comment |
SearchUser login |