next »

[Guillaume]

Seriously, it'd be the shit. I don't see it faring extremely well for complex 3d games (possibly a performance problem, and not sure how well GPU programming would play with smalltalk like programming), but for anything 2d based it'd rock.
Stuff to think about:

http://victorsavkin.com/post/16375110741/why-smalltalk
http://www.youtube.com/watch?v=PlI-gPu3SPI

[JMickle]

...what /is/ smalltalk? neither of those links really explained that to me.

[Guillaume]

It's a language from the 80's where everything is an object, objects communicate by passing objects to one another, and you develop in an environment where you edit your code as it is running and see the direct outcomes etc.

[JMickle]

i like live code editing.

[eigenbom]

I've never used smalltalk, and as far as live code editing goes, it's an awesome idea, but I think we're still a long way off .. Victor's app is a party trick, but a very cool one. The live-coding musicians are breaking some ground, but it's still so immature. Real-time manipulation of in-game data, hot-loading assets (such as scripts), etc., otoh, are totally doable, so I'd like to see more games use them. But I'd champion any one trying to do this! It might be better do it in Lua though ... just because I like it.

[yesfish]

Unity allows you to edit then reload scripts as the game's running... I bet you could modify other engines to do similar functionality

[Dacke]

I already rely on Hot Code Replacement when programming Java in Eclipse.

(But I don't have all the time-line, edit-future stuff that could be nice for a game)

[Polly]

.. and you develop in an environment where you edit your code as it is running and see the direct outcomes etc.

ZGameEditor does exactly that ( using C instead of smalltalk ) .. and not just code, you can add objects, import textures, switch shaders, modify sounds, link DLLs etc. while your project is running.

[ANtY]

This article was so fun to read  

What is interesting about Smalltalk
1. Smalltalk syntax
in Smalltalk:
service := WeatherForecastService forLocation: 'Toronto'.
forecast := service forecastForDays: 5 format: 'Xml'.

in Ruby:
service = WeatherForecastService.forLocation 'Toronto'
forecast = service.forecastForDaysInFormat(5, "xml")

service.forecastFor ->{puts "Do stuff"}, ->{puts "handling errors"}

The same code will look better in Smalltalk:
service forecastFor: [Transcript show: 'Do stuff'] error: [Transcript show: 'Error!'].

not sure if trolling or just pascal programmer

[Xienen]

This article was so fun to read  

What is interesting about Smalltalk
1. Smalltalk syntax
in Smalltalk:
service := WeatherForecastService forLocation: 'Toronto'.
forecast := service forecastForDays: 5 format: 'Xml'.

in Ruby:
service = WeatherForecastService.forLocation 'Toronto'
forecast = service.forecastForDaysInFormat(5, "xml")

service.forecastFor ->{puts "Do stuff"}, ->{puts "handling errors"}

The same code will look better in Smalltalk:
service forecastFor: [Transcript show: 'Do stuff'] error: [Transcript show: 'Error!'].

not sure if trolling or just pascal programmer

Haha, agreed! 

[Dacke]

The snippet above will print ‘true’ and you cannot do anything to change it in Ruby. But you can easily change this behavior for Smalltlak. If you want to ... treat an empty collection as ‘false’ just define ifTrue:ifFalse: method.

Redefining the basic language constructs as you go. Awesome idea. Totally results in readable and predictable code. Just look at how great operator overloading works out in C++

[ANtY]

I always do

Code:

#define and &&
#define or ||

in c++

but yeah, changing true to false isn't anything useful

[Dacke]

With great power comes great responsibility.

ANtY you are clearly a powerful, responsible and wise man

edit: also, operator overloading is to give existing operators new meanings. Which is a much darker witchcraft than simple #define-macros

[ANtY]

With great power comes great responsibility.

ANtY you are clearly a powerful, responsible and wise man

Finally someone noticed, I was wondering how long I'll have to wait 

[rogerlevy]

The snippet above will print ‘true’ and you cannot do anything to change it in Ruby. But you can easily change this behavior for Smalltlak. If you want to ... treat an empty collection as ‘false’ just define ifTrue:ifFalse: method.

Redefining the basic language constructs as you go. Awesome idea. Totally results in readable and predictable code. Just look at how great operator overloading works out in C++

This is the most retarded shit ever.  C++'s syntax is almost illegible as it is, so OF COURSE changing things up on people is just going to make it worse.