March 31, 2008
On my talk at TechDays2008, I noticed the audience was looking more to integrate IronPython/IronRuby on their existing C# apps, than using it as a standalone language. In order to get one of this two languages in your application is to host a DLR engine.
It’s very easy to do this, so easy I guess it will be be used, even when it’s not the best solution (just an hintch). As usual, Michael Foord puts it plain simple, with a couple of examples for you to get started.
This is a great excuse to start allowing scripting over you application, using one (or even both!) of this great languages! As I mentioned in my presentation, there are power users who would want to code something in this languages (that are really, really simple!) and start using the full power of your application!
March 17, 2008
Quinta feira fiz a minha apresentaçãozinha no TechDays. Lá tentei convencer a audiência das vantagens (e algumas desvantagens, claro) das Linguagens Dinâmicas, e da sua utilização em .NET. Ficam por aqui os slides e os demos para o caso de alguém querer dar uma olhadela, mas ficava muito melhor contextualizado.
Para terem uma ideia, falei das razões que me levam a acreditar que as linguagens dinâmicas são o próximo passo (na evolução assembly – C – Java/C#) e em como são linguages muito mais alto nível. contei também um bocadinho da história do DLR e do estado actual das linguagens dinâmicas. Demonstrei a integração com o Visual Studio e a interacção com managed code em C#. Falei também das situações em que usar linguagens dinâmicas pode ser uma vantagem (e mostrei algum código exemplo). Acacabei referenciando exemplos de aplicações de IronPython no mundo real.
Deixo também alguns recursos adicionais para quem estiver interessado em explorar estas novas linguagens em .NET:
IronPython
IronRuby
DynamicSilverlight – Site específico com informações e tutoriais sobre linguagens dinâmicas para Silverlight
Aprender Python em 10 minutos para quem já sabe outra linguagem
Aprender Ruby em 20 minutos
Poignant Guide to Ruby – Um tutorial cheio de humor, para quem tiver mais tempo.
Michael Foord’s Introduction to IronPython - Muito bom para entrar em IronPython. É também o autor do primeiro livro sobre o assunto.
Learning IronPython – Um bom tutorial para aprender IronPython
Blogs:
IronPython
John Lam
Jim Hugunin
January 03, 2008
This post is a best-of my feedreadings of today. Some people do del.icio.us posting and I’m getting infected too.
I found about Port25, a website where is explained why Microsoft hates OpenSource! (NOT) I’m curious about what will MS say about OpenSource in 10 years. When maybe Ballmer is enjoying his retirement and someone from a different background (and younger) will decide what direction will Redmond’s still-big Giant take.
IronRuby vs Ruby.NET, a nice post by the IronRuby developer John Lam, a bit more of what I mentioned between IronPython and Python.NET.
I want the new Windows Mobile 6.1 new interface! I guess 6.0 should be called 5.1 and this one it’s the one that is the real 6!
Developer’s Hymn: pretty much self-explanatory.
A fan of Desktop Tower Defense? And you also like World of Warcraft? There you go: Hordes of Orcs! But OS X only for now…
Feeds still messy. Sorry but no time to fix it. Please bear with me and come visit my wonderful website :)
December 30, 2007
I love Python! I love .NET! Therefore I love IronPython. It let’s you do WinForms, Speech, WPF with XAML, work with ANY .NET managed library. I am even using it to do games with XNA! And the Visual Studio integration… It gives Python programmers the tools they dream about: A debugger, intellisense and a compiler.
(I will post about my IronPython adventures in the future).
But there is just one thing that I don’t like in it. It just isn’t Python! It is the Python Language, yes, but it’s not the CPython implementation. I am now stuck with two Python Consoles and there is no way of distinguish IronPython code from regular Python. Of course IronPython is way faster, but sometimes installing it and living with two pythons isn’t always the best choice.
That’s why I really enjoyed the Python.Net. It’s a way of extending Python to access the .NET framework existent in you environment. And now they are making it compatible with IronPython code! And you can still work with all the other python modules (Not all are yet implemented in IronPython). There is only one small problem: It’s alpha software and still very unstable.
I downloaded from the trunk and compiled it with VS2005. I made the binaries available for you and should work fine in Windows XP with .NET framework 1.1, 2.0 and even 3.0 with Python 2.5 except for this bug I reported. Check the readme anyway. It’s also possible to compile to use Mono, but if you really want it, you should be able to compile it yourself ;)
