221–230 of 397 posts
Earlier quoted context omitted.
I like TypeScript and would like to write backends in TypeScript. I'm coming around on Elixir. I never want to write Go that interacts with a database again. Rust seems complicated. I don't think I'm smart or committed enough to get anywhere with rust.
> I never want to write Go that interacts with a database again. Why? I’ve been using sqlx and it seems fine.
The color changing on this page gives me a migraine: https://deno.com/deploy I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it.
> I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it. Slack: "Run on Slack" Netlify: "Netlify Edge Functions" They're both listed in the Showcase: https://deno.land/showcase
Serious question, how do investors plan on making a return on their investment? Where is the cash in this?
From the post: > For example, it is integrated with GitHub in such a way that on every push it will provision a new server running specifically that code, deployed to the edge, worldwide, and persisted permanently. Want to access the code your app was running a month ago at commit f7c5e19? It will be served up instantly at a moment's notice. It costs you nothing to have that bit of JavaScript responding to requests i…
From the post: > For example, it is integrated with GitHub in such a way that on every push it will provision a new server running specifically that code, deployed to the edge, worldwide, and persisted permanently. Want to access the code your app was running a month ago at commit f7c5e19? It will be served up instantly at a moment's notice. It costs you nothing to have that bit of JavaScript responding to requests i…
I'd spawn a new DB for that instance too. It can still go a long way to give you a look at how your application worked in the past.
Let’s charitably say you can run your app with a 1GB cut down snapshot of production.
You’re going to do what, save a snapshot of the database for every commit? Every schema migration?
…and then provision that up in a running database server… which is notoriously not container friendly…
? It doesn’t sound very plausible to me.
Our database is ~1TB, and the app runs with maybe a 10GB cut down version of it, which is a pain in the ass to deal with, just for example, for local dev environments.
I agree with the parent post; it’s cute, but I can’t imagine historical per commit deployments being useful for me, honestly.
From the post: > For example, it is integrated with GitHub in such a way that on every push it will provision a new server running specifically that code, deployed to the edge, worldwide, and persisted permanently. Want to access the code your app was running a month ago at commit f7c5e19? It will be served up instantly at a moment's notice. It costs you nothing to have that bit of JavaScript responding to requests i…
Earlier quoted context omitted.
Yeah I love making prospective customers feel pain too. /s
The world doesn’t exist to cater to your weird specific thing that gives you a headache
We have web accessibility standards and companies get sued for not following them.
heh, I knew for sure Deno would be successful from the first moment it appeared on HN and people here were critical of it. My rule of: The more HN criticizes it, the more likely it succeeded, still rings true.
So crypto is going to be a giant success?