I totally agree with Christian, in fact, the point (slow, should be avoided if possible) was right there in the Summit keynote.
on the point of "slow" of course it is a relative thing and perhaps not a big deal depending on the context, but you only have to run code with Storage and the speed difference is quite palpable. it is not a 4D specific phenomena, it is intrinsic to how blocking based on mutex works. on the point of "good coding" 4D forces you to forfeit exclusive access with the "Use/End use" code block, so unless you implicitly use storage in a stacked subroutine (super bad idea), it is hard to violate the FILO tule unintentionally. a more subtle gotcha is to make the mistake of using objects and collections as if they were values, not references. it's not limited to storage, but it can really bite you when you make the mistake with storage. 2018/08/26 17:26、Tim Nevels via 4D_Tech <4d_tech@lists.4d.com<mailto:4d_tech@lists.4d.com>>のメール: Humm... interesting comment. Why do you say Storage is slower and can produce deadlocks? Tell us why you believe this. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
