There are points to a registry type of thing, but the Registry in Windows has one killer flaw; it's the only egg in the basket.

In Warp, the 'registries' are called ini files. There are two main system ones: os2.ini and os2sys.ini. However, an application is free to create and use its own ini file, so you can have your application use \\myprog\\myprog.ini if it needs those kinds of facilities. This is good practice because a program won't fsck up the system inis if something bad happens while it's accessing its ini file, and because you can keep the ini file sizes manageable; instead of a 20 MB file in ram all the time, there's an 800K file and a 1.2 MB file (those are the sizes of os2sys.ini and os2.ini on my system right now), and prolly several MBs of other ini files that are loaded when needed, and flushed out of memory when no longer required. It might slow startup down a bit (after all, the ini file has to be loaded into memory, then actually read), but it has payoffs in more efficient use of memory.

The one big advantage that the registry has over ini files is that the ini files are flat; there's only one level of app:key-value, instead of being able to nest them.