Visual Studio and Microsoft go Python

Microsoft Technical Computing Group has released a beta version for its Python integration for Visual Studio.

This is, indeed, interesting development, as it clearly shows that Python has reached a new level of  programming language maturity.  Receiving this much of attention from mighty Microsoft means that Python is no longer a mere prospect member in the cabin of enterprise solutions.

Python Tools for Visual Studio are not focused only on Microsoft’s own .NET run-time: even Jython and PyPy are partially supported, claims the spec sheet. Looks like some kind of cloud integration is on its way – maybe Microsoft wants to challenge Google App Engine by providing even better cloud development tools?

Also there seems to be more information coming in PyCon…

\"\" Subscribe to RSS feed Image Follow me on Twitter Image Follow me on Facebook Image Follow me Google+

Thoughts about WP7

Now that Nokia made sure most of the energy put on Qt goes down the drain, I took a peek at Windows Phone 7 development and I was disappointed.

I posted a short comment to Future of Qt blog post and I thought I’ll write a bigger rant to make people more aware of an important issue.

The tools for WP7 are probably the best with Visual Studio and GUI editor and what else, I’m pretty sure about that, but the platform itself is disturbing: all code must be C#. You can’t use C/C++ with WP7. And when there can’t be those, there won’t be CPython nor Lua or any scripting language implemented without C# or .NET managing your code, unless you’ll find a C# port for it. And if you did, it most likely lacks in features compared to the original. And then there’s numerous other C/C++ libraries that you can’t use.

Somebody commented on my post saying this is the reason why the platform will fail and nothing except meaningless apps(fart apps,rss readers etc) will be ported. Apps with long history, existing code base and support for multiple platforms can’t be pure C#.  And I agree 100%.

Microsoft wants to avoid fragmentation, well that’s good but not with these restrictions. Lack of “unmanaged code”, as native code is called in .NET land, will be causing fragmentation, not the ability to reuse your code. It’s your code that’s fragmenting so MS doesn’t care. This is even worse than the Apple’s ban on scripting languages, which was removed a while ago. They still allowed reusing old C/C++ libraries, like physics engines in your apps.

If WP7 ever gains popularity among major app/game makers, I believe and wish they’ll make this issue clear to Microsoft as they (I assume) did to Apple. Well, first they need to gain popularity among consumers 😉

Without knowing much about the internal workings of WP7, I don’t see reason to block native libraries. Sure, it’s harder to avoid dll hell with C/C++ as the problem is well known on desktop. But if my app doesn’t use any system libraries but only its own? How many system libraries do you think a physics library might need? How many system libraries does a Lua interpreter need? I can think of one: libc for allocating and freeing memory. All those libraries do is reserve some memory and do some math and give some results back. Sure scripting languages may allow file access etc., but that’s not necessary. I just want to script some logic of the app, not the whole app. Anyhow, I don’t see the point, somebody, please enlighten me. Google & Apple can do this without getting in your way, why not Microsoft?

I have been reading discussions about Nokia-Windows deal, and only fraction seems to think that the whole Nokia-WP7 thing is a good thing. And those who do seem to be… less informed. The only good thing here is that we are finally getting rid of Symbian, but the price is too high.

So what’s the main reason that I’m worried about: to force people use .NET and me to write only C#. We have now witnessed what happened to people skilled with Symbian C++, the fear that I heard soon after Nokia started using Symbian. So don’t try to get us stuck with a single way of doing things. Sure there’s monotouch and monodroid to reuse your code on iPhone and Android. Not sure about them though, not free and they add another layer of complexity to your app. Easier to just learn the platform’s own way. I have no trouble using C#, but that’s not the point: I want to reuse my old code and the other libraries out there. Apple is good boy compared to MS.

And my opinion about C#? Nice, but Qt Quick rules. Sadly, now I can only think that it should rule. *sigh*… back to the drawing board.