can you tell a bit more how deta compares to similar (?) services like firebase, netlify, vercel?
(don’t worry if there isn’t a great “usp” answer, just interested in learning more)
I’m personally quite excited about getting the journey from idea to something to tinker (and shareable) back down to how I remember it from a few years ago where I just live-edited files on a server. I tend to over-analyze all the various tech stack and deployment aspects too early :(
For hackathons I’m currently also using repl.it and glitch to get immediate results.
edit: kudos to getting this shipped/launching, can relate to how difficult it is to get an initial version out!
Hi — another co-creator here, thanks for the feedback.
With respect to your first question, I believe abdelhai answered it in another thread above.
We totally empathize with the experience of getting something to tinker and share rapidly up and running.
We actually started out our journey with our own cloud editor. It was essentially a worse repl.it or glitch but with a built in database and files. What we learned from our own talks with devs is that many of them really love their local development workflow and their own text editors. We decided or original approach was the wrong one for us but still want to provide the instant experience and rapid feedback that Glitch and repl.it do so well.
A couple USPs that might not be apparent in our marketing materials:
If you type 'deta watch' from the CLI, your locally saved changes will deploy in real time to your Micro(server). All you need to do is hit 'refresh' in the browser or make a new HTTP request.
We provide a real time 'Visor' which caches and logs incoming requests and responses. These can be replayed from within Deta against your latest code. Users have found this very useful for developing things like webhooks.
Comments
can you tell a bit more how deta compares to similar (?) services like firebase, netlify, vercel?
(don’t worry if there isn’t a great “usp” answer, just interested in learning more)
I’m personally quite excited about getting the journey from idea to something to tinker (and shareable) back down to how I remember it from a few years ago where I just live-edited files on a server. I tend to over-analyze all the various tech stack and deployment aspects too early :(
For hackathons I’m currently also using repl.it and glitch to get immediate results.
edit: kudos to getting this shipped/launching, can relate to how difficult it is to get an initial version out!
Hi — another co-creator here, thanks for the feedback.
With respect to your first question, I believe abdelhai answered it in another thread above.
We totally empathize with the experience of getting something to tinker and share rapidly up and running.
We actually started out our journey with our own cloud editor. It was essentially a worse repl.it or glitch but with a built in database and files. What we learned from our own talks with devs is that many of them really love their local development workflow and their own text editors. We decided or original approach was the wrong one for us but still want to provide the instant experience and rapid feedback that Glitch and repl.it do so well.
A couple USPs that might not be apparent in our marketing materials:
If you type 'deta watch' from the CLI, your locally saved changes will deploy in real time to your Micro(server). All you need to do is hit 'refresh' in the browser or make a new HTTP request.
We provide a real time 'Visor' which caches and logs incoming requests and responses. These can be replayed from within Deta against your latest code. Users have found this very useful for developing things like webhooks.
Having a database is a useful advantage over Vercel.