Re:Fluent Interfaces Are Bad for Maintainability
by erpellan on Tuesday March 20, 2018 @09:59AM
(#16628571)
Kotlin solves the problem elegantly with the 'apply' and 'run' extension functions.
[ Parent
| on HN ]
Re:Fluent Interfaces Are Bad for Maintainability
by m00g00 on Tuesday March 20, 2018 @10:19AM
(#16628742)
Which is awfully similar to JavaScript's much maligned 'with' statement.
Never understood the FUD and 'considered harmful' screeds against it. Yes I'm aware of the performance/optimization concerns, but honestly, the whole javascript language is a massive performance/optimization concern and we've managed pretty well.
Simple things like changing style properties on DOM elements:
with(element.style) {
display = "block";
marginLeft = "5px";
background = "green";
}
And of course with 'with', everything is a fluid interface, and with the flexibility of being able to enter code between the function calls.
Re:Fluent Interfaces Are Bad for Maintainability
by hungerstrike on Tuesday March 20, 2018 @10:13AM
(#16628695)
Kotlins `apply` seems exactly like the much maligned `with` statement from JavaScript, which has been deprecated.
Why is it elegant here, but deprecated there?