-
Notifications
You must be signed in to change notification settings - Fork 0
§5. Platform Weaver vs. Architectury
Arno Dölinger edited this page Jun 30, 2026
·
2 revisions
Both Platform Weaver and Architectury solve the same problem — running one codebase on several platforms — but they solve it in different ways.
| Architectury | Platform Weaver | |
|---|---|---|
| Model | Abstraction API | Annotation-driven stripping |
| Code location | Separate source modules | Single file |
| Native platform APIs | Wrapped | Direct |
| Paper support | No | Yes |
| Runtime overhead | Delegation layer | Zero |
| Custom platforms | No | Yes |
| Compile-time elimination | No | Yes |
Architectury gives you a stable abstraction layer to code against, at the cost of a delegation layer and separate source sets. Platform Weaver instead lets you call native platform APIs directly in one file and removes what doesn't belong at compile time, so the shipped JAR carries no abstraction overhead. When two platforms differ only in naming, @Chameleon closes the gap without an abstraction module.