<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web02.fireside.fm</fireside:hostname>
    <fireside:genDate>Sun, 19 Apr 2026 11:40:32 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Coder Radio - Episodes Tagged with “Smalltalk”</title>
    <link>https://coder.show/tags/smalltalk</link>
    <pubDate>Mon, 02 Sep 2019 23:00:00 -0400</pubDate>
    <description>A weekly talk show taking a pragmatic look at the art and business of Software Development and the world of technology.
</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>A weekly talk show</itunes:subtitle>
    <itunes:author>The Mad Botter</itunes:author>
    <itunes:summary>A weekly talk show taking a pragmatic look at the art and business of Software Development and the world of technology.
</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/b/b44de5fa-47c1-4e94-bf9e-c72f8d1c8f5d/cover.jpg?v=7"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:owner>
      <itunes:name>The Mad Botter</itunes:name>
      <itunes:email>michael@themadbotter.com</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<itunes:category text="Education">
  <itunes:category text="How To"/>
</itunes:category>
<itunes:category text="Business"/>
<item>
  <title>373: Interactive Investigations</title>
  <link>https://coder.show/373</link>
  <guid isPermaLink="false">fc417cc1-4b99-4d2b-9817-ffe1f3f624ae</guid>
  <pubDate>Mon, 02 Sep 2019 23:00:00 -0400</pubDate>
  <author>The Mad Botter</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/b44de5fa-47c1-4e94-bf9e-c72f8d1c8f5d/fc417cc1-4b99-4d2b-9817-ffe1f3f624ae.mp3" length="26640741" type="audio/mp3"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>The Mad Botter</itunes:author>
  <itunes:subtitle>We debate the best way to package scripting language apps then explore interactive development and the importance of a good shell.</itunes:subtitle>
  <itunes:duration>37:00</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/b/b44de5fa-47c1-4e94-bf9e-c72f8d1c8f5d/cover.jpg?v=7"/>
  <description>We debate the best way to package scripting language apps then explore interactive development and the importance of a good shell.
Plus npm bans terminal ads, what comes after Rust, and why Mike hates macros. 
</description>
  <itunes:keywords>.NET, C#, F#,  Rust, memory safety, formal methods, macros, monkeypatching, ruby, python, npm, advertising, supporting open source, macOS, scripting languages, application packaging, homebrew, snapcraft, flatpak, appimage, containers, docker, REPL, clojure, interactive development, smalltalk, forth, bpython, pry, rebel-readline, exploratory programming, sql, sqlite, litecli, Jupiter Broadcasting, Developer podcast, Coder Radio</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>We debate the best way to package scripting language apps then explore interactive development and the importance of a good shell.</p>

<p>Plus npm bans terminal ads, what comes after Rust, and why Mike hates macros.</p><p>Links:</p><ul><li><a title="Feedback: Getting started on .NET?" rel="nofollow" href="https://slexy.org/view/s2bssmHTau">Feedback: Getting started on .NET?</a> &mdash; My question is what is the easiest route to get started in .net development? When I looked online there are several different languages that can be used from C# ,F#, ASP.NEt among others. In your personal experience what is the easiest way to get started on this path?</li><li><a title="Feedback: Questioning Rust" rel="nofollow" href="https://slexy.org/view/s21pB91Mje">Feedback: Questioning Rust</a> &mdash; [...] The primary issue here is that most of the work to prove that safety (beyond "trust me" blocks) is pushed onto the developer instead of having the compiler insert protections surmised from uses of the data structures outlined in the source code.  After all, it can only prove what it is shown, not what it assumes.</li><li><a title="Feedback on Mike and Macros" rel="nofollow" href="https://www.reddit.com/r/CoderRadio/comments/cw5pki/crystal_clear_coder_radio_show_372/eyprsx0/">Feedback on Mike and Macros</a> &mdash; I'd also love to hear more about what you dislike about macros. Personally, I view Rust's macro system as one of its biggest selling points. I've written more than a few macros myself and, every time, they've simplified my code in ways I couldn't have managed without them. Perhaps more importantly, I've also noticed that many of my favorite crates make heavy use of macros—and doing so lets them expose a much more ergonomic API.</li><li><a title="The Imposter&#39;s Handbook by Rob Conery" rel="nofollow" href="https://www.goodreads.com/book/show/31572054-the-imposter-s-handbook">The Imposter's Handbook by Rob Conery</a> &mdash; You've had to learn on the job. New languages, new frameworks, new ways of doing things - a constant struggle just to stay current in the industry. This left no time to learn the foundational concepts and skills that come with a degree in Computer Science.
</li><li><a title="npm Bans Terminal Ads" rel="nofollow" href="https://www.zdnet.com/article/npm-bans-terminal-ads/">npm Bans Terminal Ads</a> &mdash; After last week a popular JavaScript library started showing full-blown ads in the npm command-line interface, npm, Inc., the company that runs the npm tool and website, has taken a stance and plans to ban such behavior in the future.
</li><li><a title="Apple wants to remove scripting languages from macOS" rel="nofollow" href="https://dev.to/stereobooster/apple-wants-to-remove-scripting-languages-2l0i">Apple wants to remove scripting languages from macOS</a> &mdash; Scripting language runtimes such as Python, Ruby, and Perl are included in macOS for compatibility with legacy software. In future versions of macOS, scripting language runtimes won’t be available by default, and may require you to install an additional package. If your software depends on scripting languages, it’s recommended that you bundle the runtime within the app</li><li><a title="Building Standalone Python Applications with PyOxidizer" rel="nofollow" href="https://gregoryszorc.com/blog/2019/06/24/building-standalone-python-applications-with-pyoxidizer/">Building Standalone Python Applications with PyOxidizer</a> &mdash; Python hasn't ever had a consistent story for how I give my code to someone else, especially if that someone else isn't a developer and just wants to use my application. </li><li><a title="Traveling Ruby: self-contained, portable Ruby binaries" rel="nofollow" href="https://phusion.github.io/traveling-ruby/">Traveling Ruby: self-contained, portable Ruby binaries</a> &mdash; Traveling Ruby lets you create self-contained Ruby app packages for Windows, Linux and OS X.</li><li><a title="ruby-packer" rel="nofollow" href="https://github.com/pmq20/ruby-packer">ruby-packer</a> &mdash; Packing your Ruby application into a single executable.

</li><li><a title="fogus: Notes on Interactive Computing Environments" rel="nofollow" href="http://blog.fogus.me/2019/04/03/notes-on-interactive-computing-environments/">fogus: Notes on Interactive Computing Environments</a> &mdash; Your programming environments should be an active partner in the act of creating systems.

</li><li><a title="Tim Ewald - Clojure: Programming with Hand Tools" rel="nofollow" href="https://www.youtube.com/watch?v=ShEez0JkOFw">Tim Ewald - Clojure: Programming with Hand Tools</a> &mdash; For most of human history, furniture was built by hand using a small set of simple tools. This approach connects you in a profoundly direct way to the work, your effort to the result. This changed with the rise of machine tools, which made production more efficient but also altered what's made and how we think about making it in in a profound way. This talk explores the effects of automation on our work, which is as relevant to software as it is to furniture, especially now that once again, with Clojure, we are building things using a small set of simple tools.</li><li><a title="Things You Didn&#39;t Know About GNU Readline" rel="nofollow" href="https://twobithistory.org/2019/08/22/readline.html">Things You Didn't Know About GNU Readline</a> &mdash; GNU Readline is an unassuming little software library that I relied on for years without realizing that it was there. Tens of thousands of people probably use it every day without thinking about it. If you use the Bash shell, every time you auto-complete a filename, or move the cursor around within a single line of input text, or search through the history of your previous commands, you are using GNU Readline. </li><li><a title="bpython" rel="nofollow" href="https://github.com/bpython/bpython">bpython</a> &mdash; A fancy curses interface to the Python interactive interpreter</li><li><a title="pry" rel="nofollow" href="https://github.com/pry/pry">pry</a> &mdash; Pry is a runtime developer console and IRB alternative with powerful introspection capabilities. Pry aims to be more than an IRB replacement. It is an attempt to bring REPL driven programming to the Ruby language.

</li><li><a title="Ammonite" rel="nofollow" href="https://ammonite.io/">Ammonite</a> &mdash; Ammonite lets you use the Scala language for scripting purposes: in the REPL, as scripts, as a library to use in existing projects, or as a standalone systems shell.

</li><li><a title="rebel-readline" rel="nofollow" href="https://github.com/bhauman/rebel-readline">rebel-readline</a> &mdash; A terminal readline library for Clojure Dialects

</li><li><a title="litecli" rel="nofollow" href="https://github.com/dbcli/litecli">litecli</a> &mdash; A command-line client for SQLite databases that has auto-completion and syntax highlighting.
</li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>We debate the best way to package scripting language apps then explore interactive development and the importance of a good shell.</p>

<p>Plus npm bans terminal ads, what comes after Rust, and why Mike hates macros.</p><p>Links:</p><ul><li><a title="Feedback: Getting started on .NET?" rel="nofollow" href="https://slexy.org/view/s2bssmHTau">Feedback: Getting started on .NET?</a> &mdash; My question is what is the easiest route to get started in .net development? When I looked online there are several different languages that can be used from C# ,F#, ASP.NEt among others. In your personal experience what is the easiest way to get started on this path?</li><li><a title="Feedback: Questioning Rust" rel="nofollow" href="https://slexy.org/view/s21pB91Mje">Feedback: Questioning Rust</a> &mdash; [...] The primary issue here is that most of the work to prove that safety (beyond "trust me" blocks) is pushed onto the developer instead of having the compiler insert protections surmised from uses of the data structures outlined in the source code.  After all, it can only prove what it is shown, not what it assumes.</li><li><a title="Feedback on Mike and Macros" rel="nofollow" href="https://www.reddit.com/r/CoderRadio/comments/cw5pki/crystal_clear_coder_radio_show_372/eyprsx0/">Feedback on Mike and Macros</a> &mdash; I'd also love to hear more about what you dislike about macros. Personally, I view Rust's macro system as one of its biggest selling points. I've written more than a few macros myself and, every time, they've simplified my code in ways I couldn't have managed without them. Perhaps more importantly, I've also noticed that many of my favorite crates make heavy use of macros—and doing so lets them expose a much more ergonomic API.</li><li><a title="The Imposter&#39;s Handbook by Rob Conery" rel="nofollow" href="https://www.goodreads.com/book/show/31572054-the-imposter-s-handbook">The Imposter's Handbook by Rob Conery</a> &mdash; You've had to learn on the job. New languages, new frameworks, new ways of doing things - a constant struggle just to stay current in the industry. This left no time to learn the foundational concepts and skills that come with a degree in Computer Science.
</li><li><a title="npm Bans Terminal Ads" rel="nofollow" href="https://www.zdnet.com/article/npm-bans-terminal-ads/">npm Bans Terminal Ads</a> &mdash; After last week a popular JavaScript library started showing full-blown ads in the npm command-line interface, npm, Inc., the company that runs the npm tool and website, has taken a stance and plans to ban such behavior in the future.
</li><li><a title="Apple wants to remove scripting languages from macOS" rel="nofollow" href="https://dev.to/stereobooster/apple-wants-to-remove-scripting-languages-2l0i">Apple wants to remove scripting languages from macOS</a> &mdash; Scripting language runtimes such as Python, Ruby, and Perl are included in macOS for compatibility with legacy software. In future versions of macOS, scripting language runtimes won’t be available by default, and may require you to install an additional package. If your software depends on scripting languages, it’s recommended that you bundle the runtime within the app</li><li><a title="Building Standalone Python Applications with PyOxidizer" rel="nofollow" href="https://gregoryszorc.com/blog/2019/06/24/building-standalone-python-applications-with-pyoxidizer/">Building Standalone Python Applications with PyOxidizer</a> &mdash; Python hasn't ever had a consistent story for how I give my code to someone else, especially if that someone else isn't a developer and just wants to use my application. </li><li><a title="Traveling Ruby: self-contained, portable Ruby binaries" rel="nofollow" href="https://phusion.github.io/traveling-ruby/">Traveling Ruby: self-contained, portable Ruby binaries</a> &mdash; Traveling Ruby lets you create self-contained Ruby app packages for Windows, Linux and OS X.</li><li><a title="ruby-packer" rel="nofollow" href="https://github.com/pmq20/ruby-packer">ruby-packer</a> &mdash; Packing your Ruby application into a single executable.

</li><li><a title="fogus: Notes on Interactive Computing Environments" rel="nofollow" href="http://blog.fogus.me/2019/04/03/notes-on-interactive-computing-environments/">fogus: Notes on Interactive Computing Environments</a> &mdash; Your programming environments should be an active partner in the act of creating systems.

</li><li><a title="Tim Ewald - Clojure: Programming with Hand Tools" rel="nofollow" href="https://www.youtube.com/watch?v=ShEez0JkOFw">Tim Ewald - Clojure: Programming with Hand Tools</a> &mdash; For most of human history, furniture was built by hand using a small set of simple tools. This approach connects you in a profoundly direct way to the work, your effort to the result. This changed with the rise of machine tools, which made production more efficient but also altered what's made and how we think about making it in in a profound way. This talk explores the effects of automation on our work, which is as relevant to software as it is to furniture, especially now that once again, with Clojure, we are building things using a small set of simple tools.</li><li><a title="Things You Didn&#39;t Know About GNU Readline" rel="nofollow" href="https://twobithistory.org/2019/08/22/readline.html">Things You Didn't Know About GNU Readline</a> &mdash; GNU Readline is an unassuming little software library that I relied on for years without realizing that it was there. Tens of thousands of people probably use it every day without thinking about it. If you use the Bash shell, every time you auto-complete a filename, or move the cursor around within a single line of input text, or search through the history of your previous commands, you are using GNU Readline. </li><li><a title="bpython" rel="nofollow" href="https://github.com/bpython/bpython">bpython</a> &mdash; A fancy curses interface to the Python interactive interpreter</li><li><a title="pry" rel="nofollow" href="https://github.com/pry/pry">pry</a> &mdash; Pry is a runtime developer console and IRB alternative with powerful introspection capabilities. Pry aims to be more than an IRB replacement. It is an attempt to bring REPL driven programming to the Ruby language.

</li><li><a title="Ammonite" rel="nofollow" href="https://ammonite.io/">Ammonite</a> &mdash; Ammonite lets you use the Scala language for scripting purposes: in the REPL, as scripts, as a library to use in existing projects, or as a standalone systems shell.

</li><li><a title="rebel-readline" rel="nofollow" href="https://github.com/bhauman/rebel-readline">rebel-readline</a> &mdash; A terminal readline library for Clojure Dialects

</li><li><a title="litecli" rel="nofollow" href="https://github.com/dbcli/litecli">litecli</a> &mdash; A command-line client for SQLite databases that has auto-completion and syntax highlighting.
</li></ul>]]>
  </itunes:summary>
</item>
<item>
  <title>365: Objectively Old</title>
  <link>https://coder.show/365</link>
  <guid isPermaLink="false">6de2350f-c728-4a0a-92bc-aa86e636c877</guid>
  <pubDate>Mon, 08 Jul 2019 22:00:00 -0400</pubDate>
  <author>The Mad Botter</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/b44de5fa-47c1-4e94-bf9e-c72f8d1c8f5d/6de2350f-c728-4a0a-92bc-aa86e636c877.mp3" length="27448238" type="audio/mp3"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>The Mad Botter</itunes:author>
  <itunes:subtitle>Wes turns back the clock and explores the message passing mania of writing Objective-C without a Mac, and we wax-poetic about programming language history.</itunes:subtitle>
  <itunes:duration>38:07</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/b/b44de5fa-47c1-4e94-bf9e-c72f8d1c8f5d/cover.jpg?v=7"/>
  <description>Wes turns back the clock and explores the message passing mania of writing Objective-C without a Mac, and we wax-poetic about programming language history.
Plus Mike gets real about the Windows Subsystem for Linux, and our take on the new MacBook keyboard leak. 
</description>
  <itunes:keywords>Macbook, server side development, backend development, developer laptop, keyboard, butterfly keyboard, scissor-switch keyboard, design, jony ive, GNUstep, language time travel, iOS, Smalltalk, programming languages, programming challenge, 7 languages, swift message passing, OOP, object oriented programming, C++, Objective-C, WSL, Windows, Linux, VSCode, windows development, Jupiter Broadcasting, Developer podcast, Coder Radio</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>Wes turns back the clock and explores the message passing mania of writing Objective-C without a Mac, and we wax-poetic about programming language history.</p>

<p>Plus Mike gets real about the Windows Subsystem for Linux, and our take on the new MacBook keyboard leak.</p><p>Links:</p><ul><li><a title="Apple is reportedly giving up on its controversial MacBook keyboard - The Verge" rel="nofollow" href="https://www.theverge.com/2019/7/4/20682079/apple-butterfly-switch-scissor-switch-2019-macbook-air-2020-macbook-pro">Apple is reportedly giving up on its controversial MacBook keyboard - The Verge</a> &mdash; Apple is planning to ditch the controversial butterfly keyboard used in its MacBooks since 2015, according to a new report from analyst Ming-Chi Kuo. 9to5Mac notes that Apple will reportedly move to a new scissor-switch design, which will use glass fiber to reinforce its keys. According to Kuo’s report, the first laptop to get the new keyboard will be a new MacBook Air model due out this year, followed by a new MacBook Pro in 2020. </li><li><a title="Objective-C - History - Wikipedia" rel="nofollow" href="https://en.wikipedia.org/wiki/Objective-C#History">Objective-C - History - Wikipedia</a> &mdash; After acquiring NeXT in 1996, Apple Computer used OpenStep in its then-new operating system, Mac OS X. This included Objective-C, NeXT's Objective-C-based developer tool, Project Builder, and its interface design tool, Interface Builder, both now merged into one application, Xcode. Most of Apple's current Cocoa API is based on OpenStep interface objects and is the most significant Objective-C environment being used for active development.</li><li><a title="A Short History of Objective-C" rel="nofollow" href="https://medium.com/chmcore/a-short-history-of-objective-c-aff9d2bde8dd">A Short History of Objective-C</a> &mdash; While most programmers discovered Objective-C only during the iPhone app revolution, Objective-C has been around for over 30 years. Objective-C has been the foundation of Apple’s desktop operating system, Mac OS X, since its debut in 2001, and was also the basis for NEXTSTEP — OS X’s immediate ancestor — created by Steve Jobs’ NeXT Computer Inc. However, Objective-C was created neither by Apple nor NeXT. Its origin was a small Connecticut startup in the early 1980s called Stepstone.</li><li><a title="GNUstep" rel="nofollow" href="http://www.gnustep.org/">GNUstep</a> &mdash; GNUstep is a mature Framework, suited both for advanced GUI desktop applications as well as server applications. The framework closely follows Apple's Cocoa (formerly NeXT's OpenStep) APIs but is portable to a variety of platforms and architectures.

</li><li><a title="GNUstep: Fun with Objective-C" rel="nofollow" href="http://www.gnustep.org/resources/ObjCFun.html">GNUstep: Fun with Objective-C</a> &mdash; Objective-C is a language based upon C, with a few additions that make it a complete, object-oriented language. Why do I think Objective-C is fun? Precisely because of this emphasis on simplicity</li><li><a title="Beginners Guide to Objective-C Programming" rel="nofollow" href="http://gnustep.made-it.com/BG-objc/">Beginners Guide to Objective-C Programming</a></li><li><a title="Installing and Using GNUstep and Objective-C on Linux - Techotopia" rel="nofollow" href="https://www.techotopia.com/index.php/Installing_and_Using_GNUstep_and_Objective-C_on_Linux">Installing and Using GNUstep and Objective-C on Linux - Techotopia</a> &mdash; The basics of Objective-C are supported by the GNU compiler collection. In order to utilize the full power of Objective-C together with the Cocoa /openStep environments on Linux, and to work with many of the examples covered in this book, it is necessary to install gcc, the gcc Objective-C support package and the GNUstep environment.

</li><li><a title="Objective-C Compiler and Runtime FAQ - GNUstepWiki" rel="nofollow" href="http://wiki.gnustep.org/index.php/Objective-C_Compiler_and_Runtime_FAQ">Objective-C Compiler and Runtime FAQ - GNUstepWiki</a> &mdash; The history of Objective-C in GCC is somewhat complicated. Originally, NeXT was forced to release the original Objective-C front end in order to comply with the GPL. This code was not quite compatible with the GNU runtime and so it was modified. NeXT did not adopt these modifications and so each release of GCC by NeXT, and then Apple, contained changes that needed back-porting to the main branch of GCC.

For a long time, GCC was the only compiler that worked with GNUstep. Unfortunately, the GCC team has not invested much effort in Objective-C in the last few years and it currently lags behind Apple's version by a significant amount.

</li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>Wes turns back the clock and explores the message passing mania of writing Objective-C without a Mac, and we wax-poetic about programming language history.</p>

<p>Plus Mike gets real about the Windows Subsystem for Linux, and our take on the new MacBook keyboard leak.</p><p>Links:</p><ul><li><a title="Apple is reportedly giving up on its controversial MacBook keyboard - The Verge" rel="nofollow" href="https://www.theverge.com/2019/7/4/20682079/apple-butterfly-switch-scissor-switch-2019-macbook-air-2020-macbook-pro">Apple is reportedly giving up on its controversial MacBook keyboard - The Verge</a> &mdash; Apple is planning to ditch the controversial butterfly keyboard used in its MacBooks since 2015, according to a new report from analyst Ming-Chi Kuo. 9to5Mac notes that Apple will reportedly move to a new scissor-switch design, which will use glass fiber to reinforce its keys. According to Kuo’s report, the first laptop to get the new keyboard will be a new MacBook Air model due out this year, followed by a new MacBook Pro in 2020. </li><li><a title="Objective-C - History - Wikipedia" rel="nofollow" href="https://en.wikipedia.org/wiki/Objective-C#History">Objective-C - History - Wikipedia</a> &mdash; After acquiring NeXT in 1996, Apple Computer used OpenStep in its then-new operating system, Mac OS X. This included Objective-C, NeXT's Objective-C-based developer tool, Project Builder, and its interface design tool, Interface Builder, both now merged into one application, Xcode. Most of Apple's current Cocoa API is based on OpenStep interface objects and is the most significant Objective-C environment being used for active development.</li><li><a title="A Short History of Objective-C" rel="nofollow" href="https://medium.com/chmcore/a-short-history-of-objective-c-aff9d2bde8dd">A Short History of Objective-C</a> &mdash; While most programmers discovered Objective-C only during the iPhone app revolution, Objective-C has been around for over 30 years. Objective-C has been the foundation of Apple’s desktop operating system, Mac OS X, since its debut in 2001, and was also the basis for NEXTSTEP — OS X’s immediate ancestor — created by Steve Jobs’ NeXT Computer Inc. However, Objective-C was created neither by Apple nor NeXT. Its origin was a small Connecticut startup in the early 1980s called Stepstone.</li><li><a title="GNUstep" rel="nofollow" href="http://www.gnustep.org/">GNUstep</a> &mdash; GNUstep is a mature Framework, suited both for advanced GUI desktop applications as well as server applications. The framework closely follows Apple's Cocoa (formerly NeXT's OpenStep) APIs but is portable to a variety of platforms and architectures.

</li><li><a title="GNUstep: Fun with Objective-C" rel="nofollow" href="http://www.gnustep.org/resources/ObjCFun.html">GNUstep: Fun with Objective-C</a> &mdash; Objective-C is a language based upon C, with a few additions that make it a complete, object-oriented language. Why do I think Objective-C is fun? Precisely because of this emphasis on simplicity</li><li><a title="Beginners Guide to Objective-C Programming" rel="nofollow" href="http://gnustep.made-it.com/BG-objc/">Beginners Guide to Objective-C Programming</a></li><li><a title="Installing and Using GNUstep and Objective-C on Linux - Techotopia" rel="nofollow" href="https://www.techotopia.com/index.php/Installing_and_Using_GNUstep_and_Objective-C_on_Linux">Installing and Using GNUstep and Objective-C on Linux - Techotopia</a> &mdash; The basics of Objective-C are supported by the GNU compiler collection. In order to utilize the full power of Objective-C together with the Cocoa /openStep environments on Linux, and to work with many of the examples covered in this book, it is necessary to install gcc, the gcc Objective-C support package and the GNUstep environment.

</li><li><a title="Objective-C Compiler and Runtime FAQ - GNUstepWiki" rel="nofollow" href="http://wiki.gnustep.org/index.php/Objective-C_Compiler_and_Runtime_FAQ">Objective-C Compiler and Runtime FAQ - GNUstepWiki</a> &mdash; The history of Objective-C in GCC is somewhat complicated. Originally, NeXT was forced to release the original Objective-C front end in order to comply with the GPL. This code was not quite compatible with the GNU runtime and so it was modified. NeXT did not adopt these modifications and so each release of GCC by NeXT, and then Apple, contained changes that needed back-porting to the main branch of GCC.

For a long time, GCC was the only compiler that worked with GNUstep. Unfortunately, the GCC team has not invested much effort in Objective-C in the last few years and it currently lags behind Apple's version by a significant amount.

</li></ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
