<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.5 (http://www.squarespace.com/) on Thu, 29 Jul 2010 16:58:08 GMT--><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><title>LJ CEO Blog</title><subtitle>LJ CEO Blog</subtitle><id>http://www.legacyj.com/lj-ceo-blog/</id><link rel="alternate" type="application/xhtml+xml" href="http://www.legacyj.com/lj-ceo-blog/"/><link rel="self" type="application/atom+xml" href="http://www.legacyj.com/lj-ceo-blog/atom.xml"/><updated>2010-03-25T16:53:59Z</updated><generator uri="http://www.squarespace.com/" version="Squarespace Site Server v5.11.5 (http://www.squarespace.com/)">Squarespace</generator><entry><title>thu blog test</title><id>http://www.legacyj.com/lj-ceo-blog/2010/3/25/thu-blog-test.html</id><link rel="alternate" type="text/html" href="http://www.legacyj.com/lj-ceo-blog/2010/3/25/thu-blog-test.html"/><author><name>Daniel Myers</name></author><published>2010-03-25T16:53:59Z</published><updated>2010-03-25T16:53:59Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>In the course of preparing the re-launch of the company, we have changedalmost every aspect of how we use our technology to solve Cobolmodernization issues.</p>]]></content></entry><entry><title>2nd thoughts...</title><id>http://www.legacyj.com/lj-ceo-blog/2009/12/3/2nd-thoughts.html</id><link rel="alternate" type="text/html" href="http://www.legacyj.com/lj-ceo-blog/2009/12/3/2nd-thoughts.html"/><author><name>Daniel Myers</name></author><published>2009-12-03T08:04:48Z</published><updated>2009-12-03T08:04:48Z</updated><content type="html" xml:lang="en-US"><![CDATA[<p>As the recently appointed CEO for LegacyJ -- the 10-year "new" name for Synkronix -- I have a variety of facts that may be of value to your readers. Our architect, Brian Sullivan, took the bold step in 1995 to conclude that the object-oriented profile of Sun's new Java language -- and Sun's backing -- would create the environment needed to move old Cobol applications "seamlessly"... All you had to do was create a translation engine significantly in advance of the introduction of J2EE, most of JVM, most of why you could verify that this was, indeed, an outstanding selection -- not a wild-eyed graduate degree programmer's mistake...<br /><br />Still, it was 5+ years before Java was close to becoming the standard it is today.&nbsp; <br /><br /></p>]]></content></entry></feed>