Hey,

I'm just done with the DevSummit conference in Stockholm, where I 
presented Qi4j. It went very well, and people are generally quite 
excited. It's fun to see that different people find different favourite 
features in it. Some more architecty folks like the explicit Module and 
Layer definitions, whereas others like the strong typing in concerns, 
and others crave the mixins. There's something for everyone it seems :-)

I've had lots of good discussions these past days with Dan North in 
particular, who was the first to point out that this isn't AOP. He 
hadn't see the current state so I went through all the terminology with 
him, and explained some of the vision we have with it. One thing that he 
immediately reacted on was that @ThisCompositeAs is way too long. 
Something like @Me, @Self or even @This would be better he thought. Any 
thoughts from you guys on this naming?

We also discussed the topic of who would this appeal to first. David 
Leangen once said that it'll take 10 years for people to catch up. Dan's 
take was that people who are normally allowed to do exploratory work, as 
a strategy in big firms, might be checking it out. Anyone who is 
generally inclined to try out new things, either because of need or 
because of their inherent nature, would be interested.

I also overheard a conversation with Roy [EMAIL PROTECTED] who 
commented that it is in recessions that disruptive technologies really 
thrive, because people are looking for alternatives to make them more 
efficient. This, I think, is a very very important point. When I started 
Senselogic in 2002, and wrote the "first iteration" (so to speak) of 
these things it was precisely that need for something that could match 
the lack of resources (time+money+people) that was the main motivation.

I also talked to some people about having built-in support for REST in 
Qi4j, and especially Dan gave me some good advice that I want to try 
out. Too early to talk about really, but it will be.. interesting :-)

That's about it. Another great conference done. Now on with coding.

/Rickard

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to