edit: original title was editorialized to to claim that doing this was a perversion
No it is not an ideal platform but sometimes factors outside your control make it the best/only option if you want to use Django/Python. I work in a largeish very Microsoft dependent hospital and getting infrastructure support (hardware, database backups etc) from the IT department requires a Microsoft stack.
Being able to deploy a Django project on either Linux or Windows systems from a single code base is a pretty big advantage for me.
 Windows Server 2008R2 / MSSQL
If someone works quicker and better in a given dev environment, power to 'em.
If someone works quite a bit better in Windows, OK... but I think it's a far better idea to mirror your deployment environment as closely as possible, not just in staging/testing, but on your development machine as well.
That's not always practical, but working in an environment you should know doesn't even vaguely approximate any deployment scenario means you will miss any platform-specific issue that would have been obvious if you were staying closer to your deployment platform. At best it will be found during testing/staging or by another dev who's using a more appropriate environment, but that's several extra steps and extra time that wouldn't have otherwise been necessary.
A massive waste of time.
Is there something about Python on Windows that isn't stable or are there specific package/modules that Django requires that have issues?
(just a joke, but cannot resist)
I wonder if they kept the default layout to keep it as simple and "out of the box" as they can in order not to confuse newcomers to the Visual Studio way of doing things.
- Install SUA
Eclipse Python support is lacking.
NetBeans seems to come along pretty well, I just hope that they have more support.
what is it lacking exactly? (using Eclipse with Python daily for the last few years)
Anyone know if IDEA really the best multi-language Eclipse alternative, or is there something better?
Other IDEs I have used:
- Aptana (PHP, html/js, css, python). It's really a fork of eclipse with some additional features. If you want a free IDE, it's better than eclipse, but not quite as good as intellij.
- Visual Studio (2005, 2010, 2012). Great if you are doing C# or F# and combine it with Jetbrain's Resharper. Not as fond of it for other languages though. I've heard JS support is also very good now, but my web development is all scripting languages like Python and PHP so it does not help me much.
- NuSphere's PHPed. A good natively compiled IDE for PHP and web, but development kind of lags behind other IDEs and a few bugs that were never fixed when I used it would constantly annoy me. Also, only Windows unless you do WINE (it worked well enough on WINE though).
- Eclipse. Eclipse interface is clunky and honestly, it's slower than Intellij or any of its derivative cousins. Aptana improves on it though. Used Eclipse for a couple of years before finding Aptana and then moving onto Intellij.
It's not just about the IDE though, jetbrains in general is a great company. Despite English not being their first language for many employees, they have awesome customer service and are very up front about their road map and interact with their users directly.
I've used some commercial IDEs in the past, such as NuSphere's PHPed (which was a decent IDE at the time, not sure how it is now). PHPed's developers did not speak English as their primary language either, but they did not have anywhere close to the same level of interaction and support. Jetbrain's bug tracker is open for anyone to report on and they actually fix stuff you report (filed a few reports over the past few years, all were eventually fixed).
Maybe I'm just getting overly excited over what any decent company should be doing in the first place. However, many IDE vendors do not seem to do that overly well. Having confidence in the developers of your IDE is important (at least to me) and that they are listening to their customers/users.
The VS 2012 betas tried putting all caps on various parts of the UI. They got tons of pushback on that, so they eventually just made it the menu so they could still claim they kept the principle idea alive. In the final release, there's an option to turn it off.
A lot of VS devs are happy that they added a proper dark mode, and there's a plugin to autohide the menus so it's less of an issue that it appears at first. The biggest usability issue is the single-colour icons.
There's probably amazing internal threads and all sorts of political issues surrounding the design. In the end, I think the champions of the change count on wearing you down, making their opponents feel silly for arguing over such petty things as menu styles.
It's been my personal experience that PyCharm's Run/Debug configuration is fast to restart in Run mode, but considerably slower in Debug mode, taking 5-10 seconds to restart and attach the debugger. So while I'd like to be able to work with breakpoints and inspection always available, in practice those tools have been harmful to my productivity.
If VS is better or faster in this regard, it might be worth a try.
I prefer to do as much without debugger and then when I need to inspect variables and step through code drop into debug mode.
With Python this may be different but I doubt it. I expect you will have to wait while the debugger loads up. If you can edit code whilst debugger is running then I can see that being a big plus and a reason to keep it on.
Maybe they got it to be easier in Azure, still, here's a couple of things they didn't show how to do and is usually a pain:
- serving static resources (easier with newer Django versions, still)
- serving in a subaddress (like serving it from mycloud.com/myapp)
- Using MSSQL with it (there are Django adaptors, but last time I tried there were some issues)
About a month ago someone posted an essay on the Python Requests library in a literary journal and titled it something like "A Literary Review of the Python Requests Library", which essentially described what the essay was about: a review of the Requests library as if it were a literary work (http://thediagram.com/12_6/rev_reitz.html).
I noticed this, read the article, and enjoyed reading about Python in an entirely different context.
But then some wise soul determined the word "literary" to cause far too many sensations and updated the title to "Review of Python Requests Library"(http://news.ycombinator.com/item?id=5073250), changing the title from something apt to something misleading. As a review of Requests for the HN audience it isn't very good (the review is accurate and well-written in its context, but my guess is a review containing the sentence "Requests is written in a programming language called Python that's known for being easy to read" is perhaps not aimed at the average HN reader looking for a technical review), but as a review of a Python library as if it were a literary work is both funny and thought-provoking.
Would the article have gotten any more attention under its original title? Maybe, maybe not. But this happens noticeably often and it would be nice if folks changing these titles puts a bit more thought in to some of those changes, and not strip out those words meant to describe why someone here would read an article.
From the HN submission guidelines:
> ... please use the original title, unless it is misleading or linkbait.
I regularly use Komodo Edit (100% Free) and it is pretty good, the IDE is even better if you want a more involved tool. This is probably my favourite for a "windows like" experience.
here is something with a bit more detail - http://tartley.com/?p=1277
They're giving out bad advice to sell bad tools. I'm a little disheartened it's got so much attention on here.
Hence the promotional 'articles' like this from Microsoft.
People bitch and moan about Microsoft being closed off from the rest of the development community, then when they offer the rest of the development community a way to use VS to write in their language of choice, they get this crap.
A lot of what Microsoft does is shit, but the constant and pointless anti-MS circle jerking is ridiculous.
I just think this is a crap way of doing Django. Just like developing Silverlight apps in VIM would be.