# Alternative Approaches ## Comparison Table | Publishing Legacy Code | Publishing Modern Code | Publishing Compiled Code | Publishing Editions | | | ---------------------------------------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------- | | Published source code | **Yes** | **Yes** | No | **Yes** | | Published compiled code | No | No | **Yes** | **Yes** | | Source and compiled code is published | No | No | Yes, however is difficult and non-standardised | **Yes** | | Producers can make use of modern features (e.g. esnext, babel) | No | Yes, however at the cost of environments that don’t support those features | **Yes** | **Yes** | | Consumers can make use of modern features (e.g. es modules, flow type) | No | Yes, however at the cost of consumers that don’t support those features | Yes, however is difficult and non-standardised | **Yes** | | Consumption always runs latest compatible code | No, legacy code always used, even on modern environments | No, modern code may not be compatible with legacy environments | Yes, however is difficult and non-standardised | **Yes, loaders can automatically load appropriate edition for target environment** | | Legacy bloat consumed on modern environments | Yes | **No** | No, however is difficult and non-standardised | **No** | | Modern features could break legacy consumption | **No** | Yes | **No** | **No** | | Fixing legacy consumption breaks is easy | No, likely requires manual code changes or polyfill | No, likely requires code rewrite or compilation | **Yes, change is a compiler flag** | **Yes, change is a compiler flag** | | Consumers informed about this | Yes, however is difficult and non-standardised | Yes, however is difficult and non-standardised | Yes, however is difficult and non-standardised | **Yes, renderers automatically inform consumers of their options** | ### --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://editions.bevry.me/comparisons/alternative-approaches.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.