4 ms·

>It doesn't sound like you do Windows development? I do, although I have only done it part time for about 16 months. And I don't do business software. I'm work

>It doesn't sound like you do Windows development? I do, although I have only done it part time for about 16 months. And I don't do business software. I'm working on a compiler in my spare time, and on an industrial dashboard for work. Both are written in plain C (plus OpenGL and FreeType for the latter) and run under Linux as well. Command window and batch files are still way more productive for me than using a pile of junk that I don't understand, hidden behind an IDE that I cannot automate.

AnIdiotOnTheNet 8y ago
"I don't want to bother learning to use the good tools, so I'll just base my opinion on all the shitty ones".
- jstimpfle 8y ago
  Would you care to substantiate your accusations? What tools do you think are superior to approaches that let you control what happens, and do not require you to push all operations through a slow, RSI inducing, non-automatizable GUI?
  - zaphar 8y ago
    You absolutely can automate the GUI. People make very good money doing exactly that. The key difference is that the barrier to doing that automation is higher than automating a CLI.
    - jstimpfle 8y ago
      Ummm... No. Thanks, but no thanks. And I'm not interested in registry cleaners, either.
johannes1234321 8y ago
"... that I don't understand ..." might be core to the problem. With your Linux/Unix tooling you have a lot more experience and invested time in learning. That knowledge isn't easily transferable. I noticed the same when I once in a while try to do "simple" stuff on Windows. However if I look at my full-time Windows colleagues they have comparable productivity on Windows to me on Linux and fail on Linux similarly to me on Windows. I could sit down and learn, and sometimes I do a bit, but for the larger time my interests are elsewhere.