HN Explorer

5 comments

[ 0.17 ms ] story [ 23.3 ms ] thread
[dead] TempleOSV2
C:\TAD\Text\QUIX.TXT

e, and the fairness of my face. And if thou wilt not relent or come to reason for me, do so for the sake of that poor knight thou hast beside thee; thy master I mean, whose soul I can this moment see, how he has it stuck in his throat not ten fingers from his lips, and only waiting for thy inflexible or yielding reply to make its escape by his mouth or go back again into his stomach."

Don Quixote on hearing this felt his throat, and turning to the duke he said, "By God, senor, Dulcinea says true,

----

Yield says TRUE? LOL

ilaksh
If Guido could carefully and objectively study ToffeeScript then he would see that it is much more readable than Python/Tornado.
p0b
So you're comparing a dialect that was written for CoffeScript which was written for the purpose of improving JavaScript's brevity and readability and was partially inspired by Python and took elements from Python to something that's supported natively in Python?

I suppose anything is possible with a meta-meta-meta language.

ntrepid8
One of the things I'm most excited about in Python is the new asyncio that Guido was talking about. I hoping that with an IOLoop in the standard library and built in Futures, that many of the synchronous network libraries available today will be able to present a synchronous mode and an asynchronous mode. The big strength of NodeJS is the async ecosystem, but Python could catch up quickly if asyncio really takes off.
ilaksh
Yes, and I am aware it was inspired by Python, that's obvious, and that's one of the biggest reasons I like CoffeeScript because of the nice somewhat Python-ish clean syntax. To me though CoffeeScript is even cleaner than Python. For example, you don't need colons in some places, and there are less underscores in some places. And with ToffeeScript smoothing out the async stuff, I think its really worth trying out for Python people.