4 ms·

> Back then they didn’t really understand the point of ssh though. As an outside observer, it really looked to me like Microsoft had their head in the clouds u

> Back then they didn’t really understand the point of ssh though. As an outside observer, it really looked to me like Microsoft had their head in the clouds up until about 2011. It's like the whole decade between 2005-2015 for MS was about recognizing and coming to terms with the multiple "whole worlds out there" and getting past NIH syndrome.

kwccoin 8y ago
To be fair to Kodak, it is very hard to invent digital photography but fail greatly to use it. Or Xerox, ... or IBM who is the largest PC seller exactly the time when it was overwhelmed by Microsoft. An organisation large enough would have middle management and people who promote from within. And they are successful in one culture and it worked even for customers. Then ...
slededit 8y ago
They understood the GUI couldn’t be everything but NIH was definitely in full swing at that time. It was enforced from the top: If you wanted to use an external product and MSFT had a competitor you needed VP approval. Same went for Open Source. Only the most senior people would even attempt it, and it was understood they were spending political capital. The one place this didn’t apply was your choice of code editor. You could use whatever you wanted and that had long been tradition. I spent a lot of effort getting VIM to work only to realize it didn’t scale well to multi-million LOC code bases.
- killjoywashere 8y ago
  As someone who uses Vim on relatively large files daily (500k - 1.5M lines), where were the hangups?
  - slededit 8y ago
    The speed of navigating the code base. Ctags existed but people using SlickEdit or Source Insight were able to navigate the code base dramatically faster. As a new hire I wasn't going to get code annotations emitted as part of the build, so an editor with a proper parser was key. Really had nothing to do with the size of the file.

kwccoin 8y ago

To be fair to Kodak, it is very hard to invent digital photography but fail greatly to use it. Or Xerox, ... or IBM who is the largest PC seller exactly the time when it was overwhelmed by Microsoft. An organisation large enough would have middle management and people who promote from within. And they are successful in one culture and it worked even for customers. Then ...

slededit 8y ago

They understood the GUI couldn’t be everything but NIH was definitely in full swing at that time. It was enforced from the top: If you wanted to use an external product and MSFT had a competitor you needed VP approval. Same went for Open Source. Only the most senior people would even attempt it, and it was understood they were spending political capital. The one place this didn’t apply was your choice of code editor. You could use whatever you wanted and that had long been tradition. I spent a lot of effort getting VIM to work only to realize it didn’t scale well to multi-million LOC code bases.

killjoywashere 8y ago
As someone who uses Vim on relatively large files daily (500k - 1.5M lines), where were the hangups?
- slededit 8y ago
  The speed of navigating the code base. Ctags existed but people using SlickEdit or Source Insight were able to navigate the code base dramatically faster. As a new hire I wasn't going to get code annotations emitted as part of the build, so an editor with a proper parser was key. Really had nothing to do with the size of the file.