> Project scope is what worries me about my own hopes (or is it dreams?) for > Storm.
Supporting new databases is well within the wishes we have for the project, so you can continue dreaming about it, and maybe they'll even become reality at some point. > My "best" solution so far is to: > 1) finish making Storm work on adodbapi on Windows > 2) make a fork of adodbapi which will run on ado.NET using IronPython. > 3) make Storm work on that platform > 4) port adodbapi to IronPython on Mono on Linux. > 5) make Storm work on that platform > > I think you will agree that is a very large scope. It actually doesn't look like a *lot* of work, once the basics are in place. If we make Storm work with adodbapi, I'd expect that getting it to work with the other platforms should be a matter of tweaking it up, rather than a massive amount of work. > I hope that you will also see the potential of that scope. I personally > cannot see why any intellegent person would want to use either SQL Server, > or .NET, or IronPython, or Windows -- but there are millions of users (and (...) I'm sure quite a few of them have no idea about why we use that Linux thing either. :-) > In the future, will Storm communicate with the unwashed masses? It requires (...) I hope it will! As you've seen, there are people interested in seeing these databases integrated, and we do want help integrating them. > Glad to hear it. I will be happy to learn that my pessimism is unwarranted. Thanks for pushing us. That kind of conversation is actually welcome, as it makes everyone think a bit about what's going on. -- Gustavo Niemeyer http://niemeyer.net -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
