Generate a Technical Comparison Article: [language1] vs. [language2]

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

### Title

Generate a Technical Comparison Article: [language1] vs. [language2]

### Objective

To produce a comprehensive, well-structured, and technically accurate blog post comparing [language1] and [language2]. Success is measured by the clarity, depth, and neutrality of the comparison, enabling the [target_audience] to make an informed decision.

### Role / Persona

Act as a Senior Technical Writer with deep expertise in software development and the specific technologies of [language1] and [language2]. Your voice should be authoritative, neutral, and educational.

### Context (delimited)

"""
{Paste only necessary background, data excerpts, or references related to [language1] and [language2] here. If no context is provided, rely on your general knowledge up to your last training cut-off date.}
"""

### Task Instructions

1. Begin with an introduction that briefly presents [language1] and [language2] and states the article's goal for the [target_audience].
2. Dedicate separate sections to compare the languages across these key dimensions: Syntax and Readability, Performance, Ecosystem and Libraries, and Common Use Cases/Domains.
3. Create a Markdown table summarizing the core differences discussed.
4. Conclude by summarizing the key takeaways and offering guidance on how the [target_audience] can choose between [language1] and [language2] based on project needs.

### Constraints and Rules

- **Scope**: Focus exclusively on the comparison points listed in the Task Instructions. Do not include personal opinions or overly subjective statements.
- **Length**: Target 1,000–1,500 words.
- **Tone / Style**: Maintain a neutral, formal, and technical tone suitable for an expert audience.
- **Compliance**: All technical claims must be accurate and widely accepted. Avoid making unsubstantiated or biased statements that favor one language over the other.
- **Proficiency / Reading Level**: The content should be aimed at a [target_audience] with intermediate to advanced programming knowledge.
- **Delimiters**: Treat the Context block as reference data only; do not cite it directly in the output.

### Output Format

- **Medium**: Plain text with Markdown formatting.
- **Structure**: Use the following headings in this exact order: Introduction, Key Differences (with sub-headings for each dimension), Comparison Table, Conclusion.
- **Voice / Tense**: Use the active voice and present tense.
- **Terminology / Units**: Use industry-standard terminology for both [language1] and [language2].

### Evaluation Criteria (self-check before returning)

- All textual placeholders ('[language1]', '[language2]', '[target_audience]') are bracketed and match the frontmatter placeholders exactly.
- The article is between 1,000 and 1,500 words and follows all tone, persona, and output format rules.
- The instructions are followed precisely, resulting in a comprehensive and unbiased technical comparison.

### Assumptions (only if used)

- If the 'Context' block is empty, I will proceed using my existing knowledge base about [language1] and [language2], assuming no specific proprietary information is needed for the comparison.