<?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"
	>
<channel>
	<title>Comments on: The spreadsheet disadvantage</title>
	<atom:link href="http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/feed/" rel="self" type="application/rss+xml" />
	<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/</link>
	<description>Simon Murphy on professional spreadsheet development stuff</description>
	<pubDate>Fri, 08 Aug 2008 19:51:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Chris Whitfield</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-5799</link>
		<dc:creator>Chris Whitfield</dc:creator>
		<pubDate>Thu, 23 Aug 2007 17:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-5799</guid>
		<description>I'm an old lag, I confess it, and even worse, a computer techie by training not an accountant.  I can just about accept the rationale for multipage workbooks and "canned" facilities like optimisation, pivot tables and the like as they, and the ready availability of functions to perform all sorts of tricky numerical computations, can save vast amounts of work and time.
The problem is that integrating a fairly low-level programming language (Basic) is simply an invitation to use the combination for things to which it is totally unsuited and extremely error prone.
All this was gone through years ago with notably assembly code and Fortran and the hard lessons learned.  It does not follow simply because it is easy to prototype an application quickly with a tool like Excel that it is suitable for the development of error-free production code.</description>
		<content:encoded><![CDATA[<p>I&#8217;m an old lag, I confess it, and even worse, a computer techie by training not an accountant.  I can just about accept the rationale for multipage workbooks and &#8220;canned&#8221; facilities like optimisation, pivot tables and the like as they, and the ready availability of functions to perform all sorts of tricky numerical computations, can save vast amounts of work and time.<br />
The problem is that integrating a fairly low-level programming language (Basic) is simply an invitation to use the combination for things to which it is totally unsuited and extremely error prone.<br />
All this was gone through years ago with notably assembly code and Fortran and the hard lessons learned.  It does not follow simply because it is easy to prototype an application quickly with a tool like Excel that it is suitable for the development of error-free production code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-431</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Tue, 20 Mar 2007 09:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-431</guid>
		<description>Intresting stuff. Not sure a aggree with all of it! ;-)

I'll only say one thing, I wrote a big dictor app - a modeling tool - a while back, it was "fun" but i dont think i would really undertake it agian. getting the UI to function (i used workbook sheets as the UI) was a pain, and not really good enough - maybe UF might have been better? But i think i'd look to do this in  .Net or VB6 now, probally .Net to be fair.</description>
		<content:encoded><![CDATA[<p>Intresting stuff. Not sure a aggree with all of it! ;-)</p>
<p>I&#8217;ll only say one thing, I wrote a big dictor app - a modeling tool - a while back, it was &#8220;fun&#8221; but i dont think i would really undertake it agian. getting the UI to function (i used workbook sheets as the UI) was a pain, and not really good enough - maybe UF might have been better? But i think i&#8217;d look to do this in  .Net or VB6 now, probally .Net to be fair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harlan Grove</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-424</link>
		<dc:creator>Harlan Grove</dc:creator>
		<pubDate>Tue, 20 Mar 2007 03:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-424</guid>
		<description>Excel services? So you can treat multimegabyte spreadsheets as black boxes rather than write efficient code to do the same thing? Gosh, that get's my juices flowing!

Excel is screwy enough as a mixture of UI and functional programming language, but mixing the two at least provides immediate gratification in terms of recalculation upon entry. Take away the UI, and you're left with the world's least efficient functional programming language. The only justification I've heard is that, "well, there's all these spreadsheets out there already." Fine. Use *EXISTING* spreadsheets with Excel services. Any developer suggesting using Excel services with *NEW* spreadsheet models should be fired on the spot.</description>
		<content:encoded><![CDATA[<p>Excel services? So you can treat multimegabyte spreadsheets as black boxes rather than write efficient code to do the same thing? Gosh, that get&#8217;s my juices flowing!</p>
<p>Excel is screwy enough as a mixture of UI and functional programming language, but mixing the two at least provides immediate gratification in terms of recalculation upon entry. Take away the UI, and you&#8217;re left with the world&#8217;s least efficient functional programming language. The only justification I&#8217;ve heard is that, &#8220;well, there&#8217;s all these spreadsheets out there already.&#8221; Fine. Use *EXISTING* spreadsheets with Excel services. Any developer suggesting using Excel services with *NEW* spreadsheet models should be fired on the spot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-421</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 20 Mar 2007 03:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-421</guid>
		<description>Jim has an excellent explanation on MVC here:
http://moverve.com/blog/2007/03/separation-of-data-and-view/
I should have tried harder, but now I dont have to - Thanks Jim! 
Cheers
Simon</description>
		<content:encoded><![CDATA[<p>Jim has an excellent explanation on MVC here:<br />
<a href="http://moverve.com/blog/2007/03/separation-of-data-and-view/" rel="nofollow">http://moverve.com/blog/2007/03/separation-of-data-and-view/</a><br />
I should have tried harder, but now I dont have to - Thanks Jim!<br />
Cheers<br />
Simon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-408</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Tue, 20 Mar 2007 00:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-408</guid>
		<description>Office Web Components were very good, ruined by licencing I'd say. (they were really OIC - Office Intranet C..) There is no 2007 version so they are a bit of a dead end now I think. (as you said Dennis)

Re VSTO - I personally like working with this stuff, but really who are the customers? Most Office devs prefer the simplicity of VBA, most VS devs only want to do web apps. Where is the demand for .net/Office solutions going to come from? There seems to be strong demand for .net grid controls, judging by the variety available.

I don't know of any corporate dev depts that would touch Excel. Its end user driven all the way in my experience. Maybe MS have seen something I've missed.
Maybe Excel services will get those corp devs interested?</description>
		<content:encoded><![CDATA[<p>Office Web Components were very good, ruined by licencing I&#8217;d say. (they were really OIC - Office Intranet C..) There is no 2007 version so they are a bit of a dead end now I think. (as you said Dennis)</p>
<p>Re VSTO - I personally like working with this stuff, but really who are the customers? Most Office devs prefer the simplicity of VBA, most VS devs only want to do web apps. Where is the demand for .net/Office solutions going to come from? There seems to be strong demand for .net grid controls, judging by the variety available.</p>
<p>I don&#8217;t know of any corporate dev depts that would touch Excel. Its end user driven all the way in my experience. Maybe MS have seen something I&#8217;ve missed.<br />
Maybe Excel services will get those corp devs interested?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harlan Grove</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-404</link>
		<dc:creator>Harlan Grove</dc:creator>
		<pubDate>Mon, 19 Mar 2007 23:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-404</guid>
		<description>Answers to questions may become obvious, but the questions don't become obsolete. Looks like there's an assumption that those corporate development departments were already doing most of their development work in Excel. Not where I work.</description>
		<content:encoded><![CDATA[<p>Answers to questions may become obvious, but the questions don&#8217;t become obsolete. Looks like there&#8217;s an assumption that those corporate development departments were already doing most of their development work in Excel. Not where I work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Wallentin</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-393</link>
		<dc:creator>Dennis Wallentin</dc:creator>
		<pubDate>Mon, 19 Mar 2007 18:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-393</guid>
		<description>Simon, Harlan et al,

&#62;&#62;is it really appropriate for spreadsheets?

When large corporates port themselves to .NET and their developing department(s) are requested to use .NET then the question is quite obsolete. 

Marcus,
OWC is a really underestimated package but keep in mind that MSFT made it totally wrong when they released the first version (9.0) with their license setup. Except for that MSFT has never pushed for the OWC package and now they don't develop it further.

Kind regards,
Dennis</description>
		<content:encoded><![CDATA[<p>Simon, Harlan et al,</p>
<p>&gt;&gt;is it really appropriate for spreadsheets?</p>
<p>When large corporates port themselves to .NET and their developing department(s) are requested to use .NET then the question is quite obsolete. </p>
<p>Marcus,<br />
OWC is a really underestimated package but keep in mind that MSFT made it totally wrong when they released the first version (9.0) with their license setup. Except for that MSFT has never pushed for the OWC package and now they don&#8217;t develop it further.</p>
<p>Kind regards,<br />
Dennis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-392</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 19 Mar 2007 17:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-392</guid>
		<description>Marcus - Mickey Mouse is spot on, that is exactly the attitude. On the plus side though I think that is why sys admins don't bother locking down VBA.
I think Excel is one of the biggest (most properties/methods) COM components around?
Eek-a-cell - I don't like any long formulas, but ones that dont do anything would be even more unwelcome.</description>
		<content:encoded><![CDATA[<p>Marcus - Mickey Mouse is spot on, that is exactly the attitude. On the plus side though I think that is why sys admins don&#8217;t bother locking down VBA.<br />
I think Excel is one of the biggest (most properties/methods) COM components around?<br />
Eek-a-cell - I don&#8217;t like any long formulas, but ones that dont do anything would be even more unwelcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EEK-A-CELL</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-390</link>
		<dc:creator>EEK-A-CELL</dc:creator>
		<pubDate>Mon, 19 Mar 2007 15:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-390</guid>
		<description>Two things piss me off 

1.	Authors that say; Only the most trivial spreadsheets don’t use arrays.
2.	Really really really looooooong conditional formulas that really don’t do much! And waste your time learning in then first place.</description>
		<content:encoded><![CDATA[<p>Two things piss me off </p>
<p>1.	Authors that say; Only the most trivial spreadsheets don’t use arrays.<br />
2.	Really really really looooooong conditional formulas that really don’t do much! And waste your time learning in then first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus</title>
		<link>http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-386</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Sun, 18 Mar 2007 21:41:30 +0000</pubDate>
		<guid isPermaLink="false">http://smurfonspreadsheets.wordpress.com/2007/03/16/the-spreadsheet-disadvantage/#comment-386</guid>
		<description>Hi Simon,

"he'd rather write from scratch"
I think that some of this comes from two sources:

1. Perception: MSO dev is Mickey Mouse and couldn't do what I need; and

2. Ignorance: You mean I could have done this with the OWC Grid control?

The OWC (OFfice Web Components) are very under-rated. Having 'OFfice' in the name seems to devalue them in some peoples' eyes.

"client as rich as Excel"
I've had 'real' developers ask if I've ever worked with COM without realising that Excel is one big COM object with a rich hierarchy of objects, properties and methods as you're going to get.</description>
		<content:encoded><![CDATA[<p>Hi Simon,</p>
<p>&#8220;he&#8217;d rather write from scratch&#8221;<br />
I think that some of this comes from two sources:</p>
<p>1. Perception: MSO dev is Mickey Mouse and couldn&#8217;t do what I need; and</p>
<p>2. Ignorance: You mean I could have done this with the OWC Grid control?</p>
<p>The OWC (OFfice Web Components) are very under-rated. Having &#8216;OFfice&#8217; in the name seems to devalue them in some peoples&#8217; eyes.</p>
<p>&#8220;client as rich as Excel&#8221;<br />
I&#8217;ve had &#8216;real&#8217; developers ask if I&#8217;ve ever worked with COM without realising that Excel is one big COM object with a rich hierarchy of objects, properties and methods as you&#8217;re going to get.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
