Offray Vladimir Luna Cárdenas-2 wrote > But I have not > being able to convince any of my coder friends to switch to Pharo > instead of C++, Java or Javacript, which by the way, is the language > they already know and use to put bread on the table on a daily basis. > > So I think that we deal with a paradox: while Smalltalk advocacy is > better suited for a Blue Ocean Strategy[2], exploring and implementing > new/emerging scenarios and markets, money is already mostly invested in > Red Oceans of constituted technologies and practices ecosystems. > Bridging both is pretty difficult.
Yes, that is the principal obstacle and challenge. When I'm pushing Smalltalk, I mention the language's simplicity and conciseness, I mention the purity of the object-oriented model, I mention the built-in IDE, and so on. But the key advantage that I emphasize is *programmer productivity*. I realize it's hard to argue with the availability of jobs for Java, Python, JavaScript, etc. It's hard to argue with their rich ecosystems. It's hard to argue with the status quo of established code bases and IT infrastructures. But we have to make them believe that Smalltalk can cut their development time in half, if not better. What is it worth to a company to cut their development time in half? It means much lower development cost. It means much shorter "time to market." Is this not worth investing time and energy in Smalltalk? Even if the job opportunities aren't there. Even if it means overhauling your IT infrastructure. The investment can lead to more users and more jobs. If they don't believe it, then we have failed. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
