ms123

only tested on chrome...

I did pretty much that. However my version features a COW that reads tweets; a platypus that displays user's info; a snail that shows images and a turtle that plots the tweet on a map.

http://cowpilot.herokuapp.com/cowspeak?search_term=coffee+tw...

Congratulation, it looks really awesome.

I'm trying to find the video, but haven't been successful so far.

I've tried to google for "Jerktoaster", but there's only 5 links, non of them relevent.

I love that executable markdown style. I created a project some time ago that does just that. For the records, here it is: https://github.com/mikaa123/lilp

Hypermedia APIs are an approach to solve this problem. It essentially does what you did, and add some other benefits like de-coupling URIs.

I think it's a really interesting question.

My candid answer would be that many factors popularize a language; and being a "great language" isn't necessarily one of them.

Perfect. What is there more to say, really? You made the world a little better today.

Thanks for pointing out the article

Your point is valid. My stand is that recursion forces the programmer to think about the edge cases first, which would make a bug less likely to appear.

Thanks for the award.

Yup, there's only one implementation. But doesn't in change? What will the compiled code be like in 3 years from now?

The compiled code's prupose is to be optimised, not consistent. This is my point.

By restricting yourself to think Javascript when you're coding in CoffeeScript, you're producing a code that sucks in JS and in CS.

Am I the only one to completely disagree with the author?

It's important not to mix everything. CoffeeScript is a language. There just happen to have an implementation for it.

This invalidates the "debug" workflow problem. Let me restate the CS debugging workflow:

    Start discovering the problem in the code I wrote.
    Fix it in the CS
    Problem fixed, move on, otherwise start over.

A computer language is by definition a mean to express unambiguous statements. So does CS. So does the other languages. The resulting program will do exactly what your code asked to.

Do we check compiled code when we code in C? Do we look at the Bytecode when we write Java?

The fact that CS compiles to JS is an "implementation detail". That's the CS compiler's job. If you don't trust it, don't use it.

It's worth mentioning 'css3buttons' project which does the same thing in a really elegent way.

https://github.com/michenriksen/css3buttons

Fun, little, and mind-rewarding. That's just how hacks should be. I found what I'll be doing this afternoon.

Interesting experiment. It goes to show the importance of wording and conciseness in titles.

my point is that programs can be pipelined, not applications.

To me the difference between "old-web" and "new-web" is a lot like the one between "program" and "application.

Old-web was just text and markup. A lot like the output of command line programs that could then be used by other programs to perform what we want.

New-web is about application. Programs made for the end-user. Apps aren't thought to be pipelined with other apps. Thus for a web-app, the browser is often designed to be the only supported plateform. Thus the extensive use of JS.