Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Artifact ID: | eedb351649b3da3acf55537e1e82bb55e80dbf91a63373f3f66cafe82c538208 |
---|---|
Page Name: | Ecosystem |
Date: | 2017-12-17 05:20:29 |
Original User: | kc5tja |
Mimetype: | text/x-markdown |
Parent: | 1b0c9c2a964218b84249e2f63cd208d03a47ef2b1e97df3106a1997da81b1931 (diff) |
Ecosystem
Presently, the Kestrel-3 does not have any known users besides me. Thus, there's not much of an ecosystem at present. For this reason, the Kestrel-3's hardware is primarily optimized for my use-cases for the computer.
These are the types of applications I personally wish to run on the Kestrel-3:
- software development tools, especially for future Kestrel-3 enhancements
- basic hardware development tools (i.e. expansion peripherals for the Kestrel-3)
- basic Internet and amateur packet radio applications
- basic productivity tools
- simple 2D games.
As more use-cases are discovered, particularly as more users work with the system, hardware and system software changes can be made to accommodate them. For example, I intend on using the Kestrel-3 to help run a home business, so at least one variation of the design will be business optimized. Others I know who are interested in the computer prefer to write games, graphics demos, or compose music. This skews the Kestrel-3's hardware and system software design for these applications. It is through this iterative feedback approach that the Kestrel-3 will become a family of related computer designs.