elie/PhoenixPE
1
0
Fork 0
mirror of https://github.com/PhoenixPE/PhoenixPE.git synced 2025-09-17 18:48:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (mediawiki)

Jonathan Holmgren
2022-09-18 18:48:09 -05:00
parent 196bce5e7b
commit d5bb62b4e8
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ.mediawiki

@@ -22,7 +22,9 @@ PhoenixPE on the other hand targets basic/advanced users as well as developers l
'''TL;DR: No. It's an alternative. The developers of both projects are part of a vibrate community that works together and shares their knowledge and experience. Use the one that best meets your needs. You can't go wrong.'''
== Why don't you just use PortableApps.com, SFX Constructor, etc instead of developing your own App Scripts? ==
== Why don't you just use PortableApps instead of developing your own App Scripts? ==
There are a few issues to be taken into account with with pre-packaged applications like those provided by PortableApps.com, SFX Constructor, etc.
1. Using a pre-packaged portable app introduces another 3rd party relationship. Once the original author releases a new version of the software, somebody has to notice and create a new portable app package. This can introduce delays in the update process as PhoenixPE has no control over when or if the package maintainer updates the portable app for the new version. It also leaves us vulnerable to the package maintainers opinion/idea of what a portable app package includes and what features are available.