Synopse Open Source - Tag - GetItmORMot MVC / SOA / ORM and friends2024-02-02T17:08:25+00:00urn:md5:cc547126eb580a9adbec2349d7c65274DotclearGetIt "Spirit" Concernsurn:md5:c8befaf992f7ae8f2053d260241925262015-06-06T10:52:00+02:002015-06-06T12:23:00+02:00AB4327-GANDIPascal ProgrammingblogDatabaseDelphiGetItmORMotOpenSourceORMSOA <p>I'm confused by the <a href="http://community.embarcadero.com/index.php/article/news/16027-submitting-libraries-to-getit">
GetIt Submitting official blog page</a>.<br />
Reminds me the darker ages of <a href="http://www.deltics.co.nz/blog/posts/1097">Delphi licensing change of
XE3</a>.</p>
<p><a href="http://blog.marcocantu.com/blog/2015-june-more-info-getit.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+marcocantublog+%28marcocantu.blog%29">
GetIt</a> is the new XE8 package manager for RAD Studio. Information about how
to submit your libraries to GetIt has just been made available by Embarcadero.
The idea behind GetIt is really to make is easier and faster to discover,
install, and keep updated some of the best open source libraries for Delphi and
C++Builder.</p>
<p>When you <a href="http://community.embarcadero.com/index.php/article/news/16027-submitting-libraries-to-getit">
look at the approval conditions</a>, it sounds like if mORMot would not find
its way in this package manager:</p>
<blockquote>
<p>Replacing key capabilities that are part of the core platforms definitions
such as Client/Server FireDAC pack or the DataSnap/EMS Enterprise middleware,
would be less likely to be accepted.<br />
The different SKUs are meant for different types of developers, and multi-tier
capabilities with strong client/server RDBMS integration
<strong>require</strong> an Enterprise edition license.<br />
We will bias acceptance toward GetIt libraries that respect the <strong>spirit
of our licensing and editions</strong>, not just use the letter of the license
and the technical boundaries. If you are unsure about your submission please
check with us first. </p>
</blockquote>
<p>What is this "<em>spirit of our licensing and editions</em>"?<br />
Why is it not part of the official license terms?<br />
Where does this assumption comes from?<br />
Would the licensing conditions change in the close future, as with the XE3
"episode"?<br />
Would Marco's interpretation become the new rule?</p>
<p>It clearly <a href="https://blog.synopse.info?post/post/2012/09/03/Client-Server-allowed-back-to-XE3-pro">reminds me the XE3
time where there was an attempt from Embarcadero to modify their licence
terms</a>, so that third party vendors or Open Source libraries would not be
allowed to create multi-tier frameworks with Delphi!<br />
Is it true that "<em>strong client/server RDBMS integration
<strong>require</strong> an Enterprise edition</em>" ?<br />
Last time I checked the licence terms, it was not stated.<br />
Why on earth would we have to pay for the <em>Entreprise</em> edition, if the
<em>Professionnal</em> edition is all that you need?</p>
<p><img src="http://static.tvtropes.org/pmwiki/pub/images/suicidalstupidity_6656.jpg" alt="" /></p>
<p>Still the same "closed" spirit.<br />
It is like if they know their own n-Tier solution weaknesses, so they try to
avoid any other possibility, but to use their own.<br />
They clearly do not understand the benefit and dynamic of Open Source.</p>
<p>I guess our little <em>mORMot</em> falls directly into this "unwelcomed"
category.<br />
I did not make the submission yet. But should I?<br />
Perhaps sub-part of the framework may find its way in: <a href="http://synopse.info/fossil/wiki?name=PDF+Engine">SynPdf</a>, <a href="http://synopse.info/files/html/api-1.18/SynCrypto.html#">SynCrypto</a>,
<a href="http://synopse.info/files/html/api-1.18/SynGdiPlus.html#">SynGdiPlus</a>,
<a href="http://synopse.info/files/html/Synopse%20mORMot%20Framework%20SAD%201.18.html#TITL_45">
SynCommons</a>...<br />
But the main ORM/SOA/REST/MVC/StubMock features would certainly be
rejected.</p>
<p>Our Open Source project is sometimes preferred to DataSnap/EMS (or even
FireDAC), not only for licence cost, but also about features, documentation,
stability, compatibility with older versions of Delphi, performance, and Linux
compatibility.<br />
I have encountered several companies which are still using Delphi <em>because
of <em>mORMot</em></em>: if they did not have found it, they would have moved
to C# or Java, just to be able to use a full SOA/MVC stack, which was not
available, even in the "Enterprise" version of Delphi.</p>
<p>Story repeats itself.<br />
I just wanted to ensure that the licensing terms would not change in that
direction.<br />
I - as many Delphi users - would not let this GetIt "spirit" become the new
rule.<br />
We have to react, as we did for XE3, otherwise we may all suffer!<br />
IMHO Embacardero should better focus on the compiler and IDE, not cutting the
branch on which they are seated...</p>
<p>What do you think? <a href="http://synopse.info/forum/viewtopic.php?id=2623">Comments and feebacks are
welcome</a>!</p>