You can modify or fix any part of the system including basic "libraries" very easily and thanks to relativelly small, friendly and open community you can have as a single person greater influence on future Pharo development than in any other mentioned environment. Safer investition :-)
-- Pavel 2013/8/23 p...@highoctane.be <p...@highoctane.be>: > Hello, > > 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) > + STOMP > > + 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 > NSA-backdoor-enabled") > > 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). > > Phil
