Re:Next Up in the Obvious Category...
on
Design Patterns
·
· Score: 1
I`ve never heard of it either. I`m not sure where people get off being smart arse and `Oh, i heard about it years ago`. So what? Someone told you sooner, that's all. Get over it.
There's certainly no need for anyone to be a smart arse about it. And the book will probably continue for a while to be one of those that is mentioned far more often than it is read. But for the very reason of the book's numerous citations, I'd suggest to a professional programmer that they might want to consider whether they are reading widely enough if they managed to miss these references. I'd recommend Software Development magazine (sdmagazine.com) and Dr Dobbs' Journal (ddj.com) as good places to visit now and again to keep abreast of what's happening in the software-development world generally.
So they admit it but they don't admit it?... I'm not sure how you can accuse a company of not admitting a mistake when your proof of that mistake is the company's admission of it
Because their admission is still not completely truthful and tries to represent the situation better than it is.
A successful project with analogous goals is anydbm. You can make generic operations on databases, and it will work on mysql and postgresql.
anydbm is a generic interface to variants of the DBM database, not relational databases like MySQL and Postgres. For relational databases the generic interface is DB-API.
When Zope Corporation hired the PythonLabs team, they heartily agreed to turn over the copyright of Python to Guido van Rossum
This seems to imply that Zope Corporation (formerly Digital Creations) owned copyright in Python. Though various bodies have owned copyright in Python at different times, Zope Corporation is not one of them. Instead when CNRI were discussing transferring their copyright, ZC agreed that it should be to Guido personally and ultimately to the PSF, rather than to ZC themselves as Guido's new employer. At least that's my understanding.
I'm not porting it to python unless someone wants to port Template Toolkit to python also
See http://htmltmpl.sourceforge.net/
Hamish Lawson
It doesn't add enough perceived added value
on
Why not Ruby?
·
· Score: 2
I think the answer to the poster's question as to why Ruby hasn't gained as much support as other languages is that it doesn't add enough perceived value to persuade people to move away from they currently use. After many years of using Perl, I switched to Python because I was looking for something that I reckoned was more object-oriented, cleaner and more explicable - I imagine similar reasons would be given by others who made the same move. But before making the move I had to weigh up the cost of switching. I've since had a look at Ruby, and though I'm prepared to concede that it may, perhaps, be a better language technically, it doesn't offer me enough perceived added value to warrant the cost of switching.
Why not use both Ruby and Python/whatever? Though there is truth in the maxim "Use the appropriate language for the task", it's also true that there are many benefits from having a body of work in the same language. Leaving aside the time and effort to learn Ruby, for me to do a project in Ruby would mean ending up with some code that I probably couldn't use from my other projects. That's why I've characterised it as a switch.
When Guido said Python is used "much more across the board than Perl", I think he meant that it is applied to a wider range of problems, not necessarily that more people use Python than Perl (in the same way that there are a large number of COBOL programmers and applications out there, but within quite a narrow domain).
Especially OS/390 on which none of the other languages mentioned in this discussion will even run.
Python appears to be available for OS/390:
Because their admission is still not completely truthful and tries to represent the situation better than it is.
A successful project with analogous goals is anydbm. You can make generic operations on databases, and it will work on mysql and postgresql.
anydbm is a generic interface to variants of the DBM database, not relational databases like MySQL and Postgres. For relational databases the generic interface is DB-API.
Hamish Lawson
When Zope Corporation hired the PythonLabs team, they heartily agreed to turn over the copyright of Python to Guido van Rossum
This seems to imply that Zope Corporation (formerly Digital Creations) owned copyright in Python. Though various bodies have owned copyright in Python at different times, Zope Corporation is not one of them. Instead when CNRI were discussing transferring their copyright, ZC agreed that it should be to Guido personally and ultimately to the PSF, rather than to ZC themselves as Guido's new employer. At least that's my understanding.
Hamish Lawson
scrytch wrote:
I'm not porting it to python unless someone wants to port Template Toolkit to python also
See http://htmltmpl.sourceforge.net/
Hamish Lawson
I'm not porting it to python unless someone wants to port Template Toolkit to python also
See http://htmltmpl.sourceforge.net/
Hamish Lawson
I think the answer to the poster's question as to why Ruby hasn't gained as much support as other languages is that it doesn't add enough perceived value to persuade people to move away from they currently use. After many years of using Perl, I switched to Python because I was looking for something that I reckoned was more object-oriented, cleaner and more explicable - I imagine similar reasons would be given by others who made the same move. But before making the move I had to weigh up the cost of switching. I've since had a look at Ruby, and though I'm prepared to concede that it may, perhaps, be a better language technically, it doesn't offer me enough perceived added value to warrant the cost of switching.
Why not use both Ruby and Python/whatever? Though there is truth in the maxim "Use the appropriate language for the task", it's also true that there are many benefits from having a body of work in the same language. Leaving aside the time and effort to learn Ruby, for me to do a project in Ruby would mean ending up with some code that I probably couldn't use from my other projects. That's why I've characterised it as a switch.
When Guido said Python is used "much more across the board than Perl", I think he meant that it is applied to a wider range of problems, not necessarily that more people use Python than Perl (in the same way that there are a large number of COBOL programmers and applications out there, but within quite a narrow domain).