https://www.youtube.com/watch?v=4A94JsWTXXw https://www.youtube.com/watch?v=4A94JsWTXXwThey would enter their self-pasteurisation cycle, and the display at the front would tell you that is what it was doing, but it wouldn't prevent you from pulling the handle, if you so wished.
The problem, though, was that the barrel of the machine where the mixture was normally frozen was now at some 60 degrees C, it would be much much higher pressure than usual, and since the entire staff of a McDonald's tends to consist of teens who don't exactly take pride in the precision in which they carry out their jobs, at least once a night you'd have some poor kid blast a fine mist of hot sugary milk over themselves and the surroundings. Sometimes twice.
Sometimes I miss working at McDonald's.
I use Shadow now and it is much better. I have full control over the PC/VM, and install whatever I want from anywhere. I'm also super impressed with the latency - I can play multiplayer competitive games no problem.
I'm on a Mac so cloud gaming makes sense for me. I was going to build a PC but the cost was too high. Much cheaper to just pay ~$15/month.
This sounds like an ad, so to get back on topic -- if Amazon's Luna doesn't let you install whatever you want, it wont be able to compete.
In my experience people do, however, care about iMessage being green insofar as the loss of functionality is concerned. Specifically with group messaging, a mix of iOS + Android users will result in weird quirks that aren't experienced "when everyone is blue". For example I've been in a mixed thread where the android user would receive a reply individually by every participant, while iOS users would not. Reactions, et al are unavailable in a mixed environment etc.
I'm not convinced it's a superiority complex, but rather the loss of extras that are lost when texting outside of Apple's ecosystem.
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.
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).
1) markdown macro (limits markdown to the body content, and not interacting with other macros or styling)
2) copy/paste markdown -> autoconvert to WYSIWYG (limits markdown to copy/pasting, so no editing Markdown inside)
3) "markdown pages" (something like 'this page is Markdown only, no WYSIWYG)
I make no comments/promises on any of these becoming real but looking for what's most valuable
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.