<?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 Brave New Geek</title><link>https://bravenewgeek.com/tag/programming-languages/</link><description>Recent content in Programming Languages on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 25 Jul 2017 09:06:26 -0500</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/programming-languages/index.xml" rel="self" type="application/rss+xml"/><item><title>Are We There Yet: The Go Generics Debate</title><link>https://bravenewgeek.com/are-we-there-yet-the-go-generics-debate/</link><pubDate>Mon, 24 Jul 2017 21:50:25 -0500</pubDate><guid>https://bravenewgeek.com/are-we-there-yet-the-go-generics-debate/</guid><description>&lt;p&gt;At GopherCon a couple weeks ago, Russ Cox gave a talk titled &lt;a href="https://www.youtube.com/watch?v=0Zbh_vmAKvk&amp;amp;index=4&amp;amp;list=PL2ntRZ1ySWBdD9bru6IR-_WXUgJqvrtx9"&gt;&lt;em&gt;The Future of Go&lt;/em&gt;&lt;/a&gt;, in which he discussed what the Go community might want to change about the language—particularly for the so-called &lt;em&gt;Go 2.0&lt;/em&gt; milestone—and the process for realizing those changes. Part of that process is identifying real-world use cases through &lt;a href="https://github.com/golang/go/wiki/ExperienceReports"&gt;experience reports&lt;/a&gt;, which turn an abstract problem into a concrete one and help the core team to understand its significance. Also mentioned in the talk, of course, were generics. Over the weekend, Dave Cheney posted &lt;a href="https://dave.cheney.net/2017/07/22/should-go-2-0-support-generics"&gt;&lt;em&gt;Should Go 2.0 support generics?&lt;/em&gt;&lt;/a&gt; Allow me to add to the noise.&lt;/p&gt;</description></item><item><title>Go Is Unapologetically Flawed, Here’s Why We Use It</title><link>https://bravenewgeek.com/go-is-unapologetically-flawed-heres-why-we-use-it/</link><pubDate>Wed, 20 May 2015 11:46:16 -0500</pubDate><guid>https://bravenewgeek.com/go-is-unapologetically-flawed-heres-why-we-use-it/</guid><description>&lt;p&gt;Go is decidedly polarizing. While many are &lt;a href="https://sendgrid.com/blog/convince-company-go-golang/"&gt;touting&lt;/a&gt; their &lt;a href="https://www.youtube.com/watch?v=bAQ9ShmXYLY"&gt;transition&lt;/a&gt; to Go, it has become equally fashionable to &lt;a href="http://nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/"&gt;criticize&lt;/a&gt; and &lt;a href="http://tmikov.blogspot.com/2015/02/you-dont-like-googles-go-because-you.html"&gt;mock&lt;/a&gt; the language. As Bjarne Stroustrup so eloquently put it, “There are only two kinds of programming languages: those people always bitch about and those nobody uses.” This adage couldn’t be more true. I apologize in advance for what appears to be just another in a long line of diatribes. I’m not really sorry, though.&lt;/p&gt;</description></item></channel></rss>