People introduced to amber is highly unlikely to be aware of Pharo but that does not change the fact that if you as Amber tell this coder "hey I also offer a very powerful IDE" instead of "hey I also offer a very basic IDE" it will be obviously a big plus for him.
I just dont think diverting resources to creating an IDE for Amber is optimal. Anymore than Pharo ignoring Amber and creating its own complex solution to access Javascript libraries would be optimal. I think that Amber and Pharo should be merged, maybe not as code bases or not as projects or websites or whatever but as communities. The way I see it both work towards the same goal, making the Smalltalk voice heard loud and clear. I think a closer integration is for the benefit of both communities. The communities are too small to afford to spread thin. Inventing the future is all cool and great but this world runs on money , not on progress and innovation. In most cases money is a big obstacle to progress. "I love progress , I just dont like change" (sorry dont remember where I got the quote from) So I think it would be wiser to be practical and take advantage of what you already have and take it one step further at a time. On Tue, Apr 29, 2014 at 2:56 PM, Sebastian Sastre < sebast...@flowingconcept.com> wrote: > > On Apr 29, 2014, at 5:58 AM, Markus Fritsche <mfrits...@reauktion.de> > wrote: > > > 1. The most kick ass thing I can think of would go something like this... > > > The most "kick ass thing" I can think of is... > > - Have a Pharo World being interfaced to an amber frontend, so you can use > your image through your browser. > > ... on second thought... that might be cool but after five minutes it'll > make me think "and now?" > > > Yes, what now? > > I agree the other way around is way more attractive. Both ways is awesome. > > But even that is invisible for most people. > > What they need is to look like ass kickers in the face of their clients: > *people > that buys the experience of the app not how easily hard they debug*. > > In the other hand, if they can debug better and use this tools to get to > the goal faster, that counts as ass kicking sure. > > What is happening now is that they’re using the javascript universe of > packages and make the right salad. > > There is a market opportunity in designers that shyly try to get something > non-static done for their clients. > > We should be listening to these guys. > > Using wordpress and adding plugins is profitable but it has limits and > they know that. > > So they are using the first thing that’s elegant and work with a conf or > two for a start. > > Express js is a good fit for them because is easy for them to grasp the > basics > > What I see is the opportunity of thinking beyond engineers and computer > scientists and being an option for designers. > > What I don’t see is us being prepared or caring about that huuuuuuuuuuuge, > even gigantic market. > > If we keep being reactive and defensive on this we will distance ourselves > of: > > Design Principles Behind Smalltalk > The purpose of the Smalltalk project is to provide computer support for > the creative spirit in *everyone*. > > > Let’s say eveyone is too much. Lets strategically focus in the two > audiences that are influential the most: > 1. computer scientists > 2. designers > > They are the innovators and disruptors. > > They are inventing the future > > In which ways are we making their lives easier? (or staying at the margin > from that) > >
