Comments (3)
Potentially similarly:
- Provide alternative implementations made in different languages
Not sure I understand this either: What benefit is there to maintaining multiple official implementations? The payload shouldn't care what language the stub is written in. Either it works fine, or it doesn't and someone (hopefully) makes a better one.
from type3-runtime.
Retrospectively, I don't recall any payload formats other than squashfs which I'd like to see supported officially. I guess one of the reasons is that there already are some (only partially compatible) implementations that don't use squashfs but claim to be AppImages. Almost all tooling around type 2 makes the assumption that the payload is squashfs, but it isn't really mandated by the specification.
I think I could live with enforcing squashfs at this point. But as you noticed in #8, there is some interest in alternative payload formats as well. Heck, we could even support mixing different payload formats and (fake-)overlay-mounting them.
Edit: by the way, I'm pretty sure a type 3 should specify a way to extract desktop integration data without having to read the payload format as a fallback.
What benefit is there to maintaining multiple official implementations?
This doesn't discuss the possibility of having different "official" implementations (although there certainly could be more than one, e.g., a C and a Rust one), but also really allow third-party-written runtimes. The point in standardizing is to allow such development, not to prevent it. As said, there already are some alternative (experimental?) runtimes for type 2.
What could set off official runtimes from third-party ones is code signing. We could provide properly signed releases.
from type3-runtime.
Heck, we could even support mixing different payload formats and (fake-)overlay-mounting them.
Absolutely you could, and yes, you could make a ELF+PKZIP polyglot or more. the reason I asked these questions is that with any feature there's a complexity/benefit tradeoff. So I don't think any of these things should be done :)
This doesn't discuss the possibility of having different "official" implementations
I see, having a decent spec so that someone could make a third-party runtime seems sensible.
As for the code signing (and we're going off topic again here i suppose). If the user downloads and runs an appimage, they run the payload anyways (you have already written about sandboxing in #10). So I'm not sure if having a signed runtime brings any tangible benefit over just signing the entire AppImage with software vendors keys, as you'll have to trust them anyways.
from type3-runtime.
Related Issues (13)
- Brainstorming about the design goals of a type-3 image format HOT 20
- Multi-Layer AppImages HOT 9
- Versioning AppImage components HOT 1
- removing specification requirement of .desktop files HOT 3
- remove limitation on number of applications HOT 4
- Clarify Image format, runtime, header HOT 3
- ELF resources HOT 14
- Is it technically possible to make an AppImage that is also a valid zip file? HOT 18
- FUSE compatibility HOT 1
- Proper sandboxing HOT 1
- Desktop Integration Data without accessing payload HOT 9
- Consider shell scripting as language
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from type3-runtime.