![]() ![]() CraftOS does add in some extra code to allow accessing networked peripherals through the base peripheral API, but other than that, what the system already provides is enough for pretty much all use cases. ComputerCraft's simplistic peripheral interfacing API removes most of the need to manage hardware manually. Contrast this to a real system, in which hardware has to be memory mapped or controlled through arbitrary I/O ports components can have various interfaces that are not compatible with other versions of components of the same type and access has to be abstracted for effective use. Hardware (peripherals) is automatically handled inside the mod through the peripheral API, and hardware is exposed through a simple object-oriented-like interface. According to Wikipedia: "An operating system (OS) is system software that manages computer hardware, software resources, and provides common services for computer programs." However, much of this is not really possible to accomplish in ComputerCraft. The term "OS" is thrown around a lot, and in my opinion it's very overused. There are many common misunderstandings and undersights that newbie developers run into when writing an operating system, and these end up creating mediocre products at best. Usually, there are some very obvious flaws in these "OS"es, ranging from poor design choices, to overstating what they are and underdelivering. People look at the limited command-line interface that CraftOS provides, and think, "I want this to work like my normal computer does!" Time and time again, a new post pops up on the ComputerCraft forums or Discord either announcing an OS, or asking for help with an OS, or releasing an OS. One of the most common projects I've seen for ComputerCraft is to write an operating system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |