PHP Fog ...

I reckon a Smalltalk-type Heroku/PHP Fog (http://techcrunch.com/2011/01/10/php-fog-raises-1-8-million-to-be-the-heroku-of-php) would be nice :)  Would there be a viable business opportunity there or is the market simply too small?

there's always EC2 and Gemstone: http://www.vimeo.com/18375790

Nick Ager wrote

there's always EC2 and Gemstone: http://www.vimeo.com/18375790

Yep, I reckon the screencast you made is great  ... but ... it's not quite the same though :)

About 6 months ago I shelved a project for doing Heroku-style
deployments from Pharo to Seaside. Perhaps I should dig out my backup
and pick it up. I thought I was the only one that might want this, and
I got caught up with some issues serializing and sending objects over
the network.

So that's my first question: what's the best way to serialize and send
an object over the network? Would it perhaps be better to just tell
the deployed image to use Monticello to update? Can Monticello roll
back in case of error (so it can be headless)?

-Steven

On Tue, Jan 11, 2011 at 6:36 AM, Geert Claes <[hidden email]> wrote:

Geert,

Even before we get into the sizing of market, we need to see if injecting Venture Capital into Pharo will do for the better or not...

--
Cesar Rabak


Em 11/01/2011 07:19, Geert Claes < [hidden email] > escreveu:

I reckon a Smalltalk-type Heroku/PHP Fog
(http://techcrunch.com/2011/01/10/php-fog-raises-1-8-million-to-be-the-heroku-of-php)
would be nice :)  Would there be a viable business opportunity there or is
the market simply too small?
--
View this message in context: http://forum.world.st/PHP-Fog-tp3208657p3208657.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

On Jan 11, 2011, at 5:57 PM, Steven Baker wrote:

> About 6 months ago I shelved a project for doing Heroku-style
> deployments from Pharo to Seaside. Perhaps I should dig out my backup
> and pick it up. I thought I was the only one that might want this, and
> I got caught up with some issues serializing and sending objects over
> the network.

I would love to see money raised for doing this kind of startup over pharo.


> So that's my first question: what's the best way to serialize and send
> an object over the network? Would it perhaps be better to just tell
> the deployed image to use Monticello to update? Can Monticello roll
> back in case of error (so it can be headless)?

not as far as I know.
Now I think that we are making progress to be able to load code in a separate environment
so we could really load everything in an environment and not install it in case of problem.
It just takes more times than expected.

Stef

On Tue, Jan 11, 2011 at 10:33 PM, Stéphane Ducasse
<[hidden email]> wrote:
>
> On Jan 11, 2011, at 5:57 PM, Steven Baker wrote:
>
>> About 6 months ago I shelved a project for doing Heroku-style
>> deployments from Pharo to Seaside. Perhaps I should dig out my backup
>> and pick it up. I thought I was the only one that might want this, and
>> I got caught up with some issues serializing and sending objects over
>> the network.
>

Please share your code :)
Heroku didn't get there in a day, and used lots of good tools provided
by the community. What we need now is those tools.

> I would love to see money raised for doing this kind of startup over pharo.
>

Let's find some million dollar projects only Pharo can solve :)

Stéphane Ducasse wrote

I would love to see money raised for doing this kind of startup over pharo.

I would love to get funding for a vision I've had for years now; a Smalltalk (Seaside, AIDA or Iliad based) Platform as a Service (intuitive online IDE, transparent version control, point-and-click deployment, shareable add-ons, ...) but I think it's still a little bit too early yet ... until then I'll keep tinkering away at the concept idea :)