unknown_error

How would cryptocurrency free us from financial tyranny? At some scale finance becomes a state affair, and regulated by law backed by a monopoly on violence. Or, otherwise, you end up with crypto-warlords with private military companies. In neither sense would the average user be meaningfully "free"; it seems like you're replacing democratic checks-and-balances with harder-to-regulate digital capital, which is "freedom" only to the super-rich.

It's like somebody at the bottom of the Ponzi scheme defending it to death because someday, maybe, just maybe, he'll rise to the top...

Hmm, so in a way, it's kinda like a CDN for a database?

Is this something that will eventually get worked into Dialogflow?

In short: the vendor (Cloudflare) handles it, not you. Cloudflare has to quickly disseminate a lot of things to their data centers all the time (new files, routing rules, cache invalidations, etc.) and Durable Objects piggybacks on that same infrastructure.

From the client's point of view, all the network I/O is to a "centralized" server and not peer-to-peer, except in this case the "centralized" endpoint is actually a cluster of data centers that all talk to each other behind the scenes.

Client --> nearest Cloudflare node --> all the other nodes via their phat pipes, not yours

Edit: their global stateful serverless chatroom demo more clearly demonstrates how it works: https://github.com/cloudflare/workers-chat-demo

Can someone please explain how Vitess works, in plain English? How does it magically make MySQL scale?

And then what does PlanetScale add on top of Vitess hosted anywhere else?

Sorry, the linked blog post is both very abstract and assumes a high level of preexisting knowledge about database scaling.

There is still value in proprietary solutions that offer significant time/money savings vs open source. Not all of us have infinite resources to develop and maintain every solution in-house, whether that's an auto-scaling database or email or Google Docs or whatever.

For small/medium businesses, sometimes it's better just to let the experts do their thing and build on top of it...

I don't know that it's "demanding" as much as "tedious"... I feel like our entire field is built as a mountain of hacks upon hacks. How the heck did Javascript become the dominant programming language of worldwide communications?! The ecosystem is so fragile and unstable (https://hackernoon.com/how-it-feels-to-learn-javascript-in-2...) that it seems like most of web dev is keeping up with fashion changes rather than doing anything truly good for the user.

Windows Forms supported responsive layouts decades ago, and Visual Studio was a beautiful system to work in... now we have forty dialects of Javascript and twenty thousand CSS mutations served by like four browsers that share mostly the same renderer but still aren't compatible, overseen by standards groups that compete with each other to actually be the standards... sigh... it's like our main output is job security, producing new features to fix the new features from last week, like a ouroboros forever trapped in the matrix.

</rant>

I just really appreciate people who can code a clean, elegant app, because I can't remember the last time I saw one in the web world!

It works well! I remember being pleasantly surprised by this feature when I was searching for an unrelated document last time I logged in, and it found a bunch of images. I was like, wait, how did it know that...? It's a cool stealth feature.

Any chance Dropbox might want to add more DAMS-like features in the future, so that Dropbox can be used as a central image repository not just for photo originals but public websites, etc.? Kinda like Imgix or Cloudinary? I know our org already uses Dropbox to store asset originals, and it would be lovely to be able to hook in to a powerful API to serve it at different responsive sizes, formats, cropping, etc.

Forgot to say: If the computing resources don't cost you that much, consider making higher business/enterprise plans where you sell an SLA and/or support contract and/or custom feature development/integrations, etc. rather than making it usage-based.

TLDR, IMHO: Get rid of the Small plan, make the Sandbox tier a much more generous free tier (1k/10k with logo), and charge more for the bigger plans. "First one is always free" kinda thing, so that devs can use your service for small projects (that don't cost you much) but then upsell it for broader enterprise-wide adoption on bigger projects.

As a dev, I have the opposite opinion: The low-end pricing is a barrier to adoption. $9/mo isn't much, but it's the difference between "Oh cool, I can immediately use this in some of our side projects!" and "Oh, I have to request budget approval for this, explain what it is to superiors who might not be in the IT dept, answer questions about why we don't do just build it ourselves, answer questions about vendor support and lock-in, etc."

It would cost more time for me to jump through all those hoops than to just use a standard CSV parsing library -- even though the workflow is vastly inferior -- because it's much less bureaucratic.

Other services often provide a more generous free tier so that devs (the first ones to try something, often) can use it in a real-world project, fall in love with it, and then sell the paid version (which could be much more than $99) to their superiors only when the prototypes have proven valuable enough to make a solid sales pitch.

I'm not a business consultant by any stretch, just letting you know that as a dev, I'd probably never bother using this because of the bureaucratic headaches involved with your pricing structure. Just my 2c.

Wow, this is incredibly impressive!

As a web dev, I feel a moment of satisfaction when I manage to make a heading look right on both desktop and mobile. Lol, what you've done is several orders of magnitude more difficult... I could spend a lifetime coding and not even know how to start drawing the first pixel. Kudos!!