However, a problem with sarcasm tag is that it wouldn't really help accessibility compared to say saying "Sarcasm:" or something like "(The preceding remark was sarcastic.)".
PHP is a much simpler language which helps a lot with optimizations. For instance, consider something like property access.
In PHP, doing `$a->b` accesses field `b` of object `$a`. The implementation is essentially type check (making sure `$a` is an object) and hash table lookup. If this fails, then it calls `__get` method if it exists.
In Python on the other hand, `a.b` involves `__getattr__`, `__getattribute__`, `__mro__`, `__get__`, `__set__`, `__delete__` and `__dict__`. Here is a description of how the attribute access works: https://docs.python.org/3/howto/descriptor.html#overview-of-....
> Records use : in their literal form, which is overloaded with type ascription. This is also annoying in cases where you might want to move a field into a let binding.
> Once sales start dying and a minimum time has passed, I will release the game source code as some kind of open source. I'm not very happy with the draconian nature of (L)GPL, nor do I believe the other licenses have much merit other than to boost the egos of the original authors, so I might just possibly release it all as public domain.
This did not happen yet, Minecraft is still selling really well.
It was also a personal (and opinion) statement from Markus Persson (notch), who fully owned the game at the time, predating the formation of Mojang, let alone Mojang's acquisition by Microsoft.
I'm disheartened also by the fact it'll never become open source, but the statement was never legally-binding and never part of the terms that a purchase of Minecraft (in alpha, at that) entailed.
Is that even relevant when not given any timeframe? I can and did believe Notch back when he said it, I don't think he was trying to be misleading, but with no timeframe and the game being the size that it is now microsoft might as well release the source code, yes, 500 years from now.
Can we please get some sort of code escrow system going, similar to how the national libraries collect all published works in a country? Video games are culture too.
I don't think there is anything wrong with storing passwords unencrypted locally assuming the machine itself has encrypted storage. Malware that retrieves passwords from password manager could get them from an unlocked password manager as well.
Reading a file and code execution (which is required for reading another processes memory) are two different levels of vulnerabilities.
Essentially if you have a piece a software with a bug that allows someone to remotely read files from you system, your browser stored passwords are compromised while your passwords stored encrypted are safe-ish depending on how good your passphrase is.
Of course if you have malware that can run arbitrary code on your system you are hosed either way.
Encrypting your mass storage devices doesn't protect against malicious code as by definition the filesystem is unlocked once you're logged in. Mass storage encryption is primarily protection against physical access.
Technically it may not be a copyright infringement - whether emojis can be copyrighted is quite complicated.
However, this is irrelevant as App Store Review guidelines say the following.
> Apps may use Unicode characters that render as Apple emoji in their app and app metadata. Apple emoji may not be used on other platforms or embedded directly in your app binary.
The problem here is that generally this is decide by courts, not by apple.
This is basically yet another piece of evidence of a monopoly. Apple acting as the judge, jury, and executioner regarding what it thinks is “it’s rights”
I think Apple would have to be stupid to block booting other operating systems on the devices they already have sold. This could easily lead to lawsuit, similar to one that Sony had when they removed OtherOS functionality from PlayStation 3.
Accessibility matters. If nothing else because it is a legal requirement with laws such as US's Americans with Disabilities Act, UK's Disability Discrimination Act, EU's European Accessibility Act, Australia's Disability Discrimination Act, and Ontario's Accessibility for Ontarians with Disabilities Act.
However, a problem with sarcasm tag is that it wouldn't really help accessibility compared to say saying "Sarcasm:" or something like "(The preceding remark was sarcastic.)".