<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>Andrey Yatsyk</title>
 <link href="http://andrey.yatsyk.com/atom.xml" rel="self"/>
 <link href="http://andrey.yatsyk.com/"/>
 <updated>2010-06-08T08:17:54-04:00</updated>
 <id>http://andrey.yatsyk.com/</id>
 <author>
   <name>Andry Yatsyk</name>
   <email>yatsyk@gmail.com</email>
 </author>
 
 
 <entry>
   <title>Sun Buys MySQL</title>
   <link href="http://andrey.yatsyk.com/2008/01/21/sun-buys-mysql.html"/>
   <updated>2008-01-21T00:00:00-05:00</updated>
   <id>http://andrey.yatsyk.com/2008/01/21/sun-buys-mysql</id>
   <content type="html">&lt;h1&gt;Sun Buys MySQL&lt;/h1&gt;
&lt;p class=&quot;meta&quot;&gt;January 21st, 2008 &amp;#8211; Saint-Petersburg&lt;/p&gt;
&lt;p&gt;Sun is going to buy MySQL. Two years ago when Oracle tried to buy MySQL, Marten Mickos (MySQL &lt;span class=&quot;caps&quot;&gt;CEO&lt;/span&gt;) said &amp;#8216;We will be part of a larger company, but it will be called MySQL&amp;#8217;. Will we see Sun rebranding? :)&lt;/p&gt;</content>
 </entry>
 
 <entry>
   <title>Yahoo Pipes</title>
   <link href="http://andrey.yatsyk.com/2007/05/02/yahoo-pipes.html"/>
   <updated>2007-05-02T00:00:00-04:00</updated>
   <id>http://andrey.yatsyk.com/2007/05/02/yahoo-pipes</id>
   <content type="html">&lt;h1&gt;Yahoo Pipes&lt;/h1&gt;
&lt;p class=&quot;meta&quot;&gt;May 2, 2007 &amp;#8211; Saint-Petersburg&lt;/p&gt;
&lt;p&gt;Yahoo released &lt;a href=&quot;http://pipes.yahoo.com&quot;&gt;Pipes service&lt;/a&gt; few month ago. The aim of this project is to bring possibility of mashups creating to much broader audience. This service has a lot of coverage in different blogs such as &lt;a href=&quot;http://www.techcrunch.com/2007/02/07/yahoo-launches-pipes/&quot;&gt;techcrunch&lt;/a&gt;, &lt;a href=&quot;http://radar.oreilly.com/archives/2007/02/pipes_and_filte.html&quot;&gt;oreilly radar &lt;/a&gt; and &lt;a href=&quot;http://www.google.com/search?hl=en&amp;q=yahoo+pipes&amp;btnG=Search&quot;&gt; much more&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There is &lt;a href=&quot;http://video.google.com/videoplay?docid=8569811679113799879&quot;&gt;video&lt;/a&gt; with pipe developers on google video.&lt;/p&gt;
&lt;p&gt;I would like to summarize some thoughts about pips in this post.&lt;/p&gt;
&lt;p&gt;What I would like to have in pipes is some high-level language that could be used simultaneously with &lt;span class=&quot;caps&quot;&gt;GUI&lt;/span&gt; constructor. It would be great if Pipes behave same way as &lt;span class=&quot;caps&quot;&gt;UML&lt;/span&gt; tools that could export java code(or code on other mainstream language) and if we change java code all changes incorporated into diagram. Creating such tool for general programming language is quite hard task but I don&amp;#8217;t think that it would be very hard for &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; with very limited syntax. I suppose that Pipes team already has some kind of language in their backend.&lt;/p&gt;
&lt;p&gt;With such &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; we could: &lt;br /&gt;
&lt;ul&gt;&lt;br /&gt;
&lt;li&gt;Send code fragments or entire pipes by mail or by post it to discussion groups (as  pipes created  for amateurs it is especially important to have ways ask questions in discussion groups). &lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Diagrams definitely looks cool but how can I quickly see what is different in two version of pipe. With text representation any diff utility could be used.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;I would like to store pipe in repository and return to any previous version if I need. With &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; there is no problem but now it is impossible. &lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;span class=&quot;caps&quot;&gt;GUI&lt;/span&gt; editor is impressive web application but in some cases it is not convenient.  For example lot of pipes contains parameters like this: &lt;img src=&quot;http://andrey.yatsyk.com/wp-content/uploads/2007/05/pipes_edit_field.PNG&quot; alt=&quot;pipes edit field&quot;/&gt; . We see only a few symbols from in field. &lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;
&lt;p&gt;For me the most killer feature of Pipes is possibility to export pipe result in json format. This is very cool and I think that we will see a lot of new light-weight mashups.  What very frequently stops me from creating some small and cool mashup is that I need to create database, write server side code not forgetting about caching, potential sql injections and all that not so funny stuff. Server side applications always try to stop working after hosting upgrades :).  With pipes small mashups could be created much more easily. Mash data on pipes server and use results in client side &lt;span class=&quot;caps&quot;&gt;AJAX&lt;/span&gt; application that consist from static javascript and html files.&lt;/p&gt;
&lt;p&gt;Pipes is actively developing project and new features adding. Especially nice that new sources of data appearing.&lt;/p&gt;</content>
 </entry>
 
 
</feed>