KENSSharp or KensSharp?

[Clownacy]

This is a nitpick, but I figure it's at least worth mentioning, since it bothers me every time I see it.

The naming of this is pretty inconsistent: the repo is named 'KENSSharp', but the installer calls it 'KensSharp', and this happens in a lot of other areas too.

Personally, since 'KENS' is an abbreviation, I prefer the former, but admittedly it is a little harder to read. Not to mention, since 'KENS' only stands for 'Kosinski, Enigma, Nemesis, and Saxman', it's a little inaccurate now that Comper and Kosinski+ have been added, but maybe that's an issue for another time.

[MainMemory]

KENSC+Sharp then? Although that reads more like 'KENSC' Plus 'Sharp' as if it's a combination of two things.

[Clownacy]

If we ever made this feature-equivalent with KENSC-FW, we'd have Rocket compression to worry about, too. And if we wanted compatibility with S2NA GHZ, we'd need Chameleon compression as well. I don't think we can keep tacking letters on.

Also, just a side-comment, I thought the reason this is called KENSSharp/KensSharp and not KENS# or KENS-Sharp was to avoid using symbols? IIRC, Kosinski+ is referred to as 'KosinskiPlus' in a few areas of KENSC-FW's source for the same reason.

Now that I think about it, Flamewing did name his repo mdcomp instead of KENSC-FW. I'm not sure if a total rename would be a good idea, though. I mean, KENS is a pretty cryptic name, but would 'C# Mega Drive compression library' really be a good alternative? If we abbreviate it, we get 'CMDCL' but, well, we're back to the 'it's cryptic' problem.

At least KENS has made a bit of a name for itself. I think by this point people in the know realise it's synonymous with compression, so even if it's a slight misnomer, it still represents the project well enough. Kind of like how 7-Zip supports a bunch of formats, but is still called 7-Zip.

[MainMemory]

Why limit ourselves to MD compression formats? We could add PRS, and... uh... I can't think of anything else.

[FraGag]

The name is supposed to be KENSSharp. However, I agree that the name is outdated and I wouldn't mind if it was changed.

[MainMemory]

Well we could call it MMComp, since I started it, and to my knowledge all the programs using it were made by me. :v

[Clownacy]

Guess I should've said something at the time, but I'm not opposed to renaming this to MMComp. I think sticking your username in the project name is a good way to keep it distinct.

[MainMemory]

Um. I wasn't seriously suggesting that. For one thing, I had almost nothing to do with the actual coding of the project. I have no idea what it would be called instead though. As long as we keep it restricted to stuff designed for the Mega Drive, we could call it MDCompSharp or something. If we ever expand beyond that, SonicComp? SegaComp? RetroComp?

[Clownacy]

I don't think naming descriptively will work. Like you said, putting MD in the title will just make it invalid if we ever support a non-MD format.

SonicComp isn't the most accurate, since the KEN range of formats was used by more than Sonic. SegaComp isn't too accurate either, since Comper and Kosinski+ are custom. RetroComp... sure, chances are we'll never support anything from any of Sega's most recent games, but still, it seems like a needless limitation.

I think names just work best when they're arbirary. Otherwise you're left naming it after the handful of things that are basically guaranteed to never change, like how the library is written in C#, or how it's a collection of (de)compressors. I wouldn't mind if 'KENSSharp' stayed, really.

[MainMemory]

I meant "Retro" as in "Sonic Retro".

[Clownacy]

I guess that will never change...