It is (perhaps) fortuitous that this issue comes up at this time. I have struggled to imagine a thoughtful value proposition for DeltaSpike targeting our 700+ developers on six continents (that don't necessarily use English as a first language). The subtle distinction between a CDI-container and a CDI extension seems to me like a lower-level concern that fails to grapple with the value proposition for DeltaSpike.
That is, why should one consider DeltaSpike as a wrapper for technologies that are implementable with a native API? For example, in the persistence space, what is the compelling value proposition for obfuscating the specification-backed Java Persistence API with a proprietary DeltaSpike API that dictates a CDI dependency? (Presume that some folks perceive an additional dependency as a negative... not a positive.) Said a third way, if we expect DeltaSpike acceptance to grow beyond the current faithful, how do we articulate the advantages in a manner that causes the thoughtful to think? _Marvin -----Original Message----- From: John D. Ament [mailto:john.d.am...@gmail.com] Sent: Monday, June 20, 2016 10:41 AM Subject: Re: [ANNOUNCE] Release of Apache DeltaSpike 1.7.0 Sebb, Great points. I'll make sure the email for the next release provides more details. John On Mon, Jun 20, 2016 at 10:33 AM sebb <seb...@gmail.com> wrote: > What is the project about? Why should I be interested in it? > (rhetorical questions) > So the e-mails should contain at least brief details of what the > product does. However the sentence: > "Apache DeltaSpike is not a CDI-container, but a portable CDI extension." > will mean nothing to most people. What does CDI mean?
