4 ms·

Erm... I sort of figured it out years and years ago, and I do work in plain vim. (Hence to me there's no difference whatsoever between one Linux distro and ano

by _yosefk 11y ago

Erm... I sort of figured it out years and years ago, and I do work in plain vim. (Hence to me there's no difference whatsoever between one Linux distro and another, because in any case I can only get plain vim and plain grep to work and not much else. So I won't reply wrt Debian vs Ubuntu except that the other standard reply that I get apart from "running old software" being wrong is, I always seem to be using the wrong distribution. I think the one thing that unites all the distros is that each of them is always the wrong one...) The difference is that on Windows I can run VS just as easily as I can run vim.

ploxiln 11y ago
One time I wanted to edit and compile a large open source application on windows... can't just run a build, have to open the project file in VS... VS has to index the source code for intellisense, slows down the whole interface and uses a full gig of memory, and I haven't started a build yet... Really, I'm just quite biased against windows in particular, because I had only Windows 98 and Windows XP when I first came of the age to have and tinker with my own computer, and the amount of stuff that you can't control and can't fix (installing common software, networking, file sharing, drivers) is infuriating. If something only runs on Windows, that's it's biggest flaw. EDIT it's an easy potshot so I'll throw in this link http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2156195-fix-260-character-file-name-length-limitation http://visualstudio.uservoice.com/forums/121579-visual-studi...
- vitd 11y ago
  Well, I've had the opposite experience. I wanted to build a basic open source package for unix on my Mac. I got the source and followed the instructions to "make whatever". It failed with highly cryptic errors that I later learned through lots of searching meant there were dependencies on other open source projects I didn't have, and all of which had the same sort of dependency problems of their own, and some of which didn't have the proper config files for building on a Mac. I gave up. But honestly all of that misses the point. The article is talking about typical users, not developers. Building stuff is far beyond people who don't know what a browser cookie is.

by _yosefk 11y ago

ploxiln 11y ago

One time I wanted to edit and compile a large open source application on windows... can't just run a build, have to open the project file in VS... VS has to index the source code for intellisense, slows down the whole interface and uses a full gig of memory, and I haven't started a build yet... Really, I'm just quite biased against windows in particular, because I had only Windows 98 and Windows XP when I first came of the age to have and tinker with my own computer, and the amount of stuff that you can't control and can't fix (installing common software, networking, file sharing, drivers) is infuriating. If something only runs on Windows, that's it's biggest flaw. EDIT it's an easy potshot so I'll throw in this link http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2156195-fix-260-character-file-name-length-limitation http://visualstudio.uservoice.com/forums/121579-visual-studi...

vitd 11y ago
Well, I've had the opposite experience. I wanted to build a basic open source package for unix on my Mac. I got the source and followed the instructions to "make whatever". It failed with highly cryptic errors that I later learned through lots of searching meant there were dependencies on other open source projects I didn't have, and all of which had the same sort of dependency problems of their own, and some of which didn't have the proper config files for building on a Mac. I gave up. But honestly all of that misses the point. The article is talking about typical users, not developers. Building stuff is far beyond people who don't know what a browser cookie is.