Wednesday, May 20, 2009

Wascana is over

Yes, I'm giving up on the dream. For most of my time working on the CDT, I've tried to help make it the C/C++ IDE for anything and everything. A lot of people flocked to it naturally mainly in areas where it had no real competition, especially in the embedded space. And lately I'm seeing a lot of uptake in the Linux desktop space as well. And looking at the vendors contributing to the CDT, it matches what they were investing in. And that's great. We've really met, and at times exceeded, the objectives we set out for ourselves.

But I always yearned for one more. The Windows desktop space. It was Microsoft Visual Studio 6 that got me into using IDEs and built my passion to work on one. And the CDT has always had Visual Studio as one of the bars we were working towards reaching. And as Microsoft reduced their investment on Visual C++, we were able to meet that bar and scream past it. I remember reading an article where they were struggling with indexing, an area where the CDT is now really strong. That was a proud moment for me.

Yet to really show we've met the bar, I felt we needed to have a real IDE distribution that had equivalent functionality to Visual Studio. That meant including a compiler and a strong SDK for building Windows applications. Wascana was my attempt at building that IDE. And I had a lot of great feedback on it. People loved the simplicity of a single install that gave them everything to do their work.

But a few things have happened since I started Wascana. Mainly, I switched jobs and am no longer working 100% on the CDT. In fact it is much less than that, probably just enough to fulfil my duties as project lead. So any work on Wascana would have to be on my own time.

And I need to be honest with myself and you, the passion I once had for CDT for Windows (which should have been the name of this project) is waning. As I blogged about last, my attention is turning to mobile. There are lot of really cool mobile platforms out or about to be released and there is a lot of opportunity in that space to make a difference. CDT for Windows, not so much. It's too much of a fight. A fight I don't have the time or the passion to fight any more.

I know a number of people will be disappointed by that. And to those who still want to see something like Wascana, I encourage you to carry the torch. I'm not going anywhere and would be happy to provide guidance. And who knows, maybe one of the vendors that I know sell a Wascana type thing will make their work more readily available.

Anyway, I'm very excited about what's happening in the mobile space. CDT has a huge roll there so my passion for that does not wane. In fact, there is one area that I think we really need to fix, i.e. CDT's build system, that can really help mobile app developers. And if I stop pushing for an internal builder and a fancy build model that I felt we needed to match Visual Studio and instead just provide a good Makefile editor and template engine, maybe we can dig out of that hole too.

9 comments:

  1. Doug, I know it's hard to put something to bed you've put your heart into. I still miss CodeWarrior after all these years. In the end, you have to be true to your own needs and not the expectations of others. Let someone else lead the charge now--you've done your part for Queen and country.

    For your mobile pastime, consider what we're doing in TML. We're going thru the process of widening the scope and your knowledge/mentorship would be perfect. One aspect may be Android NDK + CDT. There are others.

    Give me a shout sometime.

    -EC

    ReplyDelete
  2. Doug,

    Sorry to hear that you don't have the time to put into Wascana any more. I hoped one day to be able to build Objective C apps on Windows :-)

    Things don't always work out the way you plan though, and I know what it's like trying to drive hobby projects forward. In the end, you can take comfort in knowing you did your best and hopefully a good starting point for those that come after. It might be a long shot, but hopefully someone will pick it up and take it forward.

    Good luck in the mobile space!

    Alex

    ReplyDelete
  3. Mobile is indeed where it's at these days... I wish I had time to play with all these technologies.

    Wascana was (is) a great idea, but I always had the impression that it was kind of doomed - or at least a difficult endeavour. Maybe someone will take on your mantle!

    Have fun with the new technology!

    ReplyDelete
  4. Too bad about the "CDT on Windows" issue - names matter and I'm pretty sure you'd have more users and contributors with that name.

    ReplyDelete
  5. The name was one thing, but the real killer was the inability to host it at Eclipse.org. I'd have loved to make the C/C++ IDE EPP package a real IDE including the compiler and SDK.

    If the board ever sees fit to change the rules, I likely would start this up again to try and get contributions flowing. But that's easy to say since I don't see hell freezing any time soon.

    ReplyDelete
  6. Shame about Wascana - I don't think many people realised the value of it - a free, single download, single installation developemnt environment for Windows... Is there an alternative??

    ReplyDelete
  7. "Is there an alternative?"

    Err... Visual C++ Express would probably do it. Also free, and for commercial use too.

    Not as full featured (without VAX and other VS plugins), but probably much more user-friendly.

    ReplyDelete
  8. Yes, that's probably the other thing that's happened since I started working toward CDT on Windows. Visual C++ Express was born. There is much less need, other than for people building cross platform apps for an Eclipse base solution.

    ReplyDelete
  9. That's bad news :(
    I write windows applications but prefer Eclipse CDT over VisualStudio for its indexing, complex syntax coloring, refactoring, open-source'ness, support for many more languages (python, perl) and especially the fact that you don't need to "add file to project" but just create a project in an existing folder, define some includes and it works!

    IMO, the main thing CDT is still missing, is a "cl.exe" tool-chain support, cause this is the real compiler for windows, and not MinGW.
    with every CDT release i hope it comes ... but i guess it won't happen soon ...

    anyway
    Thank you for everything, its really a pleasure using CDT!

    ReplyDelete