Another way of promoting Pharo is copying its advantages to other languages. The ideal way is for people to get straight to Pharo and fall in love with it. But sometimes this may be possible for several reasons. The most usual being that people simple are not in the mood of learning a new language unless they have to. As the saying goes "People love progress , its just that they equally hate change"
Introducing similar features to another language, like I did with introducing live coding enviroment to Python with direct reference back to Pharo is a very good way to promote the language. Just because you cannot code in Pharo at your work does not mean you cannot code the Pharo way. Just put a huge tag in your documentation, comments and anywhere you mention your code "inspired by Pharo ( https://pharo.org)" and you will get their attention whether they like the idea of learning a new language or not. Its like watching an ad, using sex, humour and even unrelated stuff to grab your attention to a product. The idea here is to get the attention, once you do that, the rest follows. A huge problem with Smalltalk in general is that even though every language, enviroment, tool, IDE has been copying it , it is rarely mentioned. If it did , I have no doubt it would have been masively more popular than it is right now. On Mon, Nov 6, 2017 at 9:22 AM jtuc...@objektfabrik.de < jtuc...@objektfabrik.de> wrote: > > Phil, > > Am 26.10.17 um 08:17 schrieb p...@highoctane.be: > > > > > > Now we miss the boat on mobile and bigdata, but this is solvable. > > You know, "It's solvable, and it's even easy in Smalltalk" has been what > we've been shouting down at those worms in the C++/Java swamp for > decades. We just never really proved it. We also missed the boat on web. > Seaside was the last real innovation in that field, almost 15 years ago. > When Javascript took over the frontend, we lost pace. > > > > > If we had an open Java bridge (and some people in the community have > > it for Pharo but do not open source it - so this is eminently doable) > > + Pharo as an embeddable piece (e.g. like Tcl and Lua) and not a big > > executable we would have a way to embed Pharo in a lot of places (e.g. > > in the Hadoop ecosystem where fast starting VMs and small footprint > > would make the cluster capacity x2 or x3 vs uberjars all over the > > place) this would be a real disruption. > > To it sounds like a big ball of mud to me, but that is opinion ;-) > > > > > Think about being able to call Pharo from JNA > > https://github.com/java-native-access/jna the same way we use C with > UFFI. > > > > Smalltalk argument for me is that it makes development bearable (even > > fun and enjoyable would I say) vs the other stacks. That matters. > > > Yep. As long as there is no mobile, web or big data involved ;-) To me > that is not enough for convincing project managers these days, because > web, mobile and big data as well ass AI (oh, is that probably no. 4 on > our list of missed boats?) are the topics of what we consider > future-proof projects... I am not only dissing the Pharo community here, > this is a problem for all Smalltalk vendors in my opinion. > > > Joachim > > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuc...@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >
