complexity
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 300
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
The discussion goes like this:
Q: "Why Linux? It is so complex and big!"
A: "So is UEFI PI, and now also U-Boot."
Q: "Yea but Linux is really big, see the lines of code?!"
A: "We configure a subset for use in LinuxBoot."
and so on.
In the end, a perfect 1:1 comparison does not really apply, since the mentioned projects already differ in structure. Overall, the question is about "features" (measured boot, network boot, graphical menu...) and the necessary modules/drivers. Complexity, a somewhat related point, can be hardly measured based on lines of code. Even structure. Having an overall understanding of the architecture and flow is what counts, which we get through thorough documentation; hence this book.
see also https://news.ycombinator.com/item?id=16259373
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified in the issue. Start by reading the surrounding book structure and the linked Hacker News discussion to determine whether a concrete explanation of LinuxBoot complexity is wanted; done should be a specific, agreed documentation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100