<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>bbgm - the discussion - Latest Comments in Another wish for life science APIs and web services</title><link>http://mndoci.disqus.com/</link><description>At the interface of science and computing</description><atom:link href="https://mndoci.disqus.com/another_wish_for_life_science_apis_and_web_services/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 20 May 2008 10:24:20 -0000</lastBuildDate><item><title>Re: Another wish for life science APIs and web services</title><link>http://mndoci.com/blog/2008/05/18/another-wish-for-life-science-apis-and-web-services/#comment-496135</link><description>&lt;p&gt;That's worth a rant in itself.  Funding models are critical to take the capital costs and hardware maintenance issues out of the picture.  The other issue is a more fundamental one and it's why I don't think academics should keep software locked up (even it if is open source in theory), but make it available via sourceforge, google code, etc.  Still doesn't solve the problem, but it's a start.&lt;/p&gt;&lt;p&gt;Thing is, most academic software is badly written (I've worked with enough to know by now), so what's the solution?  People don't want to pay for software, and web services are not something you can download and deploy most of the time.  Is the solution to hire young programmers?  The turnover rate will be too high.&lt;/p&gt;&lt;p&gt;Or perhaps informatics types will learn REAL software engineering.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mndoci</dc:creator><pubDate>Tue, 20 May 2008 10:24:20 -0000</pubDate></item><item><title>Re: Another wish for life science APIs and web services</title><link>http://mndoci.com/blog/2008/05/18/another-wish-for-life-science-apis-and-web-services/#comment-495715</link><description>&lt;p&gt;What’s keeping academics from setting up servers on the cloud other than funding models?&lt;br&gt;I dont think the cloud is the answer to having software work well on the web. It all maintenance. Most academic projects run out of funding , or the grad student/postdoc maintainer leaves the lab. &lt;br&gt;As a result you have broken web pages and stalled web jobs!&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">harijay</dc:creator><pubDate>Tue, 20 May 2008 09:06:19 -0000</pubDate></item><item><title>Re: Another wish for life science APIs and web services</title><link>http://mndoci.com/blog/2008/05/18/another-wish-for-life-science-apis-and-web-services/#comment-486960</link><description>&lt;p&gt;Egon,&lt;/p&gt;&lt;p&gt;I agree.  Basically the point is that we should use commonly available mechanisms to distribute code, rather than put them into this ether.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mndoci</dc:creator><pubDate>Sun, 18 May 2008 15:16:28 -0000</pubDate></item><item><title>Re: Another wish for life science APIs and web services</title><link>http://mndoci.com/blog/2008/05/18/another-wish-for-life-science-apis-and-web-services/#comment-486775</link><description>&lt;p&gt;Regarding the source code repository, I think Linux distributions provide good options here. Ensuring that your software is available in the Debian/RedHat/etc repository provides an excellent way to ensure your software is available, portable, easy to install etc. I strongly recommend this to any open source science project.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Egon Willighagen</dc:creator><pubDate>Sun, 18 May 2008 14:23:26 -0000</pubDate></item></channel></rss>