61–70 of 95 posts
If you code while working for another company dont they own that IP? Unless specifically stated on your employment contract? Just curious! Thanks
I spent some time with the founders and they are really great. Without parse and google owning fire base they way has been paved for a new IAAS/PAAS. I hope Michael and Vince can lead the way.
Please take this constructively, but I can't help but think that the prevalence of GraphQL in your messaging is a huge distraction. It seems like the real value in Scaphold is letting people build applications faster, with less effort. In fact, in your post's description of the problem you're solving, you don't mention GraphQL at all (until you start talking about solutions). Right now, the (gorgeous) site feels similar to if Shopify had launched with messaging focused on its use of Rails on the backend.
It feels like you could also be targeting the type of less-sophisticated business programmers for whom VBA is often a weapon of choice. However, when I read your site, the fact that I don't use GraphQL makes me want to move on.
Anyhow, best wishes again on your launch!
The new website looks pretty cool but I wasn’t blown away by the product. The API feels very weird when actually building an app and unfortunately most integrations didn’t work for me. We’ve tried all available GraphQL BaaS and now use Graphcool which doesn’t have all the features Scaphold provides but the ones they have are very stable and mature. Also their API seemed by far the best one we’ve tried yet (e.g. they…
To your point about the extra endpoint, I know they have different ones for simple, Relay, files, and from what you're saying not Apollo Client. To me personally, it seems a bit counterintuitive that they offer so many different endpoints when one of the premises of GraphQL was to have a single endpoint that was decoupled from the client. Open to your thoughts here to see how we can improve your experience as a developer from the client perspective!
Congratulations on your launch! Please take this constructively, but I can't help but think that the prevalence of GraphQL in your messaging is a huge distraction. It seems like the real value in Scaphold is letting people build applications faster, with less effort. In fact, in your post's description of the problem you're solving, you don't mention GraphQL at all (until you start talking about solutions). Right now…
Congratulations on your launch! Please take this constructively, but I can't help but think that the prevalence of GraphQL in your messaging is a huge distraction. It seems like the real value in Scaphold is letting people build applications faster, with less effort. In fact, in your post's description of the problem you're solving, you don't mention GraphQL at all (until you start talking about solutions). Right now…
I initially parsed the name as 'scaphoid', one of the carpal bones. I thought they were making a joke about reducing typing...turns out I just can't read properly.
My team and I have a medium sized dev shop from Southern California. We've been using Scaphold in production now for several months, and have been absolutely blown away by how much more efficient we've become. All projects in the pipeline will be using Scaphold going forward. Take my money.