3 ms·
The very next post on this blog is all about ... drum roll ... a custom framework that the moot team built, after deciding to not use any frameworks. https://m
by mjackson 13y ago
The very next post on this blog is all about ... drum roll ... a custom framework that the moot team built, after deciding to not use any frameworks.
https://moot.it/blog/technology/riotjs-the-1kb-mvp-framework.html https://moot.it/blog/technology/riotjs-the-1kb-mvp-framework...
Sadly, this behavior is very common among those who have a hard time adopting existing libraries/frameworks. In the end, they almost always re-invent their own obscure wheel that does the same job.
- felxh 13y agoThe irony doesn't escape me, but for what it's worth, here is a previous HN discussion about their framework you mentioned: https://news.ycombinator.com/item?id=6653024 https://news.ycombinator.com/item?id=6653024 A complaint I remember was that "there isn't much to see here except jQuery"
- badman_ting 13y agoBoooooo.
- ataggart 13y agoI think it's important to distinguish frameworks from libraries. With libraries, your code is the caller; you can compose things as you like, including with your own code for cases not covered by the library. But with frameworks, your code tends to be the callee; you must conform to (and are thus limited by) the assumptions the calling code has baked-in by the framework authors. My sense is that the pain from this inverted directionality is what drives these bespoke frameworks.
- ntoshev 13y agoOf course. Not using any framework (external or built in-house) would mean that the team didn't find any useful abstractions that could be layered on the raw JavaScript. Very unlikely.
- evolve2k 13y agoObligatory XKCD http://xkcd.com/927/ http://xkcd.com/927/