新项目即将推出......继续使用Python，或者使用点网络语言？请你的想法！ [英] New project coming up...stay with Python, or go with a dot net language??? Your thoughts please!
问题描述
简介主要问题
我是一家企业开发人员，为一家公司工作。得到了一个新项目
即将出现并想知道我是否应该继续使用Python进行这个新的，相当优惠的b $ b大型项目，重新回到''安全''M $使用点网的行车
语言？跨平台不是问题，但与MsSql Server（当前和未来版本）的完全控制/兼容性
肯定是。
快速历史
10多年前开始使用FoxPro，像Fox一样升级，是一个很好的
系统但是从来没有真正喜欢它因为很多因素我不会进入现在。
Delphi中有很多工作，一旦第5版出来......真的非常喜欢
一段时间。开始使用MS SQL服务器作为数据库。
如果要重新编写一个基于dos的旧数据库系统，可以使用很多
它在Delphi 7中，但真的开始出现Delphi的问题，甚至很多都很棒。
当我正在研究写道，有另一个较小的系统来处理，所以
我将不得不同时做两个......我开始四处寻找另一个
语言有了Delphi的问题，很长很短的故事，我用Python迷住了，并且使用它，用wxWindows编写界面，
和adodbapi.py进行通信ms sql server，我做了另一个较小的
系统。
令我惊讶的是，在很短的时间内我写了一个包装类
模拟使用Delphi ado记录集对象，围绕非常好的
（但有些限制）adodbapi.py模块。对于Windows用户界面，我还了解了如何使用股票资源编辑器创建wx资源文件
并将控件连接到代码。并且使用自由文本编辑器（pspad）我比使用超级duper点和视觉Delphi更有生产力。
好的，我得到了小系统完成得非常快，抛弃了我有问题的大系统的delphi版本的delphi版本，并将我的抛出
重新组合起来，完全免费的Python包，以及我发誓，如果我在Delphi版本之前就已经完成了，那么它就会结束。
好的，时间流逝，大系统继续得到改善等等......现在所有人都突然间，较小的系统需要增长很长时间，因为它已经变形了，并且需要所有这些新东西。
他们需要所有这些新东西。 />
DILEMMA
好的，我喜欢python，所以这不是问题，但是，我非常担心
关于它的增长。我最近重新访问了网络，看了很多项目
我认为现在已经开始运行一年多了，比如Boa
构造函数，Iron Python等...似乎所有这些项目都已开始，但是
从未完成。
此外，我需要越来越多*完全*控制ms sql从我的应用程序，
根本无法从adodbapi模块下载我从互联网上...
也，ms sql 2005正准备出来..如果那个写了
adodbapi.py的人不喜欢升级它，那么它甚至适用于MS SQL
SERVER 2005？ Yeesh ......你明白了......
所以，想知道是否有其他人有这些顾虑，如果没有，
为什么等等...任何投入赞赏。
Python情人，但很担心，
diego
The Main Issue in a nutshell
I am a corporate developer, working for a single company. Got a new project
coming up and wondering if I should stay with Python for this new, fairly
large project, are jump back on the ''safe'' M$ bandwagon using a dot net
language? Cross platform is NOT an issue, but COMPLETE control/compatability
with MsSql Server (current and future versions) certainly is.
Quick History
Started out 10+ yrs ago using FoxPro, upgrading as Fox did, was a good
system but never really loved it due to many factors I won''t get into now.
Did alot of work in Delp once version 5 came out... really loved it for
awhile. Began using MS SQL server as database.
Had a HUGE re-write of an old dos-based database system to do, did alot of
work on it in Delphi 7, but really began to have issues with Delp even
tho alot of it is fantastic.
As I was working on the re-write, had another smaller system to work up, so
I was going to have to do both at once... I began to look around for another
language as was having issues with Delp very long story short, I became
enthralled with Python, and using it, with wxWindows to write the interface,
and adodbapi.py to communicate with ms sql server, I did the other smaller
system.
To my big surprise, within a short time where I wrote a wrapper class that
emulated working with the Delphi ado record set object, around the very nice
(but somewhat limited) adodbapi.py module. For the windows user interface, I
also learned how to create wx resource files with the stock resource editor
and connect the controls to code. And using a free text editor (pspad) I was
MORE PRODUCTIVE than with the super-duper point and click visual Delphi.
Ok, I got the small system done very quickly, and dumped my problematic
delphi version of the big system, and re-worked it up with my thrown
together, totally free Python package, and I swear, had it finished before I
would have if I had stayed with the Delphi version.
Ok, time goes by, the big system continues to get improved etc... now all of
a sudden, the smaller system needs to grow big time, as it has morphed and
they need all these new things.
THE DILEMMA
Ok, I LOVE python, so that is not the issue, but, I am getting very worried
about it''s growth. I recently re-visted the web looking at alot of projects
I assumed would be up and running by now from over a year ago, such as Boa
Constructor, Iron Python etc... it seems all these projects get started, but
never finished.
Also, more and more I need *complete* control of ms sql from my apps, which
is simply not available from the adodbapi module I got off the internet...
also, ms sql 2005 is getting ready to come out... what if the guy that wrote
adodbapi.py does not feel like upgrading it so it even works with MS SQL
SERVER 2005? Yeesh... you get the picture...
So, wondering if anyone else is having these concerns or not, and if not,
why etc... Any input appreciated.
Python lover, but worried,
diego
推荐答案
使用点网的行车
语言？跨平台不是问题，但与MsSql Server（当前和未来版本）的完全控制/兼容性
肯定是。
快速历史
10多年前开始使用FoxPro，像Fox一样升级，是一个很好的
系统但是从来没有真正喜欢它因为很多因素我不会进入现在。
Delphi中有很多工作，一旦第5版出来......真的非常喜欢
一段时间。开始使用MS SQL服务器作为数据库。
如果要重新编写一个基于dos的旧数据库系统，可以使用很多
它在Delphi 7中，但真的开始出现Delphi的问题，甚至很多都很棒。
当我正在研究写道，有另一个较小的系统来处理，所以
我将不得不同时做两个......我开始四处寻找另一个
语言有了Delphi的问题，很长很短的故事，我用Python迷住了，并且使用它，用wxWindows编写界面，
和adodbapi.py进行通信ms sql server，我做了另一个较小的
系统。
令我惊讶的是，在很短的时间内我写了一个包装类
模拟使用Delphi ado记录集对象，围绕非常好的
（但有些限制）adodbapi.py模块。对于Windows用户界面，我还了解了如何使用股票资源编辑器创建wx资源文件
并将控件连接到代码。并且使用自由文本编辑器（pspad）我比使用超级duper点和视觉Delphi更有生产力。
好的，我得到了小系统完成得非常快，抛弃了我有问题的大系统的delphi版本的delphi版本，并将我的抛出
重新组合起来，完全免费的Python包，以及我发誓，如果我在Delphi版本之前就已经完成了，那么它就会结束。
好的，时间流逝，大系统继续得到改善等等......现在所有人都突然间，较小的系统需要增长很长时间，因为它已经变形了，并且需要所有这些新东西。
他们需要所有这些新东西。 />
DILEMMA
好的，我喜欢python，所以这不是问题，但是，我非常担心
关于它的增长。我最近重新访问了网络，看了很多项目
我认为现在已经开始运行一年多了，比如Boa
构造函数，Iron Python等...似乎所有这些项目都已开始，但是
从未完成。
此外，我需要越来越多*完全*控制ms sql从我的应用程序，
根本无法从adodbapi模块下载我从互联网上...
也，ms sql 2005正准备出来..如果那个写了
adodbapi.py的人不喜欢升级它，那么它甚至适用于MS SQL
SERVER 2005？ Yeesh ......你明白了......
所以，想知道是否有其他人有这些顾虑，如果没有，
为什么等等...任何投入赞赏。
Python情人，但很担心，
diego
bandwagon using a dot net
language? Cross platform is NOT an issue, but COMPLETE control/compatability
with MsSql Server (current and future versions) certainly is.
Quick History
Started out 10+ yrs ago using FoxPro, upgrading as Fox did, was a good
system but never really loved it due to many factors I won''t get into now.
Did alot of work in Delp once version 5 came out... really loved it for
awhile. Began using MS SQL server as database.
Had a HUGE re-write of an old dos-based database system to do, did alot of
work on it in Delphi 7, but really began to have issues with Delp even
tho alot of it is fantastic.
As I was working on the re-write, had another smaller system to work up, so
I was going to have to do both at once... I began to look around for another
language as was having issues with Delp very long story short, I became
enthralled with Python, and using it, with wxWindows to write the interface,
and adodbapi.py to communicate with ms sql server, I did the other smaller
system.
To my big surprise, within a short time where I wrote a wrapper class that
emulated working with the Delphi ado record set object, around the very nice
(but somewhat limited) adodbapi.py module. For the windows user interface, I
also learned how to create wx resource files with the stock resource editor
and connect the controls to code. And using a free text editor (pspad) I was
MORE PRODUCTIVE than with the super-duper point and click visual Delphi.
Ok, I got the small system done very quickly, and dumped my problematic
delphi version of the big system, and re-worked it up with my thrown
together, totally free Python package, and I swear, had it finished before I
would have if I had stayed with the Delphi version.
Ok, time goes by, the big system continues to get improved etc... now all of
a sudden, the smaller system needs to grow big time, as it has morphed and
they need all these new things.
THE DILEMMA
Ok, I LOVE python, so that is not the issue, but, I am getting very worried
about it''s growth. I recently re-visted the web looking at alot of projects
I assumed would be up and running by now from over a year ago, such as Boa
Constructor, Iron Python etc... it seems all these projects get started, but
never finished.
Also, more and more I need *complete* control of ms sql from my apps, which
is simply not available from the adodbapi module I got off the internet...
also, ms sql 2005 is getting ready to come out... what if the guy that wrote
adodbapi.py does not feel like upgrading it so it even works with MS SQL
SERVER 2005? Yeesh... you get the picture...
So, wondering if anyone else is having these concerns or not, and if not,
why etc... Any input appreciated.
Python lover, but worried,
diego
spiffo写道：
好的，我喜欢python，所以这不是问题，但是，我非常担心它的增长。我最近重新访问了网络，看了很多项目
我认为现在已经开始运行一年多了，比如Boa
Constructor，Iron Python等......似乎所有这些项目开始了，但是从未完成。
此外，越来越多我需要*完全*控制我的应用程序的ms sql，
根本无法从adodbapi获得模块我下了网...
另外，ms sql 2005正准备出来......如果那个写了
adodbapi.py的人不喜欢升级它甚至可以工作用MS SQL
SERVER 2005？ Yeesh ......你得到了图片......
Ok, I LOVE python, so that is not the issue, but, I am getting very worried
about it''s growth. I recently re-visted the web looking at alot of projects
I assumed would be up and running by now from over a year ago, such as Boa
Constructor, Iron Python etc... it seems all these projects get started, but
never finished.
Also, more and more I need *complete* control of ms sql from my apps, which
is simply not available from the adodbapi module I got off the internet...
also, ms sql 2005 is getting ready to come out... what if the guy that wrote
adodbapi.py does not feel like upgrading it so it even works with MS SQL
SERVER 2005? Yeesh... you get the picture...
如果一切都围绕着一个微软产品（ms sql 2005，
，那就是甚至还没有发布，你可能会更多地使用其他微软产品。这是供应商锁定的。您可以尝试使用
VS.NET 2005，看看C＃或VB.NET和ADO.NET api是否适用于
你： http://lab.msdn.microsoft.com/vs2005/
Of当然，加上ms sql 2005最终将花费大量的金钱。加上它们都不是跨平台的，但是你已经说过你这么做了。不需要那么多。
有免费的.NET替代品，比如Mono，Sharpdevelop，嘘（
http://boo.codehaus.org/ ）和nemerle ，但他们还没有赶上
..NET 2的东西。再说一遍，它还没有被发布，并且还有它们的测试版本仍然存在错误。
所以如果python库我不会感到惊讶无法处理ms sql
2005年特定的东西。
所以，如果你现在需要一个简短的答案，我会说去使用vs.net 2005，但如果
你可以等待一段时间，免费的python和.net替代品将会b / b
赶上来。
If everything revolves tightly around a microsoft product (ms sql 2005,
which isn''t even released yet), you probably are boxed in more towards
other microsoft products. That''s vendor lock-in for you. You might try
VS.NET 2005 and see if C# or VB.NET and the ADO.NET api work well for
you: http://lab.msdn.microsoft.com/vs2005/
Of course that plus ms sql 2005 will end up costing a great deal of
money. Plus none of it is cross-platform, but you already said you do
not need that.
There are free .NET alternatives like Mono, Sharpdevelop, boo (
http://boo.codehaus.org/ ) and nemerle, but they are not caught up with
..NET 2 stuff yet. Again, it hasn''t even been released yet, and there
are still bugs in their beta versions.
So it wouldn''t surprise me if the python libraries can''t handle ms sql
2005-specific stuff yet either.
So, if you need a short answer now, I''d say go with vs.net 2005, but if
you can afford to wait a while, free python and .net alternatives will
catch up.
也许用Python而不是C＃节省时间，或者你可以帮助改善adodbapi.py，确保支持下一个
版本的MS SQLServer，虽然这可能对
短期内没什么帮助。只是一个想法。
此外，还要知道 http://www.object-craft.com.au/projects/mssql/
我不知道它，但它可能证明对你。
Perhaps with the time saved by using Python instead of C# or some such,
you could help to improve adodbapi.py, ensuring support for the next
version of MS SQLServer, although that might be of little help in the
short term. Just a thought.
Also, have a gander at http://www.object-craft.com.au/projects/mssql/
I have no knowledge of it, but it may prove useful to you.
这篇关于新项目即将推出......继续使用Python，或者使用点网络语言？请你的想法！的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
