https://schema.org/docs/developers.html seems to indicate that developers should prefer https version of the vocabulary definitions.

However the JSON-LD context (even with @context: https://schema.org/) maps to the http namespace which has been consistent since the beginning of schema.org (I do not suggest changing this!) - try for instance in https://json-ld.org/playground/

I think it's good the JSON-LD is consistent for both @context examples.

However RDFa examples like https://schema.org/CreativeWork use vocab="https://schema.org/" as namespace declaration.

I think developers.html should acknowledge this difference so that developers are aware of both variants, and highlight that the JSON-LD context will map to http. It depends on where the data comes from which variant developers will want.

Something like:

For consistency with structured data already deployed with JSON-LD, the @context resolved for both http://schema.org/ and https://schema.org/ will continue to be mapped to terms in the http namespace.

BTW: developers.html page could also benefit with a link to the JSON-LD context https://schema.org/docs/jsonldcontext.json as I struggled to find it!