However, I also feel that Ruby sometimes seems too focused on being backwards compatible, to a point where it risk hurting the ecosystem. I think this thread is a good example, because it seems like such a small and benign change, yet it's taken several years and lots of back and forth, and in the end the proposed change wasn't even applied(!?).

IRIs are mapped to URIs to retain backwards-compatibility with systems that do not support the new format.

Agree, but we're stuck with API compatibility for a good while.

Much of this sort of information was later reverse-engineered, and cross-browser support for basic operations is actually quite good. (Browsers still vary widely on the details.)

Note that this is a breaking API change in the libraries (more information in the README.md). It does not affect the backwards compatibility of the protocol itself.

Will my code break on Ruby 2.7? A short answer is “maybe not”. The changes in Ruby 2.7 are designed as a migration path towards 3.0. While in principle, Ruby 2.7 only warns against behaviors that will change in Ruby 3, it includes some incompatible changes we consider to be minor. See the “Other minor changes” section for details. Except for the warnings and minor changes, Ruby 2.7 attempts to keep the compatibility with Ruby 2.6. So, your code will probably work on Ruby 2.7, though it may emit warnings. And by running it on Ruby 2.7, you can check if your code is ready for Ruby 3.0.

Lumberjack::Logger does not extend from the Logger class in the standard library, but it does implement a compantible API.

We’re happy to report that the good people at Google and Mozilla are moving towards adoption as well.

I'm not very familiar with this feature. Do you know what version of Rails is required for this code to work? Is it Rails 6.0+? We run the test suite via Travis CI for many versions of Rails so I am concerned that this will cause test failures on older versions. Can we write the tests so that they gracefully exclude the CSP stuff on older versions where CSP is not supported?

Keep in mind that third party code with references to other files also processed by the asset Pipeline (images, stylesheets, etc.), will need to be rewritten to use helpers like asset_path.

{a: 1, b: 2, c: 3, d: 4} => {a:, b:, **rest} # a == 1, b == 2, rest == {:c=>3, :d=>4}

{a, b, ...rest} = {a: 1, b: 2, c: 3, d: 4}

The problem with using a newer distro is that it upgrades glibc, which is bad for compatibility with older distros.

React Final Form was written by the same guy (@erikras) that wrote Redux Form, so much of the API is exactly the same.

hyperscript is a perfectly good alternative and uses the same interface as matt esch's virtual-dom

The backwards compatible implementation of jsx(...), we would still support key passed as props. We'd just pull it off props and issue a warning that this pattern is deprecated. The upgrade path is to just pass it to JSX separately if you need it.

It's easy to persist the entire application state in a way that is backwards-compatible, so persisted states can survive application changes.

It does, however, provide the --porcelain option, which causes the output of git status --porcelain to be formatted in an easy-to-parse format for scripts, and will remain stable across Git versions and regardless of user configuration.

Downgrade the API version used at run time by exporting the DOCKER_API_VERSION=1.21 to environment variable on the client side.

Products using the same version of Gecko have identical support for Web standards.

Firefox is at the forefront of cross-browser compatibility.

cross-browser development

In the future, these attributes may expand without the API being versioned. The current attributes are:

I usually write example code that is for both Chrome and Firefox WebExtensions.

Coming back to the two ‘FreeSync’ settings in the monitor OSD, they differ in the variable refresh rate range that they support. ‘Standard Engine’ supports 90 – 144Hz (90 – 119Hz via HDMI) whilst ‘Ultimate Engine’ gives a broader variable refresh rate range of 70 – 144Hz (62 – 119Hz via HDMI). We didn’t notice any adverse effects when using ‘Ultimate Engine’, so we’d suggest users simply stick to that option.