<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Understanding Java Compiler and Java Virtual Machine &#8211; Part 4	</title>
	<atom:link href="https://www.tecmint.com/understanding-java-compiler-and-java-virtual-machine/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/understanding-java-compiler-and-java-virtual-machine/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Thu, 03 May 2018 06:23:29 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: priya		</title>
		<link>https://www.tecmint.com/understanding-java-compiler-and-java-virtual-machine/comment-page-1/#comment-988911</link>

		<dc:creator><![CDATA[priya]]></dc:creator>
		<pubDate>Thu, 03 May 2018 06:23:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=14845#comment-988911</guid>

					<description><![CDATA[JVM allows Java portability to execute within platform and hardware-independent applications. many thanks for sharing this article.]]></description>
			<content:encoded><![CDATA[<p>JVM allows Java portability to execute within platform and hardware-independent applications. many thanks for sharing this article.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Priya		</title>
		<link>https://www.tecmint.com/understanding-java-compiler-and-java-virtual-machine/comment-page-1/#comment-932907</link>

		<dc:creator><![CDATA[Priya]]></dc:creator>
		<pubDate>Wed, 08 Nov 2017 08:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=14845#comment-932907</guid>

					<description><![CDATA[JVM is a very important concept in Java, many thanks for sharing this article. keep blogging.]]></description>
			<content:encoded><![CDATA[<p>JVM is a very important concept in Java, many thanks for sharing this article. keep blogging.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: dillon wesley stewart		</title>
		<link>https://www.tecmint.com/understanding-java-compiler-and-java-virtual-machine/comment-page-1/#comment-636187</link>

		<dc:creator><![CDATA[dillon wesley stewart]]></dc:creator>
		<pubDate>Sun, 02 Aug 2015 07:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=14845#comment-636187</guid>

					<description><![CDATA[When interest in virtual machinery began exploding in popularity, enabling so much in the Cloud storage ability, Networking in multiple device platforms, and in the limitless possible efforts developed in ap design since(bug fix, pre-run time, beta,etc...)itwas easy, even as a novice computer user(still have little clue) to see the potential in both possitive and negative usage.
It has become a prevelent method by which email scams for compiling information/data and financial activity of nefarious origins are so prevelent now that I say,&quot;p-sha!!!&quot;
Reading about the linux kernal earlier this year, and the many anomolys discovered in the brand new hp win8.1 laptop I received as a birthday present brought my attention to the basic principles which enable the loopback interface and java compiler to function as designed. Having had read virtual theory and aplicable practice, as well as beta testing since 11&#039; some of these platforms now regularly utilized now in almost every smartphone and computer which includes adobe or google+ storage and a number of other aps now grown huge since, all this enabled me to be far less unaware of those instances where recognizing the java platform&#039;s flaw/s. These begin in the char created within the kernel, establishing a runtime bios not native to the initial bios initiated in factory design. As a result, and as a result of the incredible loss of data speeds, due to the compiler having to rewrite, in &quot;realtime&quot;, for its virtual java platform/ap/machine. This is alarming for several reasons:who would wish to enjoy the benefit of a birthday gift with 6g ram which opperates as if it carries 512mb?
the char creates a gap of an exponentially large defenseless week point for anyone to further institute virtual runtime machinery compiled ether alongside, parented, or in a hidden/background process that ultimately creates an ownership conflict between the java compiler and the owner of the bios (owned wholey by the purchaser, and not so &quot;open source&quot; as to relinquish control without contractual agreement(something yet to become more than moot, as a resultof tech advancements, and java bottom line&#039;s dependence in many ways upon this ambiguity.
finally, it establishes a microsoft-like monopolly(similar to the early nineties) that can potentally arm the growth in tech advancements, as the auto industry and the combustable engine(compiler) may do in a like manner over time.
Maybe, I am only proving how little I do know about computers by writing all of ghis, and maybe I am too novice to completely understand what I am seeing, reading, and imagining capable in the run time java environment, pre-java platform(kernel), and how little we know of what mathmatics et discovered may revolutionalize the next generation of advancements we make inthe tech industry(especially considering the fiber optic increases in data speads forthcoming here in tempe, az. Which would only further enable, lets say, a computer user anywhere in the world, to char the bios of another computer in tempe, and then take advantage of any of those just outside the grid of fiber optics, who are snails paces behind discovery that their data may be actively consumed by others before they even recognize they have data which can be taken(data being a comodity nowadays) by a &quot;pirating&quot; scam to network alterior phone options from verizon, t-mobile, sprint, etc...) 
My imagination just boggles my own mind, and I fear these are just iceberg tips.]]></description>
			<content:encoded><![CDATA[<p>When interest in virtual machinery began exploding in popularity, enabling so much in the Cloud storage ability, Networking in multiple device platforms, and in the limitless possible efforts developed in ap design since(bug fix, pre-run time, beta,etc&#8230;)itwas easy, even as a novice computer user(still have little clue) to see the potential in both possitive and negative usage.<br />
It has become a prevelent method by which email scams for compiling information/data and financial activity of nefarious origins are so prevelent now that I say,&#8221;p-sha!!!&#8221;<br />
Reading about the linux kernal earlier this year, and the many anomolys discovered in the brand new hp win8.1 laptop I received as a birthday present brought my attention to the basic principles which enable the loopback interface and java compiler to function as designed. Having had read virtual theory and aplicable practice, as well as beta testing since 11&#8242; some of these platforms now regularly utilized now in almost every smartphone and computer which includes adobe or google+ storage and a number of other aps now grown huge since, all this enabled me to be far less unaware of those instances where recognizing the java platform&#8217;s flaw/s. These begin in the char created within the kernel, establishing a runtime bios not native to the initial bios initiated in factory design. As a result, and as a result of the incredible loss of data speeds, due to the compiler having to rewrite, in &#8220;realtime&#8221;, for its virtual java platform/ap/machine. This is alarming for several reasons:who would wish to enjoy the benefit of a birthday gift with 6g ram which opperates as if it carries 512mb?<br />
the char creates a gap of an exponentially large defenseless week point for anyone to further institute virtual runtime machinery compiled ether alongside, parented, or in a hidden/background process that ultimately creates an ownership conflict between the java compiler and the owner of the bios (owned wholey by the purchaser, and not so &#8220;open source&#8221; as to relinquish control without contractual agreement(something yet to become more than moot, as a resultof tech advancements, and java bottom line&#8217;s dependence in many ways upon this ambiguity.<br />
finally, it establishes a microsoft-like monopolly(similar to the early nineties) that can potentally arm the growth in tech advancements, as the auto industry and the combustable engine(compiler) may do in a like manner over time.<br />
Maybe, I am only proving how little I do know about computers by writing all of ghis, and maybe I am too novice to completely understand what I am seeing, reading, and imagining capable in the run time java environment, pre-java platform(kernel), and how little we know of what mathmatics et discovered may revolutionalize the next generation of advancements we make inthe tech industry(especially considering the fiber optic increases in data speads forthcoming here in tempe, az. Which would only further enable, lets say, a computer user anywhere in the world, to char the bios of another computer in tempe, and then take advantage of any of those just outside the grid of fiber optics, who are snails paces behind discovery that their data may be actively consumed by others before they even recognize they have data which can be taken(data being a comodity nowadays) by a &#8220;pirating&#8221; scam to network alterior phone options from verizon, t-mobile, sprint, etc&#8230;)<br />
My imagination just boggles my own mind, and I fear these are just iceberg tips.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
