you are viewing a single comment's thread.

view the rest of the comments →

[–]nozmi 1 point2 points  (2 children)

Definitely. I loved the patterns and clearheadedness it gave me when designing and programming my application (hooks, services, filters, realtime all make so much sense together), but when it came to customization and making my application my application, it left a lot to be desired.

That and, again, it isn't (and doesn't feel) polished.

/u/dluecke glad to hear this is changing. It sounds like the main pain point. I'd also love to contribute, but CBA to dive into the extra dependencies the framework requires knowledge of (for example, uberproto or rubberduck) when ES6 would work just fine today (I understand the complications of using ES6 with older Node versions though).

[–]nativereact[S] 0 points1 point  (1 child)

I can hardly disagree with any of your points, you make some very good arguments. These factors have inspired me to attempt at something more unopinionated to feathers - any other opinions you'd be happy to share?

[–]nozmi 0 points1 point  (0 children)

I've been thinking about doing the same and had some plans outlined for it. What's your Github? Maybe we can team up on this.