News for hackers. Stuff that matters.

A comment on Pseudosynchronous JavaScript. Parent comment

Re:Pseudosynchronous JavaScript by findjashua on Thursday June 25, 2015 @01:01PM (#9779288)
eventstreams are handy for handling a stream of events (user actions in UI, streaming API client), but when a request gets a single event as a response (ajax/http), async/await looks like a much simpler option (functions return the output, instead of taking a handler to process it). Thoughts?

PS: enjoyed your talk 'user is a function', looking forward to how cycle evolves.

[ Parent | on HN ]
Re:Pseudosynchronous JavaScript by staltz on Thursday June 25, 2015 @01:38PM (#9779535)
What is an event? Put differently: what cannot be an event in your application?
[ Parent | on HN ]
Re:Pseudosynchronous JavaScript by findjashua on Thursday June 25, 2015 @02:32PM (#9779983)
While events can be used anywhere in your applications, they're not the best option in my opinion. I still think functions should take an input and 'return' the output, not take a handler function to process it.
[ Parent | on HN ]