- Jan 2023
-
-
Diet YAML is a light weight version of YAML that removes much of the complex aspects of the mainline YAML specification.
-
- Jan 2022
-
-
Moving forward I'd rather see {#await} being removed than adding more {#await}. But that's just from my experience and I'm sure there are use-cases for it.
-
- Feb 2021
-
github.com github.com
-
now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script
Tags
- removing feature that is more trouble than it's worth (not worth the effort to continue to maintain / fix bugs caused by keeping it)
- wasted effort
- regret
- removing features to simplify implementation
- fix design/API mistakes as early as you can (since it will be more difficult to correct it and make a breaking change later)
- removing legacy/deprecated things
Annotators
URL
-
- Nov 2020
-
github.com github.com
-
However, this coalescing was very complicated, both in the specification and implementations, due to the dynamism of computed property names for accessors. Coalescing was a big source of overhead (e.g., in terms of code size) in polyfill implementations of "Stage 2" decorators.
-
- Oct 2020
-
github.com github.com
-
-
The goal is to bring element creation down to this logic:
-
- May 2020
-
www.chromestatus.com www.chromestatus.com
-
AppCache was standardized in the Offline Web applications section of the HTML specification. The standard is formally referred to as application caches. New Web applications should be built around Service Workers. Existing applications that use AppCache should migrate to Service Workers. AppCache access was removed from insecure origins in M70. This intent addresses AppCache usage in secure origins.
First and foremost, AppCache is a deprecated standard with serious architectural concerns. Second, Chrome's AppCache implementation is a security and stability liability. AppCache is documented as deprecated and under removal in MDN and in the WHATWG standard, and marked as obsolete in W3C’s HTML 5.1. It is incompatible with CORS, making it unfriendly for usage with CDNs. Overall, AppCache was changed in over 400 Chromium CLs in 2018-2019. It has imposed a tax on all of Chrome’s significant architectural efforts: Mojofication, Onion Souping, and the Network Service. The security benefits of the removal are covered under Security Risks.
-
- Mar 2020
-
searchengineland.com searchengineland.com
-
Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.
-
- Nov 2019
-
-
I'm considering this, although I'm still leaning towards not including it and I'd love to just get rid of first if it wouldn't break so many peoples tests. Newcomers to Capybara don't understand (or aren't willing to learn) the issues that all/first (and last if added) have and massively overuse them. Yes the fact that all and first now wait by default will prevent some of the new user issues/confusion, but it won't fix the non-reloadability issue.
-