Lorefnon BTW knex maintainer is working on a graphql server framework that is looking interesting: https://github.com/graphql-nexus/nexus

so you're using just typescript with a query builder? Or just a db driver making your SQL queries manually with string templates?

At Looop.co we're using decapi on top of objection.js database models. Our DB is Postgre. Sure we could have used Prisma instead, but objection.js allows us to drop down to war SQL queries whenever we feel like it. That's a feature we'd definitely miss if we were to use Prisma/Hasura or some similar GQL API framework. Our biggest pain-point is the client side. We use apollo-client, but we have multiple schemas and we haven't yet figured out a way to generate our types from our schemas. It should be easy with a single schema, but we have 3, so for now we're just writing the FE interfaces for our GQL queries by hand.

no platform with billions of accounts can be built using just a single language. Go is great to write performant microservices on backend but if you want to compete on client side you should have your FE single page app server side rendered so using node.js to do that makes quite a lot of sense.

I use mobx. I've used redux in the past on 2 medium sized applications, but it never felt right. Javascript as a language doesn't have native support for immutability. If it had, redux might be more enjoyable, but since JS is what it is, observable pattern that mobx has makes way more sense than redux's.

How do you feel about ES6 proxies? Currently MobX uses getters/setters, but proxies could provide cleaner way of intercepting changes. Do you think in distant future MobX could in some major version start using proxies instead of getters/setters?

jspm does offer what you suggest-cloning directly from github. All one has to do is specify a dependency as github url instead of npm name. I am not sure how much that would help-github/gitlab are private bodies as well.

No because HTML and JS should not be your primary concerns in a frontend app. How do you split your app into a set of simple and reusable components-that should be your primary concern.