5 ms·
I'm imagining a bunch of suits getting together deciding "Time to start working on the next generation of COM... COM2!". And then the first developer gets read
by 0x0 15y ago
I'm imagining a bunch of suits getting together deciding "Time to start working on the next generation of COM... COM2!".
And then the first developer gets ready to write some code, and goes "Explorer->Right click->New folder->COM2".
After a few attempts and some head scratching:
"Uhh.. I think we need another name"
- chris_wot 15y agoThat's interesting. But try creating a folder called .NET in Windows explorer... :-) Hint - you can't!
- 0x0 15y agoNice! So when they couldn't use a reserved folder name, they went for the next best thing ;)
- steverb 15y agoSure you can. Create a folder. Rename it to ".Net.". The dot at the end of the folder name is important.
- chris_wot 15y agoInteresting. But they didn't call it dot-net-dot :-)
- Dylan16807 15y agoExplorer silently strips the trailing dot and is tricked into doing the right thing.
- mkopinsky 15y agoThis becomes quite annoying when I try to create a .htaccess file. (Command line rename is the only solution I've found.)
- rbanffy 15y agoCygwin. Don't use the Windows command line. Just don't. And while you are at it, use PuTTY-based Minterm instead of the Windows console.
- mkopinsky 15y agoCan you explain why? I use cygwin when I need GNU-like tools (sed, grep, etc.) but for something like renaming a file I don't see the point of using a slower terminal that requires more typing ( cd /cygdrive/c/Doc<tab><wait>/mkop<tab><wait>/Desktop/bla vs cd \Doc<tab>mkop<tab>Des<tab>bla ) just so I can type "mv" instead of "rename". I've never used minterm. What does it do better?
- tom9729 15y agoUse MSYS (part of MinGW) and Console2 (set bash as shell). cd /c/Doc<tab>/mkop<tab>/Desktop/bla
- mkopinsky 15y agoThis doesn't answer my main question, which is WHY? What do these tools do better (enough to matter)?
- tom9729 15y agoI prefer the Unix command line everywhere. MSYS gives you a Unix shell, and all the Unix tools, built right on top of win32. I haven't used it in years, but I understand Cygwin is quite a bit heavier. The cmd.exe terminal is atrocious. Even if you don't want to use Bash, Console2 gives you things like tabs, and you can resize the window normally. tldr; It's not slower, it doesn't involve more typing, it gives you a sane Unix command-line experience on Windows.
- rbanffy 15y agoWith Cygwin, your home directory should be your WINHOME (I'm doing this from memory, bear with me), so, in fact, your cd would be cd Desk<tab>bla or, worst case, cd ~/Des<tab>bla Running programs is also a tiny fraction of what bash can do - it's a full (well... almost) fledged scripting language and you can do things like loops, conditionals and other stuff. Before I discovered watch, I'd do things like while true; do df -h ; sleep 10 ; clear ; done Also, the PuTTY-based console has a lot of niceties when compared to a plain console window - it's prettier, you have better font controls and better clipboard integration.
- quink 15y agoThey should have just incremented the last letter of COM to create the new version CON. Explorer->Right click->New folder->CON... Oh.
- cek 15y agoYou have a good imagination. I worked on COM at Microsoft. We had a project to add managed run-time capabilities to COM. This was ~'96. Internally we thought of the Component Object Model that shipped as part of OLE as "COM version 1". The version that supported distributed capabilities (aka DCOM) as "COM version 2". When we started working on adding managed runtime support we started talking about "COM 3". But that talk stopped quickly when I tried to create a directory named COM3 for some specs. Creating the directory wasn't a problem. But putting anything in it or deleting was. We quickly settled on the name "COR" for Component Object Runtime instead. We actually released the COR at the '96 (I think) PDC as an alpha. But it never actually shipped because .NET won the internal battle (full IL based managed runtime to replace COM vs. incrementally adding garbage collection and other managed capabilites to COM ala Objective-C). Later on, as the MS Transaction Server group was merged with the COM team, the name COM+ was invented to cover "DCOM + Transaction Server + MSMQ". This led to the fabled Project42 which I have chosen to forget.
- 0x0 15y agoWow, haha, thanks for sharing that. My old suspicions finally confirmed! :)
- acqq 15y agoI remember reading articles about COM+ which didn't mean MSMQ but looked more like something close to what .net framework became. Then I've read that Msmq and thought "what?" Wasn't then COR the first mentioning of what you name COR?