New S# Language - Smalltalk for .Net

curador writes "In an interview with David Simmons, CTO of SmallScript Corp., we learned about a new .NET language about to debut...." I was surfing around and found this article and had not noticed it on /. yet so start your flame engines please!"

Comments

Good for Smalltalk users

[SteveX]

I never really "got" Smalltalk but the folks that do love it. One of the cool things about the .NET framework is that being language neutral, your choice of language doesn't have to be based on what toolkits and libraries and whatnot are available to it.

So Smalltalk programmers, through S#, will be able to talk to DirectX or Gtk# or MySQL or whatever without someone having to come up with bindings or libraries or whatever they might otherwise need. Scary. :)

- Steve

Re:Good for Smalltalk users

[Anonymous Coward]

It's language neutral so long as your language is a garbage collected, single inheritance, single dispatch 00 language. Otherwise, your language becomes "C# with a thin veneer of another languages syntax".

Common Lisp on .NET, for example, while possible, would be heinously inefficient, not properly integrable with the crippled Object model (compared to CLOS's multi-dispatch, multi-inheritance model), and all in all pretty pointless.

Smalltalk with Multiple Inheritance?

[werdna]

Seems like an ideological shift to me, more closely related to C++ than to Smalltalk

Re:Nothing to flame

[Raiford]

The best and the brightest will use the language and the environment that is best suited for the task. Nobody is going to write a device driver in VB and no one should waste time is going to writing some simple gui front in for an ODBC connection to an Acess DB in ANSI C.