I'm frustrated. I feel like the Next Big Thing™ is right in plain sight. The skill tree has been satisfied, the pieces are there, just not put together. And it will be painfully obvious in retrospect. BUT I CANT PINPOINT WHAT THE FUCK IT IS!
Agreed. I see a few hurdles. 1. JVM. I think this is a bad bet. The masses don't want to deploy it. 2. Needs to be DB agnostic? Would benefit from an ActiveRecord/knex/whatever layer. ....
-
-
3. AWS AppSync is almost this. But I have little faith AWS will build a good dev UX experience around it. Someone else needs to make `graphql new my-app` magic. Even if AWS is the backend.
-
Have you seen the new awsmobile CLI that we also released (week before reinvent) as part of the Amplify launch? https://github.com/aws/awsmobile-cli/blob/master/README.md …https://aws.amazon.com/blogs/mobile/announcing-aws-amplify-and-the-aws-mobile-cli/ …
-
Not bad. AWS is def improving in this area. But I think still a ways to go. Why don't ya'll just hire
@tjholowaychuk to build this stuff? Whatever he costs it will be worth it.
End of conversation
New conversation -
-
-
1. True. Ruby/node would be more compelling (to me) 2. I'm fine w/ Postgres (MySQL to a lesser degree). But, probably need to support lots of db's to take off, yeah.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.