11 ms·
Interesting in and of itself, and yes I'm familiar with the design pattern, but with so much code to accomplish the simplest of things, Spolsky's "architecture
by V-2 9y ago
Interesting in and of itself, and yes I'm familiar with the design pattern, but with so much code to accomplish the simplest of things, Spolsky's "architecture astronauts"* spring to my mind straight away. Perhaps it's JavaScript that's not the best choice of a language here?
____
* https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/ https://www.joelonsoftware.com/2001/04/21/dont-let-architect...
- stephen 9y agoYes, agreed, using chained prototypes to accomplish nested state charts is not something I'd want to inherit as a maintainer. It's cute, in a "look at how I can make the language do this"/novelty way, but I don't think it's JavaScript's fault per se, as this seems similar to Java architects solving problems with "just another factory", "just another annotation", "just another bytecode generator", etc.
- deckard1 9y agoThat's a great article that always deserves a read once or twice a year. > Your typical architecture astronaut will take a fact like “Napster is a peer-to-peer service for downloading music” and ignore everything but the architecture, thinking it’s interesting because it’s peer to peer, completely missing the point that it’s interesting because you can type the name of a song and listen to it right away. This sentence so succinctly summarizes the current "blockchain" craze that it's hard to believe he wrote it in 2001.