<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Programming Languages on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/programming-languages/</link><description>Recent content in Programming Languages on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/programming-languages/index.xml" rel="self" type="application/rss+xml"/><item><title>Thirteen Criteria for Evaluating a Programming Language</title><link>https://severinbucher.com/posts/thirteen-criteria-for-choosing-a-programming-language/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/thirteen-criteria-for-choosing-a-programming-language/</guid><description>&lt;p>Most language choices are made for bad reasons. The last project used it, a conference talk was persuasive, the job description said so, or someone liked the syntax. A language outlasts the frameworks built with it, and often the manager who introduced it. A decision with that lifespan deserves a checklist.&lt;/p>
&lt;p>What follows is that checklist, in the order I work through it. The criteria pull against each other, so the real work is deciding which costs fit the project.&lt;/p></description></item></channel></rss>