# Why Bike? > We were promised bicycles for the mind, but we got aircraft carriers instead – Jonathan Edwards That's why I'm building Bike. I think macOS needs more "bicycles for the mind". Bike is small enough to fully understand. Once understood it's flexible enough to be used for many purposes. Bike is small, but designed for real work. It’s fast. It can handle big outlines that break other outliners. Bike’s also fast at the basics–opening files, scrolling views, and resizing windows. Bike won’t slow your Mac down. Bike makes your work open and accessible. Outlines are stored in text files using standard file formats. Bike is also scriptable. Automate and extend Bike into your own workflows with scripts. Bike is just getting started. I’ve been building on the outliner idea for a long time, Bike is the next chapter. I hope you’ll give it a try, get a license, and let me know what to improve for the next release. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bikeguide.hogbaysoftware.com/why-bike.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.