this is more like a poll that should be posted some where else, but lets see what happens...
why is the new naming convention "myVariable" why the my?
its bad enough MS wants everthing to be me.whateverWeArTalkingAbout.Value.
im sorry i just hate My Pictures, My Documents, My Crappy Computer...
sorry im a DOS & NIX guy and get aggro over Microsft crap.
anyways lets have fun...tell me what you think pro or against the above. this should be fun.
I will answer only if this thread is moved to general discussions. lol haha haha lol
bump::move this mofo
You just need to get used with it.
Every company has their own ways of naming things and you can't blame them because you're not used to theirs.
"The Internet treats censorship as damage and routes around it." - John Gilmore
ok. now this thread is in general section. lol.
i like the convention My Documents, My Pictures, etc. they are so clear and make my PC a Personal Computer
and when in doubt it is better to use the name, mycout, than using cout, for example. lol haha
I don't see the point in bashing microsoft for something like this. MS bashing is a popular sport, how come i dont see you complaining about KDE's naming convention of having K as the starting letter in most applications ?
Code:>+++++++++[<++++++++>-]<.>+++++++[<++++>-]<+.+++++++..+++.[-]>++++++++[<++++>-] <.>+++++++++++[<++++++++>-]<-.--------.+++.------.--------.[-]>++++++++[<++++>- ]<+.[-]++++++++++.
1. The naming convention was probably used to appeal to the everyday user. I find nothing wrong with it.why is the new naming convention "myVariable" why the my?
its bad enough MS wants everthing to be me.whateverWeArTalkingAbout.Value.
im sorry i just hate My Pictures, My Documents, My Crappy Computer...
sorry im a DOS & NIX guy and get aggro over Microsft crap.
2. How does .NET have anything to do with this thread?
3. I'm not a Microsoft hater just for the sake of hating Microsoft nor do I consider myself a Microsoft hater. They have good products and not so good products. XP is a good product. Vista is a not so good product. MSVS 2005 is an excellent product, DirectX 9 is an excellent product, MSVS 6 was not, DirectX 3 was not, and DirectX 10 is perhaps showing to also not be what it was hyped to be. Some of their API documentation is rather convoluted, incorrect, etc., but so is every other company's API docs.
The things that irritate me about Microsoft have nothing to do with what is in this thread. I think I'll stop right there.
may be he wanted a general discussion on naming conventions.
i don't have any problem with any naming convention, be it JavaSources, MS, or linux_kernel.
but just for the discussion i want to know why a command that prints the running process list is called ps on *nix of course?
Last edited by manav; 03-29-2008 at 07:36 AM.
When someone comes up with a convention, it is usually for a good reason. Variable naming conventions are vast and varied. MS's happens to be called Hungarian notation. The intent, I suppose, is to lessen the burden on the programmer to go digging the include files to figure out what data type a particular variable is defined as. If all "ints" start with "n", then whenever you see a var that starts with "n", you can go with the assumption that it is an int. Saves time. I prefer a well defined naming convention.
Todd
Mainframe assembler programmer by trade. C coder when I can.
I believe he was talking about the naming convention used for folders and such in the OS, not actual code.When someone comes up with a convention, it is usually for a good reason. Variable naming conventions are vast and varied. MS's happens to be called Hungarian notation. The intent, I suppose, is to lessen the burden on the programmer to go digging the include files to figure out what data type a particular variable is defined as. If all "ints" start with "n", then whenever you see a var that starts with "n", you can go with the assumption that it is an int. Saves time. I prefer a well defined naming convention.
It is still better then the iCrap style that is plaguing everything it seems.
The "My Foo" style does make sense if the user can only ever see their version of it. Then it seperates the personal files (MY files) from the public files.
Actually, I like the Hungarian notation, think about it: "pcRAMDriveFSBuffer" is more descriptive and takes less characters than "ram_drive_fs_buffer" (although it's not always as easy to read)
But I also dislike My Computer, My Documents, etc.. We should start calling it My Internet Explorer , My Wordpad, My Calculator, My Visual Studio, then too.
The 'My' thing/convention makes sense. It clearly identifies the real purpose of those folders and directs users to them (even though I've never, ever, used them). It has my vote.
As for myVariable... why not? My personal library resides entirely on the 'mjpf' namespace. Inside I have several private objects prefixed with 'my' to help me distinguish what is not going to be made accessible from what is.
Since we are on the subject of folders and files, you know what I would like instead? If everything was more like Plan 9.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
when you try access My Documents of other user (say Bob) you really see Bob's Documents...
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
awsome...
my beef is just that my is usually very vague, in both programming and file structure. if i accidently save a project/file in the "My" part of windows i usually figure it for dead and use save as instead of searching through all that crap that is 'supposed' to make it easier.
the naming conventions I use are far different because 'my' doesnt tell you anything except in Mario's case. If I were to pick a variable name it would be local but at the same time tell me what I am doing with it. like lNameConNum (because im working on a soundex algotrithm....)
however to each their own!!!
this convo was started to see what the rest of the world thought and like a seinfeld episode.. is really about nothing.
cheers.
