kopochameleon

Finding this comment interesting, parent comment didn't suggest any past association but it seemingly uses project reference as pivot point to do various outgroup counter signaling / neg bun?

Many are new students who don't think about the business landscape of the service they choose to build something on.

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

Have they committed to anything different than what Heroku had committed to?

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.

I don't find it hard to believe that "Twilio, but for money", could make more money than Twilio