<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Smalltalk Reloaded: Missing Bits &#038; The Achilles Heel</title>
	<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/</link>
	<description>Community and Code for Squeak Smalltalkers</description>
	<pubDate>Sat, 17 May 2008 09:45:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: John</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-241</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 03 Feb 2008 15:37:21 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-241</guid>
		<description>I agree that there should be a high degree of integration between the different builds/frameworks.  Fragmentation is not productive.

I can see that ST companies might have missed an opportunity, but Sun was a BIG presence in the dot-com era and was in a position to effectively support and promote Java (including adding networking).

It seems to me that the next major opportunity, and maybe a more serious failing by ST companies, was web development tools/framework as captured by Ruby/Rails. We are only now seeing effective commercial offerings like GLASS from Gemstone.

Clearly successful business models can be based on open source software.  Commercial ST vendors don't seem to have fully embraced the potential of that business model.  This is unfortunate because part of what OSS-commercial vendors sell is access to innovation and ST is a great environment for innovation.   

In addition to providing better tools for professionals, commercial ST vendors could help to promote ST/Squeak as an educational platform for kids/teens.  Funding some kind of educational coordinator/evangelist would be a big help.  ST/Squeak already has some traction in this area.  Kids can be surprisingly innovative and once they start on traditional programming education with procedural languages it becomes MUCH more difficult to attract them to ST.</description>
		<content:encoded><![CDATA[<p>I agree that there should be a high degree of integration between the different builds/frameworks.  Fragmentation is not productive.</p>
<p>I can see that ST companies might have missed an opportunity, but Sun was a BIG presence in the dot-com era and was in a position to effectively support and promote Java (including adding networking).</p>
<p>It seems to me that the next major opportunity, and maybe a more serious failing by ST companies, was web development tools/framework as captured by Ruby/Rails. We are only now seeing effective commercial offerings like GLASS from Gemstone.</p>
<p>Clearly successful business models can be based on open source software.  Commercial ST vendors don&#8217;t seem to have fully embraced the potential of that business model.  This is unfortunate because part of what OSS-commercial vendors sell is access to innovation and ST is a great environment for innovation.   </p>
<p>In addition to providing better tools for professionals, commercial ST vendors could help to promote ST/Squeak as an educational platform for kids/teens.  Funding some kind of educational coordinator/evangelist would be a big help.  ST/Squeak already has some traction in this area.  Kids can be surprisingly innovative and once they start on traditional programming education with procedural languages it becomes MUCH more difficult to attract them to ST.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-231</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sat, 02 Feb 2008 00:09:53 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-231</guid>
		<description>@Patrick
I agree. But thinking back on those days in the Smalltalk community there was a real “corporate” feel to Smalltalk. Squeak was not really out yet, everything was VW and Digitalk… multi $K USD products because they thought they were going to save IT from itself and make some scratch at the same time.

There was the big corp pull but Digitalk still had the independents who had bought at $99 - my company happened to be located a few floors up from Digitalk in the early days and I went downstairs and handed Jim Anderson a check - it didn't feel so corporate then.

"Back in those days “web” and “corporate” were two different things."
true

"As I understand it, Sun went to ParcPlace to get VW Smalltalk to be the “Oak” language for “Set Top Boxes” and such (remember, this was before Java was targeted at the web. Everyone was all about “Set Top Boxes”.) Apparently PP wanted to license it for more than an arm and a leg, and the rest is history. This is anecdotal but heard from more than one source."
I'd heard this too and always felt it was at least somewhat accurate</description>
		<content:encoded><![CDATA[<p>@Patrick<br />
I agree. But thinking back on those days in the Smalltalk community there was a real “corporate” feel to Smalltalk. Squeak was not really out yet, everything was VW and Digitalk… multi $K USD products because they thought they were going to save IT from itself and make some scratch at the same time.</p>
<p>There was the big corp pull but Digitalk still had the independents who had bought at $99 - my company happened to be located a few floors up from Digitalk in the early days and I went downstairs and handed Jim Anderson a check - it didn&#8217;t feel so corporate then.</p>
<p>&#8220;Back in those days “web” and “corporate” were two different things.&#8221;<br />
true</p>
<p>&#8220;As I understand it, Sun went to ParcPlace to get VW Smalltalk to be the “Oak” language for “Set Top Boxes” and such (remember, this was before Java was targeted at the web. Everyone was all about “Set Top Boxes”.) Apparently PP wanted to license it for more than an arm and a leg, and the rest is history. This is anecdotal but heard from more than one source.&#8221;<br />
I&#8217;d heard this too and always felt it was at least somewhat accurate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-230</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sat, 02 Feb 2008 00:03:26 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-230</guid>
		<description>“I guess I’m corrupted by Emacs. ”
well since you said it :-) ... 
somewhere in the late 80's I got a Mac with 2 19in monitors(late 80's I think) and was doing a bunch of work in Smalltalk and Macromedia Director - that's when screen real estate came home to me ... using keyboard macros and commands are great supplements for me, but wetware is primary</description>
		<content:encoded><![CDATA[<p>“I guess I’m corrupted by Emacs. ”<br />
well since you said it <img src='http://squeak.funkencode.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> &#8230;<br />
somewhere in the late 80&#8217;s I got a Mac with 2 19in monitors(late 80&#8217;s I think) and was doing a bunch of work in Smalltalk and Macromedia Director - that&#8217;s when screen real estate came home to me &#8230; using keyboard macros and commands are great supplements for me, but wetware is primary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-229</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Fri, 01 Feb 2008 23:49:56 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-229</guid>
		<description>@Jonathan - my pleasure! Flipping back thru your book was fun!</description>
		<content:encoded><![CDATA[<p>@Jonathan - my pleasure! Flipping back thru your book was fun!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-228</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Fri, 01 Feb 2008 23:47:04 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-228</guid>
		<description>@John Isn’t Seaside a framework and not an “incompatible build?” 
well maybe in theory, but last I checked(probably fall) Seaside was running on Squeak 3.7 while Croquet, Sophie are Squeakland 3.8 but with different images and/or VMs - they don't work together out of the box and there's no guide or tool for integrating them other than a very big hammer. Don't mean to sound too cynical - I'm really not, it's just that peole keep tossing out ideas that people very reasonably(as in your case) take at face value. 

@Before the internet took off, networking was secondary.
True, but there were several commercial Smalltalks that had every opportunity to jump on the bandwagon before Java ever got on the scene. 

@It seems to me that ST’s business case is “making the difficult easy, and impossible possible”. The complexity of the solutions that programmers tackle keeps increasing. (Is there a law for this yet?) FORTRAN and COBOL were tools for fast computations and accounting with well defined inputs and outputs. Then C and soon C++/Java took over and allowed more complex systems to be modeled. ST has been head of its time.

If you check my other posts, you'll see that's not how it happened. ST did make the business case you mention in the late 80's early 90's and had clearly beaten C/C++ mindshare wise before Java ever arrived. IBM had blessed it and during that era $99 was like open source so a growing community of individuals had gathered around Digitalk as well. I agree that the commercial entities should support Squeak and GNU ST better.</description>
		<content:encoded><![CDATA[<p>@John Isn’t Seaside a framework and not an “incompatible build?”<br />
well maybe in theory, but last I checked(probably fall) Seaside was running on Squeak 3.7 while Croquet, Sophie are Squeakland 3.8 but with different images and/or VMs - they don&#8217;t work together out of the box and there&#8217;s no guide or tool for integrating them other than a very big hammer. Don&#8217;t mean to sound too cynical - I&#8217;m really not, it&#8217;s just that peole keep tossing out ideas that people very reasonably(as in your case) take at face value. </p>
<p>@Before the internet took off, networking was secondary.<br />
True, but there were several commercial Smalltalks that had every opportunity to jump on the bandwagon before Java ever got on the scene. </p>
<p>@It seems to me that ST’s business case is “making the difficult easy, and impossible possible”. The complexity of the solutions that programmers tackle keeps increasing. (Is there a law for this yet?) FORTRAN and COBOL were tools for fast computations and accounting with well defined inputs and outputs. Then C and soon C++/Java took over and allowed more complex systems to be modeled. ST has been head of its time.</p>
<p>If you check my other posts, you&#8217;ll see that&#8217;s not how it happened. ST did make the business case you mention in the late 80&#8217;s early 90&#8217;s and had clearly beaten C/C++ mindshare wise before Java ever arrived. IBM had blessed it and during that era $99 was like open source so a growing community of individuals had gathered around Digitalk as well. I agree that the commercial entities should support Squeak and GNU ST better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Pletzke</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-227</link>
		<dc:creator>Jonathan Pletzke</dc:creator>
		<pubDate>Fri, 01 Feb 2008 19:34:48 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-227</guid>
		<description>Thanks for taking me back in time to the good ole days. Dave Simmons was my Smalltalk mentor, and he is a very sharp guy.</description>
		<content:encoded><![CDATA[<p>Thanks for taking me back in time to the good ole days. Dave Simmons was my Smalltalk mentor, and he is a very sharp guy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-226</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 01 Feb 2008 17:43:46 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-226</guid>
		<description>Aren't the "multiple builds" supposed to be a strength?  (relative ease of creating Domain Specific Languages)  Isn't Seaside a framework and not an "incompatible build?"  I'm not that familiar with the others but why wouldn't they also be considered frameworks?

Tech history seems to prove that incremental progress is valued over paradigm shifts.  With "write once, run everywhere" Java offered to solve a real problem for developers and was innovative without being too different from what past procedural programmers were used to.  Before the internet took off, networking was secondary.

It seems to me that ST's business case is "making the difficult easy, and impossible possible".  The complexity of the solutions that programmers tackle keeps increasing.  (Is there a law for this yet?)  FORTRAN and COBOL were tools for fast computations and accounting with well defined inputs and outputs.  Then C and soon C++/Java took over and allowed more complex systems to be modeled.  ST has been head of its time.

This is somewhat borne out by some Java developers recent complaints about how bloated it is.  Clearly, Java tries to be everything to everyone and there are Java efforts to incorporate Ruby and Rails frameworks (JRuby, Groovy, etc.)  

It's hard for any non-mainstream language to succeed.  (Remember the complaints that Java was dog slow? and the endless "but we can do this in C++" demonstrations?) Java had the enduring support of Sun but its success was never a given.  IMO Commercial ST vendors should support Squeak (better) so that they can take advantage of innovations like Seaside.  (Surprisingly, they seem to be late to incorporate Seaside.)</description>
		<content:encoded><![CDATA[<p>Aren&#8217;t the &#8220;multiple builds&#8221; supposed to be a strength?  (relative ease of creating Domain Specific Languages)  Isn&#8217;t Seaside a framework and not an &#8220;incompatible build?&#8221;  I&#8217;m not that familiar with the others but why wouldn&#8217;t they also be considered frameworks?</p>
<p>Tech history seems to prove that incremental progress is valued over paradigm shifts.  With &#8220;write once, run everywhere&#8221; Java offered to solve a real problem for developers and was innovative without being too different from what past procedural programmers were used to.  Before the internet took off, networking was secondary.</p>
<p>It seems to me that ST&#8217;s business case is &#8220;making the difficult easy, and impossible possible&#8221;.  The complexity of the solutions that programmers tackle keeps increasing.  (Is there a law for this yet?)  FORTRAN and COBOL were tools for fast computations and accounting with well defined inputs and outputs.  Then C and soon C++/Java took over and allowed more complex systems to be modeled.  ST has been head of its time.</p>
<p>This is somewhat borne out by some Java developers recent complaints about how bloated it is.  Clearly, Java tries to be everything to everyone and there are Java efforts to incorporate Ruby and Rails frameworks (JRuby, Groovy, etc.)  </p>
<p>It&#8217;s hard for any non-mainstream language to succeed.  (Remember the complaints that Java was dog slow? and the endless &#8220;but we can do this in C++&#8221; demonstrations?) Java had the enduring support of Sun but its success was never a given.  IMO Commercial ST vendors should support Squeak (better) so that they can take advantage of innovations like Seaside.  (Surprisingly, they seem to be late to incorporate Seaside.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Logan</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-225</link>
		<dc:creator>Patrick Logan</dc:creator>
		<pubDate>Thu, 31 Jan 2008 20:20:18 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-225</guid>
		<description>"And so Emacs is my Window manager..."

Emacs will likely always be my window manager when not in a Smalltalk environment. And when I worked for Gemstone, Emacs *was* my Smalltalk environment. Kind of nice there too.

"my real point is that Smalltalk community didn’t strike the web while the iron was hot - before Java showed up and got traction."

I agree. But thinking back on those days in the Smalltalk community there was a real "corporate" feel to Smalltalk. Squeak was not really out yet, everything was VW and Digitalk... multi $K USD products because they thought they were going to save IT from itself and make some scratch at the same time.

Back in those days "web" and "corporate" were two different things.

As I understand it, Sun went to ParcPlace to get VW Smalltalk to be the "Oak" language for "Set Top Boxes" and such (remember, this was before Java was targeted at the web. Everyone was all about "Set Top Boxes".) Apparently PP wanted to license it for more than an arm and a leg, and the rest is history. This is anecdotal but heard from more than one source.</description>
		<content:encoded><![CDATA[<p>&#8220;And so Emacs is my Window manager&#8230;&#8221;</p>
<p>Emacs will likely always be my window manager when not in a Smalltalk environment. And when I worked for Gemstone, Emacs *was* my Smalltalk environment. Kind of nice there too.</p>
<p>&#8220;my real point is that Smalltalk community didn’t strike the web while the iron was hot - before Java showed up and got traction.&#8221;</p>
<p>I agree. But thinking back on those days in the Smalltalk community there was a real &#8220;corporate&#8221; feel to Smalltalk. Squeak was not really out yet, everything was VW and Digitalk&#8230; multi $K USD products because they thought they were going to save IT from itself and make some scratch at the same time.</p>
<p>Back in those days &#8220;web&#8221; and &#8220;corporate&#8221; were two different things.</p>
<p>As I understand it, Sun went to ParcPlace to get VW Smalltalk to be the &#8220;Oak&#8221; language for &#8220;Set Top Boxes&#8221; and such (remember, this was before Java was targeted at the web. Everyone was all about &#8220;Set Top Boxes&#8221;.) Apparently PP wanted to license it for more than an arm and a leg, and the rest is history. This is anecdotal but heard from more than one source.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Friedrich</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-224</link>
		<dc:creator>Friedrich</dc:creator>
		<pubDate>Thu, 31 Jan 2008 17:32:04 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-224</guid>
		<description>I'm subscribe to the squeak list but have overread that. But some pointed it out very clear. You do not have  a broader picture of your sources and in fact  you do no have something which resembles an outline. I guess I'm corrupted by Emacs. Which all in all is a pleasat too for handling text (in whatever forms they come along) ;-) And so Emacs is my Window manager, I can not see why it should not be Smalltalk, but I'm reall not keen making it that "comfortable" to me as I'm used to in Emacs (well a few decaded of editor development is really a tough job ;-)

Regards
Friedrich</description>
		<content:encoded><![CDATA[<p>I&#8217;m subscribe to the squeak list but have overread that. But some pointed it out very clear. You do not have  a broader picture of your sources and in fact  you do no have something which resembles an outline. I guess I&#8217;m corrupted by Emacs. Which all in all is a pleasat too for handling text (in whatever forms they come along) <img src='http://squeak.funkencode.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> And so Emacs is my Window manager, I can not see why it should not be Smalltalk, but I&#8217;m reall not keen making it that &#8220;comfortable&#8221; to me as I&#8217;m used to in Emacs (well a few decaded of editor development is really a tough job <img src='http://squeak.funkencode.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Regards<br />
Friedrich</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-222</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Thu, 31 Jan 2008 15:59:09 +0000</pubDate>
		<guid>http://squeak.funkencode.com/2008/01/29/smalltalk-reloaded-missing-bits-the-achilles-heel/#comment-222</guid>
		<description>Friedrich - there's a conversation going on at the Squeak-dev list entitled  Editing class method sources in single place ... you'd probably find it interesting ... I don't use Whisker or Star or OmniBrowser but thought they might convey the idea that the tools are malleable. I think though that it helps to &lt;a href="http://croquet.funkencode.com/2008/01/31/story-oriented-coding/" rel="nofollow"&gt;broaden the context&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Friedrich - there&#8217;s a conversation going on at the Squeak-dev list entitled  Editing class method sources in single place &#8230; you&#8217;d probably find it interesting &#8230; I don&#8217;t use Whisker or Star or OmniBrowser but thought they might convey the idea that the tools are malleable. I think though that it helps to <a href="http://croquet.funkencode.com/2008/01/31/story-oriented-coding/" rel="nofollow">broaden the context</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
