[haiku-development] Re: Services Kit status for beta 3
- From: Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx>
- To: Haiku Development <haiku-development@xxxxxxxxxxxxx>
- Date: Mon, 1 Mar 2021 08:29:09 +0000
Hi,
On Sun, Feb 28, 2021 at 10:44 PM Zenja Solaja <solaja@xxxxxxxxx> wrote:
Hi all. Speaking as an Haiku app developer, one of my new projects is using
the Services Kit, and I personally have no problem refactoring it to use any
new API even when it breaks the ABI (as long as a transition guide is written
to help us migrate to the new API). This is expected for a Beta /
development release. Of course, after R1 is finally released, I do expect
the ABI to be set in stone ...
I think there are three things to note for all app developers:
- Haiku R1 beta 3 will include the current (deprecated) API in
libbnetapi.so, so you do not have to switch to the new API right now.
This does mean that future releases (beta 4 or others) will not run
your application. But at least it gives you some time to get new
builds out before that happens.
- The new API for now is distributed as a static library, meaning
that when you build your application against it, it will run on future
Haiku versions even if we change the underlying API of that library.
Note that there are things to be improved from a developer perspective
in terms of making it possible to do repeatable builds irrespective of
the build platform.
- When the API gets reintroduced into a system-supplied shared
library, it will get the same promise of compatibility as the rest of
the system.
So from my personal perspective, I prefer that the core developers break the
API in Beta in order to fix deficiencies/bugs, since I would rather have
something that works than something I ignore.
Good! And as a user of the library, please do share your thoughts.
There is going to be a period of time where we have the flexibility to
change the way things work, so that they better fit in your
applications.
Regards,
N>
Other related posts:
