Teams does both - normally it’s Enter to submit and Shift+Enter for a new line, but when you open the formatting tools it switches. They at least do have a message indicating which key combo inputs a new line, but it still gets me on occasion.
142 karma · joined August 23, 2017
Still very disappointed that macOS has not been supported since Catalina (10.15) dropped 32-bit support - from my understanding, the 32-bit architecture is deeply integrated into Wine and removing it would be a significant effort. Understandably the focus has always been on Linux, but I would still appreciate at least an update from the team on potential macOS support in the future.
It's not the SIM card slot - that's on the left side. It's not a new TouchID sensor - the website doesn't even mention it at all. And yet it exists in every single render.
As opposed to writing a new engine from scratch (Servo), I wonder how feasible it would be to fork one of these existing engines and modularize its contents? The ability to start from (close to) zero and then pick and choose which features you want in your engine would be pretty attractive to lots of developers. The application that never expects to play any sort of media or access any peripherals could exclude the respective components from the build entirely.
Of the announcements from this most recent keynote, what was new? The third camera on the iPhone? The update of the main series iPads to use the "Pro" look? A new screen in the Watch? A couple games and a tv show?
These keynotes stopped being relevant when Apple stopped producing anything keynote-worthy. They're just routine at this point.
(The shortlink above is actually safe - it redirects to https://jigsaw.google.com/)
I can forgive the extremely contrived decks, but using a card to completely change the behavior of the majority of your cards doesn't mean the game itself is Turing complete. If anything, this is just showing how you can utilize Magic game mechanics to create a Turing Machine.
A language: It's language was originally designed to be a successor to ActionScript 3, as Haxe was originally designed to replace Flash.
A cross-compiler: The most interesting part in my opinion. Basically you can write Haxe code and target many, many different platforms. Mostly how this works is by transpiling, or translating the code into valid code in other languages.
A cross-platform standard library: This just means that it includes its standard library whenever it cross-compiles.
Ways to access native capabilities: Depending on your desired compilation target, you can use specific functionality only available on that target.