To clarify, this is related to Red Hat Enterprise Linux the distro, not Red Hat the company. Fedora 29 (released a few days ago) has a KDE spin, and the project has made no mention of discontinuing that. https://spins.fedoraproject.org/kde/download/index.html
Full disclosure: I work for Red Hat (but not on RHEL or Fedora).
Or, maybe the service is 4.66 times as good as Amazon S3?
Or, the 14th letter of the alphabet is N. If we swap that for 14 we get "CN", which is the top-level domain for China, which is most certainly not in France.
The conspiracy theory possibilities are endless! ;)
This is a really cool start! In the future, I'd love to be able to set preferences and save them to local storage. (For example, it would be nice to be able to set date formatting or location.) I know I could grab a copy of the code and then change those things myself, but then upgrades would be a pain. Overall, though, good stuff!
Exciting stuff! If you're already on Aurora, when you auto-update to developer edition, you'll switch over to the new dev profile and your bookmarks and settings will be gone. You can get at those by opening the profile manager and switching back to the default profile, or by using a stable version of Firefox.
Sublime Text isn't free; it's sold on the honor system:
"Sublime Text may be downloaded and evaluated for free, however a license must be purchased for continued use."
The developer could try to enforce this rule by building in DRM or by threatening legal action, but those things would make for a pretty crappy user experience. Instead, the author chose to do the right thing by users and provide an evaluation version with no restrictions.
Legally and technically, you can certainly use Sublime Text without paying for it. To me, though, using Sublime Text for your everyday work without paying for it is the ethical equivalent of using a cracked version of Photoshop.
Personally, I find the "that" variable to be a little confusing. A developer looking at the code might wonder whether "that" is the plugin, a DOM element, or something else. To make the code a little clearer, you could use something like "elem" to represent the element on which the plugin has been called, and "plugin" to represent the plugin itself.
Full disclosure: I work for Red Hat (but not on RHEL or Fedora).