Is it bad practice to write to the registry?

just for settings later and using a standalone executable with no way to remove it? Because I did, I do, and don't care. It just works.

config files or die

i don't give a fuck what's in my registry.
config files piss me off because you delete them and you're setting's gone.
write 'em somewhere deep in the registry and i dont hafta care about 'em. see no evil, hear no evil, speak no evil

fuck it pretty much every app in the world does this,
I still wonder how the fuck the bloatgistry holds together, it must be a programming masterpiece

You can store pretty much everything to registry. For example, it is perfectly acceptable to store all sound and image data to registry in binary format.

The registry is very convenient in many ways. The data is always available and it is common knowledge, that Windows system can read registry faster than it can read normal files located in Windows file system, since the registers are located in CPU itself.

It is possible to emulate filesystem with Windows registry. An ideal solution for any application would be to store the actual executable binary to registry and then create a simple loader executable that reads registry and creates executable memory block from it.

The registry is not only limited for storing any kinds of information. It can also be used for inter process communication. You can emulate shared memory just by creating common entry for applications in registry. Semaphores are also easy to implement. Just create a key with an integer value representing semaphore value.

The next version of Windows makes much more use of registry than current versions. It is rumored that the kernel itself is now mostly located in registry, leading to improved stability and speed benefits.

>>1
If you have several apps that have to share settings: use registry.

If you have single app that wants to look clean: use it's working directory for everything.

>>1
Yes, every windows program do that. Sometime later you have a bloated windows install even if you remove these shit altogether.
get your hands out of my registers

>>3
Reinstall/new computer and registry's gone.

>>5
Registry duplicates file system. That is: use good filesystem, like LMFS (Lisp Machine File System, optimized for many small files).

>>5
HAHAHAHAHAHAHA

no

>>8
Lisp
HAHAHAHAHAHAHA

no

Windows filesystem structure is so fucked up that they need to duplicate the filesystem on a more uniform bloat bag, the "registry".
FACT

Just look at how WINDIR looks like the crude output of lots of different builds. I even found some buildlog.htm in there.

<-- check 'em

>>10
Accept Lisp and your computing will be saved!

I really like using XML for settings files whenever I'm working on an open project that I intend for the user to be able to edit the configuration.

I like to use binary settings however for games, it's a lot easier to save and load a bunch of binary data for the player's current place in the game.

>>11
But why would a file need permissions in its own folder? That makes no sense!

>>15
Everything makes sense to some observer, because if it doesn't, said observer will be created to reduce entropy relative to information. This is how our universe works.

<-- check 'em
u mena ↑ check 'em ?

>>15
But why would a user need permissions in its own folder? That makes no sense!

Sussman and the Magical Dildos

I posit that file permissions is a cultural and non-scientific concern to keep the common man down.

>>22
amazing dubs bro

thank you

You're using the tool for it's intended purpose. It is correct to write configuration settings in the registry. Removing registry settings is the job of the uninstall routine.

>>23

>>1
with no way to remove it

>>24
with no way to remove it
How do you do that?

this is left as an exercise to the reader