... and then the author proceeds to presenting clunky, unreadable fluent syntax
That was a good joke for the afternoon.
... and then the author proceeds to presenting clunky, unreadable fluent syntax
That was a good joke for the afternoon.
Or are you suggesting that the majority of programmers struggle to read and understand fluent method chaining?
I don’t have a dog in this fight because this blog post is very novice oriented. I’m just genuinely confused why you think it’s unreadable or “clunky”. What is it about the fluent example that you find clunky?
These patterns are commonplace for many years now in many languages.
The intention was to show how declarative code can come from imperative with a 'true' one-liner.
i've worked with people in the past who refused to allow any actual LINQ in the codebase (use resharper to convert it to fluent!) even though it essentially became obfuscated.