Jeremy Bush

> E.g. Why do my presenters inherit from View? There's a very obvious muddling of responsibilities there, the View both renders and presents the data. Yeah, that's one nice thing...

btw, I made repos for my experiment application: https://github.com/zombor/Raptor-Demo-Delivery https://github.com/zombor/Raptor-Demo-App Delivery is the raptor app, and only includes delivery mechanism files. App is the business logic files of the application....

Sometime since I posted this, I wrote a standalone mustache renderer. It lets you use PORO's as your view classes: https://gist.github.com/zombor/4727040 This eliminates the crappy need to extend and bind...

Yep, here you go. ```json > jest --debug jest version = 19.0.2 test framework = jasmine2 config = { "automock": false, "bail": false, "browser": false, "cacheDirectory": "/tmp/jest", "clearMocks": false, "coveragePathIgnorePatterns":...

Cool, thanks for the heads up. With vue-octicon, there's some webpack config needed, I wonder if it's a similar thing with this: https://github.com/Justineo/vue-octicon#es-modules-with-npm--vue-loader-recommended

I've ended up just moving away from vue-octicon, so unfortunately I don't have a good answer.

I currently have two use cases: 1. An apache file server. A client basically transfers documents into their home directory and an apache docker container mounts that as it's document...

FWIW, I just ended up creating an array with the objects in it by hand. In thinking about it more, this feature doesn't make a whole lot of sense to...

If your methods have specific object signatures, and you need to iterate an actual object, my way wouldn't work.

Why bother with this? I don't see the advantage vs. the extra code required to support it.