This is not to take anything away from this project, just making an observation. The programming field often feels like it's in a giant loop constantly re-discovering what went before.
Warp – self-contained, single binary applications
11–20 of 157 posts
Re: Warp – self-contained, single binary applications
#12This sounds like a much less general binctr [0]. I don't see how warp handles the most trivial case of a dynamically linked executable; I see no references to patchelf or other such tricks to ensure it looks within the application's cache directory for dynamically linked libraries, nor do I see any mount namespaces. Does warp do that? Why would I use warp if it doesn't when there are more generic solutions that can h…
> This sounds like a much less general binctr. binctr is Linux-only, and appears to need Docker as a runtime requirement? This has neither constraint, apparently?
Re: Warp – self-contained, single binary applications
#13Based on the readme, this is basically an SFX archive, which runs a binary upon completion of extraction to temporary folder, much like winzip & the like have created for ages.
Re: Warp – self-contained, single binary applications
#14Very neat. Would like to see more languages targeting single binaries. This is one reason (I believe) that has made Go so popular.
I wish also had this. However, containers work. Not sure why they do java though, i thought java has been happy with jars so far.
It's still early days in terms of what's available in the runtime (e.g. the AWT subsystem is missing), but it's pretty damn impressive anyway.
Re: Warp – self-contained, single binary applications
#15It's fascinating how self-contained binaries are now coveted as such a desirable feature. Dozens of languages (if not more) were capable of this decades ago. In fact, some of them could generate self-contained binaries that allowed you to bundle app assets like icons and images inside the executable - no additional add-ons needed. And they were native executables, not complicated wrappers with layer upon layer of dif…
It might feel that way, but this is driven by economics. Basically disk, memory, and bandwidth is far cheaper than it used to be so who cares if you waste a GB or so copying the same libraries all over if you don't have to solve for dependency hell?
Re: Warp – self-contained, single binary applications
#16Very neat. Would like to see more languages targeting single binaries. This is one reason (I believe) that has made Go so popular.
Re: Warp – self-contained, single binary applications
#17It's fascinating how self-contained binaries are now coveted as such a desirable feature. Dozens of languages (if not more) were capable of this decades ago. In fact, some of them could generate self-contained binaries that allowed you to bundle app assets like icons and images inside the executable - no additional add-ons needed. And they were native executables, not complicated wrappers with layer upon layer of dif…
I think part of this comes from various tradeoffs becoming more or less important at different times. Processing power goes up so you move to fat clients, then people move to battery powered devices and heavy lifting makes more sense on servers again.
Re: Warp – self-contained, single binary applications
#18I wonder what benefits this has over other solutions? Originally when it said multi-platform i thought it meant that one binary could run on multiple platforms like a fat binary. But i think all of the examples require you to have a specific target in mind.
Re: Warp – self-contained, single binary applications
#19Very neat. Would like to see more languages targeting single binaries. This is one reason (I believe) that has made Go so popular.
I wish also had this. However, containers work. Not sure why they do java though, i thought java has been happy with jars so far.
Re: Warp – self-contained, single binary applications
#20It's fascinating how self-contained binaries are now coveted as such a desirable feature. Dozens of languages (if not more) were capable of this decades ago. In fact, some of them could generate self-contained binaries that allowed you to bundle app assets like icons and images inside the executable - no additional add-ons needed. And they were native executables, not complicated wrappers with layer upon layer of dif…
> The programming field often feels like it's in a giant loop constantly re-discovering what went before. It might feel that way, but this is driven by economics. Basically disk, memory, and bandwidth is far cheaper than it used to be so who cares if you waste a GB or so copying the same libraries all over if you don't have to solve for dependency hell?
Not in the cloud.