![]() ![]() It shows the grey smiley face placeholder image for every sticker pack apart from your bitmoji rip-off pack. * The sticker selector has been completely broken for at least 3 years. But if you kill messenger completely then bring it back, your message is back - even if you have sent and received dozens of messages in the interim. * Type something into the input box, quick-switch to another app, then switch back to messenger. Most of these have been ongoing for several months and some for several years. Just a few of the issues off the top of my head. It astounds me that people will take technical advice and use software libraries developed by this company that delivers such poor quality software. Messenger on Android is genuinely one of the buggiest pieces of software I have ever used. What might have happened if they had done better? For example, note that the original browser company, Netscape, failed due to poor code maintenance, letting IE take over. They could also avoid a lot of the chaos that comes when a company dies of pernicious waste. The users could be getting better software. Or everybody could just do less work and go home early, doing things they care about.Īnd speaking of use, let's note that the waste impacts the users and the world. The people forced into being code janitors could spend their time making things that actually get used. They could be learning, like adults do, how to clean up after themselves, and so lead richer lives. The same developers could be developing meaningful things. What you're doing here is known as the broken window fallacy. ![]() Wasted time, wasted opportunity, wasted money. The depressing part is the large amount of waste here. You work there to make more money and deleting some feature that is probably referenced by some other dead code somewhere else isn't profitable work for anybody.Ĭompanies don't suffer. Reality is that it isn't quite this easy (fewer users are that valuable, most don't use it daily, etc). Restyle a button to be more appealing in the peripheral vision of users and that probably breaches that threshold. It just has to be minimally better than what it's replacing. So your feature doesn't even have to be that good. That's like increasing the value of the average user by 1/200,000. When you have 3 billion users if you make the company 1/100th of a penny per user per year you pay for yourself. If not, and it never is, they'll leave it around and move on to something else. Once the feature is done, if it's easy to delete it they will. Implementing new features does.Īnd so engineers implement new features and write more code and release the features and get rewarded for doing so. They don't do things that don't get them rewarded. People at tech giants don't love their employers like they are their mother or something. Enable compile-time optionsīy specifying pre-processor flags, you can enable optional features like FTS5, Geopoly, etc.Because you don't make money deleting code. e.g./Note that on iOS the file system is sand-boxed, so you cannot access files/directories outside your app bundle directories.Īlternatively, you can place/move your database file using one of the many react-native fs libraries. The library creates/opens databases by appending the passed name plus, the documents directory on iOS and the files directory on Android, this differs from other SQL libraries (some place it in a If you have an existing database file you want to load you can navigate from these directories using dot notation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |