Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a Windows bias by consistently referencing Windows as the default development environment, prioritizing Windows-specific tools (Visual Studio, .NET Core SDK, Simulator.exe), and providing step-by-step instructions tailored for Windows users. Linux and macOS environments are mentioned only as an aside, with no detailed instructions or examples. The use of Windows command prompts, Visual Studio, and references to Windows-based hardware further reinforce this bias. There are no explicit Linux build/run examples, and Linux alternatives are not presented in parallel or with equal prominence.
Recommendations
- Provide explicit Linux and macOS instructions for all supported SDKs, including prerequisites, build, and run steps.
- Include Linux-specific examples for building and running the TPM simulator (e.g., using gcc, make, or cmake on Linux, and running the simulator as a native Linux binary).
- Reference cross-platform tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio, or provide CLI-based alternatives.
- Ensure all command-line examples use cross-platform syntax, or provide both Windows and Linux/macOS variants.
- Mention Linux package managers (apt, yum, etc.) for installing dependencies like Git, Node.js, Java, and CMake.
- Clarify hardware requirements for Linux users (e.g., how to check for TPM 2.0 on Linux, and how to interact with it).
- Where Windows-specific binaries are referenced (e.g., Simulator.exe), provide or link to Linux equivalents (e.g., ELF binaries, build instructions).
- Reorganize content so that Windows and Linux/macOS instructions are presented in parallel, not with Windows as the default.
Create Pull Request