I agree Jacopo. Less is more. This also has to do with the philosophy that simple != easy. These "lazy" commands are nice but they have a price as they add to the complexity. Now if you change something you need to change other things to keep the system functional. You also confuse your users when you have many ways to achieve the same result.
I also think we are introducing convenience too early. We just introduced gradle recently and we did not even remove all the libs yet nor did we introduce a plugin system. It's just way too early to start shoving more and more. Historically OFBiz suffered from being overly complex with a fat code base. Why? it is exactly because of simple things like this one. Imagine this small tangling of code happening thousands of times everywhere in the code base, what do you get? you get the complexity we are suffering from right now. That is why many times I get very afraid when touching code because I just don't know what am I going to break next. Taher Alkhateeb On Saturday, 13 August 2016, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > On Fri, Aug 12, 2016 at 1:58 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com <javascript:;>> wrote: > > > ... > > Why? I prefer, it's more intuitive and I feel a continuity with "legacy", > > to type start and stop rather than ofbiz and "ofbiz --shutdown" :p > > > > Jacques > > > My preference is to design and implement a set of tasks that is as clean, > lean and consistent as possible rather than trying to blend the new tasks > with the "legacy flavor"; while the "legacy flavor" may initially help > old-time adopters already used to the previous style, on the other hand it > could increase the initial learning curve for new adopters. > > Jacopo >
