From d5bb62b4e83e2a1ceae7fc8b1f6ebb0d73a701d8 Mon Sep 17 00:00:00 2001 From: Jonathan Holmgren Date: Sun, 18 Sep 2022 18:48:09 -0500 Subject: [PATCH] Updated FAQ (mediawiki) --- FAQ.mediawiki | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/FAQ.mediawiki b/FAQ.mediawiki index a6fe7f3..9f09c56 100644 --- a/FAQ.mediawiki +++ b/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.