What if Meta’s hidden objective behind the Threads-to-Mastodon initiative is a play on app.net? And, what if threads.net is a measured step towards what could be the greatest pivot in all of tech?
What if Meta’s hidden objective behind the Threads-to-Mastodon initiative is a play on app.net? And, what if threads.net is a measured step towards what could be the greatest pivot in all of tech?
Many hate the “as a service” model, you might need to elaborate on how it will be implemented.
Lots of options here TBH and I haven’t put much thought into it. Providing a service by running and managing software updates, migrations etc…, is one. MongoDB Atlas and Confluent Cloud are good examples of what I had in mind.
Why do people hate the “as a service” model?
Edit: i dont know how many people feel this way, I beleave this and heard (verry biased, right to repair) people say this before.
Probably confusion but also abuse of the buisness model. “As a service” implies the recurrant payment is due to the service costing them resources to keep running. People like Adobe are just rent seeking. Also, the idea of ownership vs renting gets blurry.
Your examples, altho I havent thuroughly looked through them all look to be doing “as a service” correctly