Show HN: ClarifyJs – Overcoming Limits of JavaScript Method Chaining
github.com
github.com
Maybe it is just a too simple example to get a point across, but I would want to see an example where this would not work.
That said, I get uneasy when reading code like the example
send('hello everyone!').to('friends').except('john');
since it doesn't follow my mental model of how programs execute. It's shorter than the builder pattern, but, at least to me, less understandable because there's more magic going on.I guess otherwise it would need to be something like send('hello everyone').to('friends', 'John'); but now you don't understand what 'John' does unless you read the code - which,I know, realistically people don't always make their methods match the names so you don't really know that except('John') does what you might assume until you read it as well.
But in a theoretical world that was as we would like it to be you could reason from the method name to what the method actually does.
> await msg('hello everyone').to( list).except('John')
Streams, events, etc have all solved this problem without repurposing existing syntax to “fix” a round peg by making it square.
Clever though.
How is this clearer than normal method calling, when you have to look for a priority number in the config to know which method executes before the other one?
Sorry but I think this is a really bad idea...
I think DSLs are, as their name says, domain specific. I do not think there's a one size fits all solution.
The places where this comes in handy are already prime candidates for bug hiding locations. Adding this in might remove some of those, but if the cost is that debugging what remains is significantly more difficult, then is it really worth it?