Hugo Thunnissen <devel@hugot.nl> writes:
On 8/17/23 23:14, Philip Kaludercic wrote:
Another idea is to have a Makefile generate the file, like the one you
describe in option 2., that is generate whenever the package is built
and bundled into a tarball for distribution. That way you don't have to
store a binary blob in your repository, and you can avoid burdening the
user with additional computations at either compile or runtime.
Does the generation require any special functionality/tools/code to be
provided on the device the index is generated on?
The php function/class stubs are generated with a php script, but I'm
checking the resulting stubs file into git. The index itself can be
built with just my package based on the stubs file.
I saw that, and the commit did not look that nice, but I cannot say that
I have looked into the issue in sufficient detail to say with certainty
or not that there is no better solution.
Also: If the former is the case, is the reduction in load time that
this brings even significant enough to be worth the bother or should I
just hold off on this while I look for a more efficient solution?
I'd say it would be worth it, if the resulting package would be smaller
and would load quicker. After all, the performance on your laptop might
not be that significant of a difference, while for someone else with an
older or slower device, a 30%-speedup is pretty significant.