elie/PhoenixPE
1
0
Fork 0
mirror of https://github.com/PhoenixPE/PhoenixPE.git synced 2025-09-16 10:08:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update Apps, New RequireDriver API, Add TPM passthru to vmware, HiveEdit define custom prefix

Browse Source
This commit is contained in:
Homes32
2021-12-18 10:21:29 -06:00
parent 2e1d6613c9
commit 8b5e4f7799
24 changed files with 3287 additions and 3051 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -32,10 +32,10 @@ No. PhoenixPE development started around 2014 as a Winbuilder project and was or
### Is PhoenixPE a replacement for Win10XPE?
No. Both produce a very similar environment based on decades of community members working together. We aren't in competition.
No. It's an alternative. Both produce a very similar environment based on decades of community members working together. We aren't in competition.
In my option the 2 projects have different goals. Win10XPE states that _"it's main objective is to be simple, user-friendly and to be as fast as possible"_. This caters well to user that just want to press a button and get a working PE without much fuss. Win10XPE does great at providing a simple, pre-packaged experience, however it's core codebase is cumbersome and inconsistent and in an effort to provide a simple user experience, it loses the flexibility and ease of customization advanced users crave.
PhoenixPE on the other hand targets advanced users and developers that what more control over how and what goes into their PE. It strives to be simple for both users to build, and developers to contribute to.
PhoenixPE on the other hand targets advanced users and developers that what more control over how and what goes into their PE. It strives to be simple for both users to build, and for developers to contribute/maintain.
TL;DR: No. If anything the projects complement each other and encourage developers to work together. Use the one that best meets your needs. You can't go wrong.
TL;DR: No. It's an alternative. If anything the projects complement each other and encourage developers to work together and share their knowledge and experience. Use the one that best meets your needs. You can't go wrong.