[Pharo-dev] The Pharo Advantage: what is it for you?

phil at highoctane.be phil at highoctane.be
Fri Aug 23 04:32:30 EDT 2013


As part of the defense of a budget and technology choices, what would you
guys list as a key advantage of using Pharo for creating software solutions?

My current stack is:

Pharo 2.0
Seaside 3 (including Seaside-REST)
Magritte 3
Twitter Bootstrap

+ a couple of data storage stuff (DBXTalk, Phriak, Voyage)

+ Amber if needed

I've been test driving the whole stack for a while and even if there are
some quirks, it looks like good enough for what I want to achieve.

Now, my question: what is the Pharo advantage you would put forward vs
other choices (like LAMP, Java, Rails etc).

I am aware of what those could be but I am more looking for what makes you
tick when using the technology (like: "it is fun to work with", "no more
Java for me, due to ...", "speeds dev time by ...", "not

This is the kind of thing we should have in stock for helping the
Consortium members get buy in from people giving a yes on budgets.

Thanks in advance for your help! (BTW, I am going to use this on monday
morning for defending our position on a significant project).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130823/ca30d148/attachment-0002.html>

More information about the Pharo-dev mailing list