Hi Tim,

Thank you for the support.

With Redline you will be able to deploy Smalltalk to AWS Lambda 

Smalltalk source can be packaged into a STar (Smalltalk archive) which is 
actually a Java jar and deployed.

See jaws-maven-plugin for an approach to getting Java code deployed easily as a 
Lambda 

Sent from my Commodore 64

> On 30 Dec 2016, at 10:25 pm, Tim Mackinnon <tim@testit.works> wrote:
> 
> Actually I think James is on to something and we should try and support him.
> 
> Having recently played with AWS Lambda and written a few Alexa services in 
> JS,  I was intrigued how you would approach such end points in Smalltalk and 
> whether it would be a productive language and environment to run them in. 
> (Btw - the lambda environment is very interesting - scalable infrastructure 
> that is peanuts to run).
> 
> To try this, the basic building blocks provided by these services are either 
> JS or Java - so for Smalltalkers that sounds like Smalltalk running on Amber 
> or Redline.
> 
> I find Amber and all the JS infrastructure very daunting - gulp, amd etc. And 
> for Lambda you also get caught into this world of package management and 
> loading up JS dependencies.
> 
> I'm intrigued how a jvm Smalltalk might approach this problem (as well as 
> many others I'm sure). We seem to achieve a lot with quite a small image of 
> building blocks.
> 
> As pharo is a research community, can we help James explore this a bit more? 
> Certainly there is a drive to a minimal Smalltalk image - so that work can 
> immediately feed into this.
> 
> To add to the research'y side context - these service infrastructures seem to 
> feel a lot like callable blocks of code. We are used to thinking in this way 
> in our image - we use blocks everywhere. How might they run in a scaleable 
> environment vs straight function call languages?
> 
> Tim
> 
> Sent from my iPhone
> 
>> On 30 Dec 2016, at 09:31, Dimitris Chloupis <kilon.al...@gmail.com> wrote:
>> 
>> I think what most people would want is to use Java libraries from inside 
>> Pharo. You seem to want to bring Pharo classes to Redline Runtime .
>> 
>> I have the opposite idea of bringing Redline Runtime inside Pharo and give 
>> us Pharo developers an easy way to use Java libraries and mix pharo with 
>> java code. I think also Pharo would serve great as an IDE for Redline 
>> Smalltalk. 
>> 
>> I already have JNIPort thats does that but none will complain to have 
>> another tool around, I am sure it will come very handy. 
>> 
>>> On Fri, Dec 30, 2016 at 2:08 AM James Ladd <ladd.ja...@gmail.com> wrote:
>>> Hi Pharo People,
>>> 
>>> I have continued work on Redline Smalltalk and I'm wanting to discuss what
>>> the absolute minimum
>>> set of Classes and method should be included in the Redline Runtime.
>>> 
>>> Would anyone here like to participate in that discussion?
>>> 
>>> - James.
>>> Redline Smalltalk <http://redline.st>
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://forum.world.st/Redline-Talking-Runtime-basics-tp4928375.html
>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>>> 

Reply via email to