4 ms·

Here's the motivation: https://github.com/solenya-group/solenya#motivation https://github.com/solenya-group/solenya#motivation

ricardobeat 7y ago
> the side-effects of complexity are costly code bases defended by programmers who's actual talent is politics Spot on. That describes a majority of mainstream libraries in JS today.
ng12 7y ago
That doesn't really mean anything to me. It keeps talking about "other frameworks do this" or "other frameworks focus on this" -- but all of the examples in the docs would be basically 1:1 rewrites into React or Vue.
- pickle-ts 7y ago
  Someone has actually just posted on github a request for Solenya to implement the RealWorld example app. I think that would be great idea, so people could directly compare Solenya with say React+Redux. Abstract reasoning is one thing, but it's always good to see side-by-side comparisons. Note the inclusion of a state management library for an apples-to-apples comparison, since Solenya has intrinsic state management. Also note that I'm firmly NOT in the "all you need is the V in MVC" camp. Dealing with state is one of the trickiest aspects of writing scalable code that I've sought to address. There's an excellent video that discusses state management in large applications here (in the context of Angular, but the principles apply generally): https://www.youtube.com/watch?v=eBLTz8QRg4Q https://www.youtube.com/watch?v=eBLTz8QRg4Q My goal has been to deal with these issues in a way that works for both small and big apps. Previously, I dreaded having to make the decision at the start of an app: "is this app complex enough that I have to pay the tax of using a state manager?", where there's two very different ways of writing the application and I had to cross my fingers whether I'd made the right choice. The solution to this dilemma with Solenya, has been to make the tax of having state management so low that it's always on, whether the application is big or small.

ricardobeat 7y ago

> the side-effects of complexity are costly code bases defended by programmers who's actual talent is politics Spot on. That describes a majority of mainstream libraries in JS today.

ng12 7y ago

That doesn't really mean anything to me. It keeps talking about "other frameworks do this" or "other frameworks focus on this" -- but all of the examples in the docs would be basically 1:1 rewrites into React or Vue.

pickle-ts 7y ago
Someone has actually just posted on github a request for Solenya to implement the RealWorld example app. I think that would be great idea, so people could directly compare Solenya with say React+Redux. Abstract reasoning is one thing, but it's always good to see side-by-side comparisons. Note the inclusion of a state management library for an apples-to-apples comparison, since Solenya has intrinsic state management. Also note that I'm firmly NOT in the "all you need is the V in MVC" camp. Dealing with state is one of the trickiest aspects of writing scalable code that I've sought to address. There's an excellent video that discusses state management in large applications here (in the context of Angular, but the principles apply generally): https://www.youtube.com/watch?v=eBLTz8QRg4Q https://www.youtube.com/watch?v=eBLTz8QRg4Q My goal has been to deal with these issues in a way that works for both small and big apps. Previously, I dreaded having to make the decision at the start of an app: "is this app complex enough that I have to pay the tax of using a state manager?", where there's two very different ways of writing the application and I had to cross my fingers whether I'd made the right choice. The solution to this dilemma with Solenya, has been to make the tax of having state management so low that it's always on, whether the application is big or small.