You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Any breaking release should only require a small amount of update work on the part of end users. Bundling too many breaking changes at once forces users to delay updating indefinitely. Make it as easy as possible for your user base to follow you, to evolve with you.https://twitter.com/GabriellaG439/status/1430201998045900801 …
The greatest asset of a language or framework is its ecosystem, and bundling breaking changes in a single release invalidates large swathes of your ecosystem. Always go with incremental change, so you bring the ecosystem with you. Evolution, not mass extinction.
It's quite a bit more nuanced than that. If there are significant breaking changes (with broad scope) that bring worthwhile gains, I'd rather they come together than deal with breaking changes every release. Breaking changes w/ narrow scope can be evolved more easily.
Also, significant, foundational changes enable other significant changes, so stagger them? I'd be more likely to stop using something that kept breaking every x months, I can deal and control a single big transition more easily, delay yes, but long term, meh.
but on the flip side it caused the Perl world some grief when some wanted to move forward & others wanted extensive backcompat it took a long time & many community hiccups & possibly still is, plus end user confusion. Rock n a hard place.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
