I'd like some opinions about where you think BuzzPerl should go. What are you looking for in BuzzPerl? What should it look like? Ease of use? Should it be a module? Is an abstraction/simplification of pattern/etc storage required? What routines would be useful?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-08-29
What I am looking for is to drop this BuzzPerl thing and start something like BuzzPython. There are so many reasons for this - the full support for COM interfaces is enough to convince anyone that Perl should not be used. Another one is the native support of OOP in Python. C'mon guys, please join the modern age :-) Drop that old ugly clunky antiquated language. Using a language like Python in Windows allow for Buzz to communicate with other COM interfaces. It alows for Buzz to work with Blender for example. The sky is the limit. And what do you have? Perl? Forget it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd like some opinions about where you think BuzzPerl should go. What are you looking for in BuzzPerl? What should it look like? Ease of use? Should it be a module? Is an abstraction/simplification of pattern/etc storage required? What routines would be useful?
What I am looking for is to drop this BuzzPerl thing and start something like BuzzPython. There are so many reasons for this - the full support for COM interfaces is enough to convince anyone that Perl should not be used. Another one is the native support of OOP in Python. C'mon guys, please join the modern age :-) Drop that old ugly clunky antiquated language. Using a language like Python in Windows allow for Buzz to communicate with other COM interfaces. It alows for Buzz to work with Blender for example. The sky is the limit. And what do you have? Perl? Forget it!