Students who are learning to build things on these platforms shouldn't lose their early work.

We're Charlie Brown running towards the football repeatedly. We need to learn a lesson here. "We're the good platform devs" branding doesn't mean a company will do the kind thing by their true believer users (post-acquisition, post-cash-flow-belt-tightening, post-IPO, etc)

There ought to be a platform on which new coders can build a free simple web app in a playground, and know it will be accessible in 20 years. If a company wants to use "free easy backends" as bait for capturing growing companies' future costs, devs should hold them to long-term persistence and at least an off-platform future migration path. See also Parse, Geocities, etc

Use some % of the money and put it in to an OSS migration path or a fund to pay their own future AWS bills, c'mon.

Comments URL: https://news.ycombinator.com/item?id=33452824

Points: 3

# Comments: 0

From the title "Show HN: Open-source Firebase Alternative? It's here (github.com/appwrite)" was expecting the entirety of Appwrite to be a new project shown here for the first time. Could the title be changed to reflect what's new? Perhaps the title of the GitHub Issue being linked: "Announcing Appwrite 0.14 with 11 Cloud Function Runtimes!"

Good example of "all or nothing thinking" here. "Toiling every day on the backs of humans for our every need" OR "Frighteningly advanced automation" — reality is higher fidelity than that.

We're already SO far towards the latter scenario (washing our clothes magically with the press of a button), painting it as a dichotomy only serves to highlight how out of touch with reality the immutable scarcity worldview is.

> (The streamers did not provide their legal names to The New York Times. In years past, women gamers who have spoken out against the industry using their legal names have been subjected to further harassment, hacking and doxxing.)

This Seattle school figured out measures for handling lunch and remote schooling availability, at least: https://www.nytimes.com/interactive/2020/03/10/us/covid-19-s...

Especially in these early days, dispersal of dense populations can easily mean saving many lives. We need to flatten the curve so spread rate does not exceed hospital bed availability.

Nobody's saying we won't all be extremely inconvenienced by this, but slowing the spread will mean that inconvenience does not include many avoidable deaths. And now is the time to do everything we can. In weeks, once we feel the effects more closely, it is too late to make an impact.

This comic puts it well, the goal is to flatten the curve: https://twitter.com/SiouxsieW/status/1236721200291655680

In your scenarios:

1. "keep it contained at the university" would probably look like: thousands of students, staff, businesses get the coronavirus rapidly over the course of the next two months (possibly overwhelming local hospitals), proceed to spread across the other densely populated area universities, Boston, NY, Spring Break, summer internships, travel everywhere happens post-mass-infection phase. Many deaths attributable to the campus being open likely.

2. Single person brings it to where they're from - same effects of a single sick person traveling we're seeing in the US every day (including what brought it to Boston). Unless they're going to another densely populated university or conference, which if more measures like this take place they should not be, the impact will be far less.

At this point they aren't aware of any students who have it, so a likely scenario if nothing is done is that the student population GETS it from the Biogen outbreak in Cambridge, AND spreads it at a much higher rate across the local area, country, world.