<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vierundsechzig.de</title>
	<atom:link href="http://www.vierundsechzig.de/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.vierundsechzig.de/blog</link>
	<description>Software&#038;Service</description>
	<lastBuildDate>Fri, 18 May 2012 05:06:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Do you like where Oracle is taking you? &#8211; jdk12 coming in 2021 (maybe)</title>
		<link>http://www.vierundsechzig.de/blog/?p=543</link>
		<comments>http://www.vierundsechzig.de/blog/?p=543#comments</comments>
		<pubDate>Wed, 18 Apr 2012 05:42:05 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[jdk8]]></category>
		<category><![CDATA[lambdas]]></category>
		<category><![CDATA[oracle]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=543</guid>
		<description><![CDATA[Simon Ritter from Oracle outlined just recently the upcoming jdk 8 and the future directions that oracle wants to take the jdk. According to their plans, 2021 is going to be a great year, as the jdk12 will see the probably dim light of a smog-filled day: They certainly have plans for java. Focusing on [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=543</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Roll out the RedCarpet: Macros for Markdown</title>
		<link>http://www.vierundsechzig.de/blog/?p=527</link>
		<comments>http://www.vierundsechzig.de/blog/?p=527#comments</comments>
		<pubDate>Thu, 29 Mar 2012 10:53:07 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Rails]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[macros]]></category>
		<category><![CDATA[markdown]]></category>
		<category><![CDATA[redcarpet]]></category>
		<category><![CDATA[rendering]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=527</guid>
		<description><![CDATA[Letting Users use WYSIWYG-Editors for writing content is usually a bad idea: We all start with good intentions, but sooner or later, this pseudo-html produces a great, ugly markup-mess (e.g. the living hell that Microsofts Word places on the Clipboard if you paste it into TinyMCE. That&#8217;s why we replaced all this nastiness with simpler [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=527</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>As a Webadministrator, in order to make sure we serve our customers, my website should be monitored.</title>
		<link>http://www.vierundsechzig.de/blog/?p=522</link>
		<comments>http://www.vierundsechzig.de/blog/?p=522#comments</comments>
		<pubDate>Wed, 07 Mar 2012 07:40:38 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[arquillian]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[Seam]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=522</guid>
		<description><![CDATA[He that is amonge you without synne, let him cast the first stone at her. &#8211; can&#8217;t say that something like this did not really ever happen to me, but the outages on the various jboss-websites appear quite frequently. This is especially annoying, when it happens for Arquillian, a project whose sole purpose it is [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=522</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MVC-Testing in Spring: Not yet, but it&#8217;s getting there&#8230;</title>
		<link>http://www.vierundsechzig.de/blog/?p=520</link>
		<comments>http://www.vierundsechzig.de/blog/?p=520#comments</comments>
		<pubDate>Wed, 07 Mar 2012 06:51:17 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[arqullian]]></category>
		<category><![CDATA[Spring]]></category>
		<category><![CDATA[spring mvc]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=520</guid>
		<description><![CDATA[There is an excelllent talk by Sam Brannen and Rossen Stoyanchev about Testing-methods and advances in Spring 3.1. Spring is adopting the annotation-style of configuration everywhere, which comes in very handy inside testing-classes and finally makes it manageable to setup Test-Contexts. However, it still remains awfully complex, which is probably a good reminder on how [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=520</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Note to self: Spork&amp;FactoryGirl &#8211; factories are not reloaded out-of the box</title>
		<link>http://www.vierundsechzig.de/blog/?p=512</link>
		<comments>http://www.vierundsechzig.de/blog/?p=512#comments</comments>
		<pubDate>Mon, 05 Mar 2012 15:44:15 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[bundler]]></category>
		<category><![CDATA[factory_girl]]></category>
		<category><![CDATA[note to self]]></category>
		<category><![CDATA[spork]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=512</guid>
		<description><![CDATA[Just a quick reminder: If you happen to use spork &#8211; and I bet you do as your tests run painstakingly slow as do mine &#8211; don&#8217;t expect your factories to be reloaded automtically. If you are using factory_girl, you&#8217;re probably also using factory-girl-rails. factory-girl-rails is just a little convenience-wrapper packaged as a railtie, that [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=512</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Long Running rake-tasks on Heroku</title>
		<link>http://www.vierundsechzig.de/blog/?p=442</link>
		<comments>http://www.vierundsechzig.de/blog/?p=442#comments</comments>
		<pubDate>Mon, 16 Jan 2012 16:45:26 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Cloud]]></category>
		<category><![CDATA[delayed_job]]></category>
		<category><![CDATA[delayed_task]]></category>
		<category><![CDATA[heroku]]></category>
		<category><![CDATA[hirefire]]></category>
		<category><![CDATA[import]]></category>
		<category><![CDATA[long-running]]></category>
		<category><![CDATA[rake]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=442</guid>
		<description><![CDATA[I used to do lots of imports using rake on our production-machine. This is quite handy if you have some legacy-data (a CSV-file from an old excel-file etc.) and works super-easy. Until I moved all my apps to heroku: here, long-running is fine if long is under 30 seconds: Then your job gets killed by [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=442</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Note to self: rspec-rails belongs in both :test __and__ :development</title>
		<link>http://www.vierundsechzig.de/blog/?p=434</link>
		<comments>http://www.vierundsechzig.de/blog/?p=434#comments</comments>
		<pubDate>Wed, 28 Dec 2011 18:21:50 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Rails]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[rake]]></category>
		<category><![CDATA[rspec]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=434</guid>
		<description><![CDATA[Just in case you wonder why your spec-rake-tasks are not found &#8211; this does not work group :test do gem &#34;rspec-rails&#34;, &#34;~&#62;= 2.7.0&#34; gem &#34;database_cleaner&#34; gem &#34;spork&#34;, '~&#62; 0.9.0.rc' ... end although it looks obvious on first sight. But now, your spec-tasks are not available in the development-environment and so rake -T spec comes up [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=434</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ember or knockout or backbone or spine or &#8230; &#8211; still confused? Just try them all!</title>
		<link>http://www.vierundsechzig.de/blog/?p=429</link>
		<comments>http://www.vierundsechzig.de/blog/?p=429#comments</comments>
		<pubDate>Thu, 22 Dec 2011 10:04:34 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[backbone.js]]></category>
		<category><![CDATA[ember.js]]></category>
		<category><![CDATA[knockout.js]]></category>
		<category><![CDATA[spine]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=429</guid>
		<description><![CDATA[2011 came and went without any of the existing javascript-frameworks coming out as a clear winner. For a while, it looked liked sproutcore would get some steam with the gigantic carlhuda getting behind it, but now it looks like the whole project is in flux, with both technical (moving from 1.6 to 2.0 to amber.js [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=429</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>neo4j: Awesome! and not so awesome.</title>
		<link>http://www.vierundsechzig.de/blog/?p=417</link>
		<comments>http://www.vierundsechzig.de/blog/?p=417#comments</comments>
		<pubDate>Wed, 21 Dec 2011 18:38:33 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[neo4j]]></category>
		<category><![CDATA[nosql]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=417</guid>
		<description><![CDATA[__If you want to see how far we have come, you absolutely should look at this 10min-Video about integrating neo4j and google-docs. While it scratches only the surface of what neo4j can do, it impressively shows, where all this json-source here, json-consuming app there has lead us _: Of course, your average Excel-Sheet can meanwhile [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=417</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>fcbk.gobbles_up SC: What&#8217;s next for SproutCore?!</title>
		<link>http://www.vierundsechzig.de/blog/?p=408</link>
		<comments>http://www.vierundsechzig.de/blog/?p=408#comments</comments>
		<pubDate>Thu, 10 Nov 2011 08:24:35 +0000</pubDate>
		<dc:creator>stf</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[SproutCore]]></category>

		<guid isPermaLink="false">http://www.vierundsechzig.de/blog/?p=408</guid>
		<description><![CDATA[I had an article in the making about some adventures in backbone, backbone_rails and coffeescript and what is missing from backbone and what SproutCore already has, when the news hit me that Strobe, the company that backs up SC has sold out to facebook. What does that mean? Good news? Bad news? No change at [...]]]></description>
		<wfw:commentRss>http://www.vierundsechzig.de/blog/?feed=rss2&#038;p=408</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

