Intro Download and install Frequently Asked Questions Tips and tricks

Homepage







© J.C. Kessels 2009
MyDefrag Forum
May 24, 2013, 07:29:28 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Why did you use the .MyD extension?  (Read 1908 times)
Leolo
JkDefrag Hero
*****
Posts: 98


View Profile
« on: April 05, 2009, 06:08:47 pm »

Jeroen,

Just out of curiosity. Why? Why .MyD?

Wouldn't have been better and niftier using .MyDefrag ?

I've always heard people talk about compatibility problems with extensions longer than 3 characters. But I still haven't seen those problems in real life.

And in this day and age we have Windows using a pure 32 bit (sometimes even 64 bit!) NT kernel, and we also have technologies like VFAT for FAT filesystems and Unicode for NTFS filesystems.

So, are those compatibility problems for real? Or are they just urban legends?

Kind regards.
Logged
amk
JkDefrag Hero
*****
Posts: 101



View Profile
« Reply #1 on: April 05, 2009, 06:21:18 pm »

May be better to use both extensions, .MyDefrag also as .Myd
Logged
Falcon4
JkDefrag Hero
*****
Posts: 141


teh Fighting Falcon™


View Profile
« Reply #2 on: April 05, 2009, 09:39:29 pm »

I'd been using .torrent files for so long, I totally forgot how long the extension ".torrent" is.

Good point, IMO. Making the script files ".MyDefrag" would eliminate compatibility problems with .MYD MySQL data files as well Smiley
Logged


F*ck Vista. Current system: Acer Extensa 4420/Turion 64 X2 1.9GHz TL-57 (upgrade from TK-57)/2gb HyperX RAM/160 HDD/Windows 7 Pro RTM x86
jeroen
Administrator
JkDefrag Hero
*****
Posts: 7155



View Profile WWW
« Reply #3 on: April 06, 2009, 06:59:17 am »

Wouldn't have been better and niftier using .MyDefrag ?
Perhaps it would have been allright to use a long extension, such as ".mydefrag". I don't know if that might have caused any problems, the standard is short extensions so I am just following suit. MySQL is also using ".myd", but in totally separate directories and not for doubleclicking, and MyDefrag will just exit with a syntax error if it is given a MySQL file.
Logged
Huggu
JkDefrag Hero
*****
Posts: 58


View Profile
« Reply #4 on: April 06, 2009, 08:52:46 am »

MyDefrag is designed for win2k and newer windows os. all those os support long extension. there should be no problems using long extensions and we avoid type collisions.

mysql for example is portable to other os and so the extensions needs to bee portable too.
Logged
Leolo
JkDefrag Hero
*****
Posts: 98


View Profile
« Reply #5 on: April 06, 2009, 02:20:53 pm »

Jeroen,

I don't know if that might have caused any problems, the standard is short extensions so I am just following suit.

Perhaps I'm nitpicking, but to be completely correct it should be pointed out that the short extensions were the standard years ago. They are no longer considered "standard". We have a lot of short extensions because they are a legacy and have been short for so many years, that it would be counter-productive to change them just now. It would confuse people.

However, for new programs, like MyDefrag, it's better and recommended to use longer extensions, to avoid collision with other programs.

Take a look at Microsoft, for example. They have also started to use longer extensions (.manifest files are a good example)

Also, using a unique extension gives you, as a bonus, the possibility of having an exclusive icon to recognize your files. Right now you are clashing with people who had personalized MySQL files with their own icon.

Given that MyDefrag is still a beta, I think it wouldn't be too disruptive to change the extension. It would cause very few inconveniences in the short term, and be better for the long term.

Regards.
Logged
jeroen
Administrator
JkDefrag Hero
*****
Posts: 7155



View Profile WWW
« Reply #6 on: April 06, 2009, 07:57:06 pm »

Right now you are clashing with people who had personalized MySQL files with their own icon.
The .myd extension is used by MySQL for 1 of the files in which a database is stored, in a special subdirectory with other database tables. Only the MySQL server uses these files, they are in a special format and they cannot be directly accessed, looked at, or changed by any other application than MySQL itself. They are internal files.

There is no chance of a clash, using a short extension avoids problems, and I like the ".MyD" extension and am also using it in the logo. I am sorry but in my option this is a non-issue and I will not switch to ".mydefrag" or something like that.
Logged
Leolo
JkDefrag Hero
*****
Posts: 98


View Profile
« Reply #7 on: April 06, 2009, 09:01:55 pm »

Ok. I agree that there's probably very few people customizing icons for different file extensions (most people don't bother doing that), so I guess that the clashing would be reduced to a few geeks with too much time in their hands Grin

And yes, using a short extension avoids problems with MS-DOS and Windows 95/98. But your program doesn't work under those operating systems, so in the end there's no technical benefit in using short ones.

It is, after all, a question of liking and preferences. If you like .MyD better, then I'm afraid I cannot argue with that Smiley

As the saying goes different strokes for different folks Wink

Kind regards.
Logged
robert
JkDefrag Supporter
***
Posts: 17


View Profile
« Reply #8 on: April 12, 2009, 07:16:27 am »

If I have a vote mine would be for "mydefrag", it's simple and completely unambiguous.

I just googled "myd" and sure there's nothing that really stands out as owning it (with the possible, just, exception of mysql) but there are a lot of minor contenders ("Myd recovery software collection", "Manhattan Young Democrats", "New Zealand Ministry of Youth Development").

OTOH, Google already knows mydefrag is you.

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.5 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!