Not trying to be discouraging, but I've gone along that path before, and found the solution only good enough for hello-world toy programs. Real programs interact with OS in all kinds of ways. I.e., I'd like to see how a real-world program that interacts with OS in all kinds of ways can benefit from such 100kB Smaller images. That'll be really interesting. Thanks.
Good point. With a little diligence it can be done.
Here's a broader example building a rest api into a tiny container dev.to/tonymet/build-a-2mb-rest-ap...
Later on I'll show tooling you can use to help identify dependencies methodically so it seems less like voodoo
Loving it -- looking forward to your updates.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.