If you’re used to developing on *NIX systems, coming to Windows can be a bit of a shock.
My goal in writing this article is to point out some of the pain points and, where I know they exist, some work-arounds.
Over the last few months I’ve seen a ton of confusion swirling around social media about how to help people who are new to Python development and software development in general get up and running on Windows quickly.
If you’re new to the world of Windows scripting as I am, the array of acronyms, technologies and access methodologies that you need to traverse in order to get anything done can range from bewildering on a good day to utterly derangement inducing on a bad one.
For the last year or so I’ve been working at a 100% Windows based enterprise development shop. They ship a fairly large and complex application for health insurance providers, which draws on many of the core technologies in the Microsoft enterprise stable.
Dear Sun;
When you tell me I hava Java (TM) updates available on my work Windows machine, I gleefully say sure why not and click through the installer, because generally Sun provided updates to my installed JDK don’t do anything evil, and with security and all it’s a good idea to stay up to date.