The biggest request I have of JIRA aside from performance is that whatever markdown/markup language you choose, that it be consistent across the entire product.
It is so frustrating to have to remember to use double-curlies for inline code/pre sometimes, and backticks other times. In each case, the other doesn't work. More than once using one has resulted it rendering correctly on the immediate page but not on the next.
This is one I encounter regularly but is far from the only inconsistency in support.
Also going to sound like an ad, but I stream PC VR from a cloud Shadow PC to my Oculus Quest over 5GHz Wi-Fi (effectiveness is really dependent on your proximity to their data centers) but it is really remarkable how effective it is. It is more lag than streaming from a local PC but not to the point where most games are unplayable. I can also play the same games with the same saves from my phone with their app using a Bluetooth-paired gaming controller. Couldn't be happier with their service.
> Interesting comment about the blue iMessage bubbles. I've definitely heard of it, and have seen the memes on the internet, but have never actually met anyone that cared about the _color_.
The color is used as a proxy to discuss the functionality. "Chatting blue" is more about the features that come with it than the actual bubble color, though the latter is easier to mention quickly.
Personally I've been surprised what an impact even just a now-typing indicator has on the conversation and find "green" conversations can feel a lot more disjointed.
I am more bothered about the hiding of the URL to some weird breadcrumb-y structure than the showing (now re-hiding?) of the favicon. Gave DDG a try and don't see myself switching back.
I used Mirage with Ember for many years and it has changed the way I think and approach front-end acceptance testing. I was very excited to see the work to extract the Ember-specific bits from the rest of the library (originally by @cowboyd / Charles Lowell and now from the original author Sam Selikoff himself) and am using it with a React app to great success.
It works fine when you open the image directly, but it will not apply EXIF corrects for inline images (<img> tag). There are JS libraries that load the image as file data to read the EXIF data and apply the correct rotation, but those fail in some cases (HTTPS trying to load data for an HTTP-linked image, for example).
A recent LastPass version does not fail gracefully and a lot of my webapps started getting weird console errors from users with LastPass extensions that were trying to unsuccessfully inject into our forms. :/
It is so frustrating to have to remember to use double-curlies for inline code/pre sometimes, and backticks other times. In each case, the other doesn't work. More than once using one has resulted it rendering correctly on the immediate page but not on the next.
This is one I encounter regularly but is far from the only inconsistency in support.