The ability to toggle this means users who want full-quality images can still post them, **and use their Nitro ability**, but users who would prefer compressed images for data/battery/whatever reason can also be satisfied. Uncompressed images were one of discord's best aspect to me, and having that removed without warning is extremely disapointing. I would like to suggest the ability to simply turn off that compression of images for Nitro users (and even normal users who upload smaller-than-8MB images). This is personnaly the main reason why I got Nitro and if images are to stay compressed like this it is just a dealbreaker for me. The whole point of that is to be able to share full-quality full-size pictures and not have them lose details and quality by compressing them. I find it to be infuriating, as one of the main points of paying for nitro is the ability to upload files larger than 8MB, including picture. Check out our available positions here.Yesterday I noticed that when you upload an image from mobile (haven't tested on desktop yet), the image gets badly compressed: a 12MB pic was compressed to be 2MB, a 20MB pic was downgraded to about 5. We’re always looking for the next great addition to our engineering teams at Discord. As we continue to improve the app, we will be sure to keep it lean and fast. Performance is a core feature of Discord. We currently have 27 translations, so at 30KB each this saves the user nearly 1MB.Ĭode splitting lets us add languages, features, and polish without bloating the app. With this technique, we’re able to support as many unique languages as we want without impacting performance. This is our code splitting dynamically loading the required chunk to display the language. You might notice this when switching locales because it takes a moment to load the new one. Code splitting allows us to load only the one you use. Even our animations throughout the app are lazy loaded which allows us to continue adding art and polish while keeping performance high.Īdditionally, we support a lot of translations in the app. Like our code, our stylesheets are split into loadable chunks and only arrive when needed. The routes also contain stylesheets to layout the screens. If the function signatures look strange to you, it’s because we use Flow typing here at Discord. The makeLazy asynchronous component loader, with backoff retry. Everything else is loaded on-demand, allowing users to get the parts that matter most to them quickly (and so new users responding to invites don’t need to load the whole web app). When you boot up Discord, the core set of JavaScript, fonts, images, and stylesheets is about 700KB: about the size of Google’s minimal homepage in a browser. This also means that not all of the code is available instantly, but if the bundles are kept small and are well-planned, the user will not experience the loading anyway. Segmenting the code required to get the app going makes it load faster and use less memory than if we bundled it all together. Each piece of this takes time to load and parse while increasing the app’s memory usage. Large collection of loading gifs on transparent or opaque backgrounds. See, choose and use Do you have a great website or app, but your users get bored while loading Show them an animated image to brighten up their anticipation. How Discord Stays LeanĮvery time you load an app, it has to load up code and layout styles in order to run. Below you will find pictures in gif format. We always keep this in mind when adding new features like video chat, screen sharing, or the overlay.įor our desktop app, we achieve great performance while adding features with something called code splitting which loads code on demand. We know that our users are sensitive to performance: they are likely playing a visually intense game while talking on Discord with their friends and the last thing we want to do is cause performance issues. When people complain about “bloat” in software, they often mean that every new feature makes it slower to load, takes more memory, and taxes their CPU.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |