<?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>Bytecode on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/bytecode/</link><description>Recent content in Bytecode on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sat, 24 May 2014 07:36:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/bytecode/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Java is a compiled language and Python is not</title><link>http://karpoke.ignaciocano.com/2014/05/24/why-java-is-a-compiled-language-and-python-is-not/</link><pubDate>Sat, 24 May 2014 07:36:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2014/05/24/why-java-is-a-compiled-language-and-python-is-not/</guid><description>&lt;blockquote&gt;
&lt;p&gt;One comment’s answer was ’marketing’, which in a sense is correct; one
reason we call Java a compiled language is that that’s what Sun called
it from the start. Another comment noted that Java has an explicit
compilation phase that is separate from having the JVM execute your
Java program by interpreting the bytecodes. All of this points us
towards what I feel is the real answer:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;In Java, bytecode is a first class object. In Python it’s an
internal implementation detail.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;</description></item></channel></rss>