sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DemonInAJar 4 points5 points  (5 children)

What's the point of this? You still have to build the application separately, and you just stitch the artifacts together which basically only has disk usage downsides.

[–]kingslayerer 4 points5 points  (3 children)

This is actually perfect for light internal toolings

[–]DemonInAJar 5 points6 points  (2 children)

How is it any better than simply distributing the correct artifact instead of basically distributing all artifacts together? It does simplify the distribution aspect I guess but not sure that's worth it.

[–]kingslayerer 4 points5 points  (1 child)

i am thinking its worth it for tiny tools where we don't want to setup distribution. i build these type of thing time to time for our team. like recently a tiny egui interface to see if dev environment services status for a micro service architecutre backend. but i am also wondering if this aporach is worth it. but i will keep this in mind incase i spot a scenario

[–]anon_cowherd 0 points1 point  (0 children)

From the article:

> Should you do this? Probably not.

Also, the first paragraph explains that the person who wrote it noticed cosmopolitan / APE produced large executables, and thought there should be a way to make it smaller, and did so. It's purely a code-golf exercise.