'. '

Portability

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(New page: When designing frameworks and libraries that shall be widely adopted it is important to increase portability as much as possible. If an API can be used on different systems, differ...)
Line 1: Line 1:
When designing frameworks and libraries that shall be widely adopted it is important to increase [[portability]] as much as possible. If an [[API]] can be used on different systems, different configurations, the amount of users including such [[API]] in their applications grows.
When designing frameworks and libraries that shall be widely adopted it is important to increase [[portability]] as much as possible. If an [[API]] can be used on different systems, different configurations, the amount of users including such [[API]] in their applications grows.
 +
 +
 +
[[TBD]]
 +
 +
Of course, writing portable libraries is harder. It requires more work from the [[API]] author, more self-control, more suffering. However such suffering is justifiable. There is usually a single [[API]] writer, but there are [[3SidesToEveryAPI#Mine|many users]] to it. What matters is to simplify and improve experience of those [[API]] users - own author suffering doesn't matter that much.
 +
 +
On the other hand, there is no need to suffer needlessly. Even [[API]] writers shall have a decent life! What does that mean in [[Java]]? While an [[API]] writer wants to target the oldest [[JDK]] possible, there is no point in sticking with ancient [[Java]] syntax! Just use [[Frgaal]]!
 +
 +
[[Frgaal]] is the [[Java]] compiler for framework and library authors!

Revision as of 15:03, 29 October 2022

When designing frameworks and libraries that shall be widely adopted it is important to increase portability as much as possible. If an API can be used on different systems, different configurations, the amount of users including such API in their applications grows.


TBD

Of course, writing portable libraries is harder. It requires more work from the API author, more self-control, more suffering. However such suffering is justifiable. There is usually a single API writer, but there are many users to it. What matters is to simplify and improve experience of those API users - own author suffering doesn't matter that much.

On the other hand, there is no need to suffer needlessly. Even API writers shall have a decent life! What does that mean in Java? While an API writer wants to target the oldest JDK possible, there is no point in sticking with ancient Java syntax! Just use Frgaal!

Frgaal is the Java compiler for framework and library authors!

Personal tools
buy