On 24/05/2021 07:27, Mark Rotteveel wrote:
> On 24-05-2021 00:11, Adriano dos Santos Fernandes wrote:
>> It's also funny that the few who direct uses the old API and do not want
>> to migrate and asks for core team to maintain it, generally are the ones
>> constantly asking for new features and
On 24-05-2021 00:11, Adriano dos Santos Fernandes wrote:
It's also funny that the few who direct uses the old API and do not want
to migrate and asks for core team to maintain it, generally are the ones
constantly asking for new features and fast releases.
Is this some thinly veiled jab at me?
On 22/05/2021 07:20, Mark Rotteveel wrote:
> On 22-05-2021 12:03, Dimitry Sibiryakov wrote:
>> 22.05.2021 11:10, Karol Bieniaszewski wrote:
>>> And the final conclusion why new API is better then old one as it was
>>> accepted and preffered.
>>
>> For application development new API isn't
On 22-05-2021 12:03, Dimitry Sibiryakov wrote:
22.05.2021 11:10, Karol Bieniaszewski wrote:
And the final conclusion why new API is better then old one as it was
accepted and preffered.
For application development new API isn't better than old one. Its
aim is Firebird plugins development
22.05.2021 11:10, Karol Bieniaszewski wrote:
Isn’t such documentation already available by the new API developers?
No.
Its benefits, comparision with simplicity about use, speed, memory usage,
extenibility..
Nothing like this.
And the final conclusion why new API is better then old
Isn’t such documentation already available by the new API developers?
I cannot imagine to have not comparision between every code in old vs new api.
Its benefits, comparision with simplicity about use, speed, memory usage,
extenibility..
And the final conclusion why new API is better then old one
