Comment

Comment by paulca

Given that I really don't have any practical experience using whenever.js (it's literally days old) my "argument", is that jQuery tends to be very syntax heavy.

eg. jQuery('a#click-me').click(function(){ $(this).text('Clicked!') })

... there's a lot of cognitive work going on here. Not only am I parsing javascript, as a coder, I'm parsing the CSS of the selector, and creating a mental model of the anonymous function. It's not to say that this is necessarily a bad thing, just that there's a lot of extra syntax to handle.

whenever("Click Me!").is('clicked').then('change it to "clicked"')

...reads without all of the extra syntax, but it still remains valid javascript.

> you'd have to look at three different places to understand what the code is _actually_ doing

This is a fair point, but I would argue that for most code you read, there's typically nowhere to go to find out the _intent_, which for me is really the most important thing. I think it's fascinating to be able to have "executable intent" ...

... but since I don't really have any real world experience using this, I can't really back up my arguments with any real data ... just the motivations I had to write this!

parent paulca 15 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton