43 karma · joined September 17, 2018
> I just saw your post this morning. I'd like to help resolve this as quickly as possible, if I can. I'm not exactly sure what happened in your case. This doesn't sounds fair or right, and isn't a TeamViewer business practice.
Not sure where it went from there though
edit: there’s a second page of comments where the issue appeared to be resolved but many others reported the same issue and were ignored
Edit: typo
Not sure how I feel about a statement this broad. I work mostly with front end code and I try neat things and tricks to reduce resource use all the time. I also always push for the lightest way of doing things in PRs. I’m certain I’m not the only engineer who thinks like this.
1. https://en.m.wikipedia.org/wiki/Usage_share_of_operating_sys...
>People are more likely to use a buggy app that has features they want over a perfect app with limited features.
I understand the article is specifically addressing the slowness of chat apps..if we’re talking about messenger: I’m sure they could use a fraction of the RAM with the same features. But the fact of the matter is that it has the features people want and we will continue to use it. Is Facebook so in the wrong if their RAM hungry App is so successful? I’m not sure.
On a side note regarding good software, I enjoyed using a site called teamtreehouse so much that I pay for it still 3 years later and I never log in.