TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Best vs. Easiest Tool For The Job, or Why I Dislike Microsoft

1 pointsby eykanalover 11 years ago

1 comment

sqqqrlyover 11 years ago
I have nothing against grandmothers, but I think of Windows as an OS designed for grandmothers. Everything has to be &#x27;easy enough for one&#x27;s grandmother&#x27;. There is nothing wrong with that. But I am, just a bit, beyond that level. I find it cripplingly limiting.<p>Windows has become so simplified that it does nothing easily...unless all you do is play solitaire and read web pages.<p>This is true of most MS applications. They are all project based. Two clicks and you have a working project. It is great for a MS sales demo. But when you have a real world task and it needs to move beyond a MS project template....look out.<p>I much prefer process tools. They do very little for you. There are no two click projects. You have to know what the process pieces do. The advantage is that they will connect in an infinite number of ways but this requires sufficient knowledge. The perfect example is the Linux command line (|).<p>An example: In the 90s I had a MS universal subscription that included support. It was a great deal. I needed to create a web frontend to a database. Two clicks...working. Nice. Then I noticed that data was stale. Newly inserted data in the database did not appear in my application wo restarting it. I could not figure it out. I called support. A MS engineer helped me. He was great, an expert. It took him a <i>man-week</i> to fix this!<p>I recently did something similar - a TCP server using Python and MySQL. It took a little longer to get anything to work. But I did not need an &#x27;expert&#x27; to meet the last requirement.