Thread: Project64 2.2
View Single Post
Old 22nd September 2015, 05:50 PM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
Join Date: Feb 2007
Location: In my hat.
Posts: 16,236

Originally Posted by Marcelo_20xx View Post
I guess they started to call "portable" because the USB era allowed many programs and games to be just copied in it and then executed on a different machine without any installation procedure...
Well that still has nothing to do with portability.

That means the configuration of the compiled software is portable.

The only way for the software itself to be portable is if it is designed that way. No amount of flashing EXE files over USB makes any difference there; it just sounds like a dumb expression end users refer for their ability to not have to re-configure software which actually isn't portable either way.

Not sure why USB should have to do with it. I'm sure when floppy disk drives were still the major thing, the Windows registry didn't even exist back then! So why wasn't this artificial context of "portability" so correct back then as it is now?

Originally Posted by Marcelo_20xx View Post
As of know many apps developers refers to "portable" when such app doesn't require any installation (thus writes on the registry)...
I wouldn't say it's surprising that these developers would willingly use wrong terminology if it's in their better interest to capitalize in their position of power over the users.

It's easy for developers to claim their closed-source works as "portable" because they only release for a single operating system where the "registry" even exists as a thing at all.

By the definition of portability you cite, any software that is available on a non-Windows operating system is automatically considered portable, because there is no system registry. I however disagree with that too, because it's not hard to make Linux- or Macintosh- or etc.-only software that isn't portable to other systems, like Windows.

Originally Posted by Marcelo_20xx View Post
Emulation as I see it should be locally configured on a per game basis because there isn't any single config that will run optimally for everygame, I am happy that since PJ 2.X you can have it this way...
It's a good idea, but there are approaches at emulation that don't need any per-ROM configuration at all and maintain complete compatibility with everything. For things like speed hacks or stuff like mixed or hybrid HLE then it sounds like a good idea to have per-game config, but I think that's a matter of personal approach.
Reply With Quote