3 ms·
I browsed through the README and was somewhere between laughing and crying by the end - it's like a case-study for all the baffling complexity that's been added
by bshimmin 11y ago
I browsed through the README and was somewhere between laughing and crying by the end - it's like a case-study for all the baffling complexity that's been added to front-end development over the last two or three years.
(I expect this comment won't be too popular, but I'm happy to take the flak.)
- harel 11y agoIts the single page app tax. To be honest I find it infinitely more complex than a standard old school front end but I'm also happy to pay the tax and reap the benefits in the end. Not to mention it makes things more interesting from a pure dev fun point of view.
- grumblestumble 11y ago"Now, we should define an increment action." <TYPING INTENSIFIES>. 40 lines of code later, we can increment a variable.
- yrashk 11y agoThis project is written as a literate program and most important parts of the code are exposed. What you see there is how it's actually implemented. The action is defined like this: const IncrementCounter = createAction(domain, 'IncrementCounter',t.maybe(incrementParameter)) (A oneliner)
- yrashk 11y agoto address this confusion, I've added an "excerpt from the library" label to show which parts of the code are just parts of the actual stack.