3 ms·
Then don't use this or teach it. Don't build for it. Isolate it. Let it die. Cut off its supply. Make it irrelevant. Exclude it from connectivity options by def
by nonrandomstring 2y ago
Then don't use this or teach it. Don't build for it. Isolate it. Let
it die. Cut off its supply. Make it irrelevant. Exclude it from
connectivity options by default, out of caution. It seems pointless to
complain that you can't have a bite of the poison fruit.
But also make sure others know. Actively warn and discourage other
developers away from that technology. Make "Threads" regret their lack
of openness.
- ang_cire 2y agoThe problem is that individuals cannot cut it out, because big tech firms use it pretty widely. It's basically a moat that allows companies to ship products using a shared standard, but makes it impossible for individual developers to (especially ones who aren't actively trying to start a business, but even then, $7500 a year is a lot for a garage-level startup for a technical standard). Imagine how much less innovation there would be if it cost $7,500 a year to write anything that uses the Internet Protocol suite of standards.
- nonrandomstring 2y agoI don't like to make predictions, but I think it will all eventually be swept away by forced open interoperability that is coming in strong from Europe. I don't feel any loss for independent developers who feel excluded from proprietary, locked "markets". It's saving them from wasting time. Let's check-in again on this situation in a couple of years. I'll bet "threads" is not even on the map. In the long game it always pays to go with the most free, open and interoperable standards, even if it limits opportunities in the short term.