|
|
|
|
|
|
by flurp
3890 days ago
|
|
|
> 100x less memory and was much more performant Technically you're not prevented from doing so - you would just have to keep it to yourself (/family/friends/etc). Non-technical people rarely care about these things. > backstabbing developers I don't disagree. Would be interesting if there are any stats on who/what made Twitter popular, got any? > And why is that a problem? It's a problem for Twitter when you're trying to run a top-brand. Clients who don't keep up-to-date actually make Twitter look bad to the public. It also makes it harder for Twitter to innovate, move quickly (and probably get usage stats), without coordinating with external developers.
Apple actually does (in some aspects) force developers to keep their apps up to date. I develop iOS apps and this actually consumes way more time than I wish it did. Your concerns are valid from a third-party concern but from Twitter's first-party concern they are distractions. |
|
|
Yes ! But shouldn't we let the users decide that? If one of the clients implements the newer features and users like them, they would switch to the other client. That is assuming Twitter believes in competition. This makes it seem like they want to eliminate competition and consolidate control. Its rather anti-capitalistic.
>Your concerns are valid from a third-party concern but from Twitter's first-party concern they are distractions.
Yes, I'm siding with with the third parties. Twitter is a giant company with a megaphone to make their argument anywhere they want. Personally, I don't think anyone should care about Twitter's bottom line except Twitter themselves.