- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Sean P. DeNigris

I was reading this thread and watching... Sean arguing... that Pharo is NOT Smalltalk No!!!!!!!! As I and Esteban (at least, maybe others) have repeated, *we are NOT saying that Pharo is not Smalltalk*. Either we're not explaining ourselves well or (more likely IMHO) everyone is so emotional over this (and it's a good thing that we care that much) that they're not actually reading what we're saying. How can you read either http://forum.world.st/Pharo-is-Smalltalk-and-Not-td4757342.html or my two main points at http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4756995… and say that I'm saying that?! I think there is a middle ground where everyone gets what they want. I've tried to express it in the first link above. Please - I love differences and discussion, but if you're going to react, react /specifically/ to what I said (e.g. the two points I made in the second link), because right now, you are only arguing with yourself ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757346… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Jimmie Houchin

I understand. My apologies for contributing to one of those days. For me that day was while I was reading this thread and watching Doru and Sean arguing with Eliot. It almost made me want to go back to Squeak. Not that I am saying there is anything wrong with Squeak. They were firmly arguing that Pharo is NOT Smalltalk. They contend that making changes that make it different than Smalltalk-80 make it not Smalltalk. http://www.tudorgirba.com/blog/pharo-is-pharo Their contentions were not refuted. I wanted to put forth my understanding and opinion that Pharo is a Smalltalk. And then you reply stating of course everybody here knows Pharo is Smalltalk. But that is exactly what Doru is arguing against. If Pharo is going to distance itself from Smalltalk and be consistent about it, then every Pharo reference to Smalltalk in the image or website or wikipedia unless historical should be changed. This inconsistency makes Pharo look bad. Jimmie On 04/30/2014 01:58 PM, Esteban Lorenzano wrote: > Some days a I really would love not to love smalltalk... > > On 30 Apr 2014, at 20:52, Jimmie Houchin <jlhouchin(a)gmail.com > <mailto:jlhouchin@gmail.com>> wrote: > >> But that is the point. This kind of marketing is false. It denies who >> we are. >> >> As soon as they look at Pharo. Learn to use and then learn that Pharo >> is a Smalltalk and that we are liars. >> >> Did keeping silent about Pharo help in the Reddit thread. No. >> Did the current marketing explain well what Pharo is. No. >> Read the thread. People were confused. >> And regardless of the marketing attempt, the fact of Pharo being a >> Smalltalk did not remain suppressed. So therefore, those who were >> closed minded against Smalltalk have then been alerted, and they can >> close their minds. Attempting to not make it plain was an abject failure. >> >> People who understand the value of Smalltalk and of a modern open >> source implementation will come. >> >> >> I guess none of the commercial Smalltalks are alive? Nobody knows of >> them. They are going broke? >> >> Gemstone, VisualWorks, ... >> >> What is this new thing that people are using? >> >> Clojure based on Lisp. Not new. >> Python 23 years old. >> Lua 21 >> Ruby 19 >> >> Clojure based on Lisp but adding modern functional features disproves >> any thought that an old language with lots of baggage can't attract >> new users. >> From the Clojure home page. """Clojure is a dialect of Lisp""" >> They embrace their heritage and are better for it. They also detail >> their value proposition and being a Lisp is part of it. >> >> >> I am all agreeable to attracting people to our community. But >> falseness isn't the way. >> >> Not everybody is closed minded and ignorant. Those that are we can >> wait until they are not. >> >> But Pharo has to offer people the proper value proposition. When it >> does, I believe it will attract sincere people. When the value of >> Pharo meets the needs of the people, it will attact the appropriate >> people. But until then, we can market it however we want and they >> will not care. Right now Pharo is working hard to reach that point >> that it can offer them something they will value. For some it already >> does. For others not yet. That not yet, it a bigger obstacle than >> Pharo being marketed as a Smalltalk and telling the truth. >> >> We need to embrace being a Smalltalk and sell our value proposition >> in terms that mean something to somebody who doesn't already get >> Smalltalk. We failed at that. Too vague, too ambiguous. It confused >> some of the Reddit people. People to whom we are supposedly intending >> to attract and market to. >> >> Jimmie >> >> >> On 04/30/2014 01:22 PM, Esteban Lorenzano wrote: >>> Againâ¦ you are missing the point. >>> nobody here doubts Pharo is a Smalltalk. >>> nobody outside our small world believes Smalltalk is alive. >>> >>> And yesâ¦ you can argue all what you want. But you are scratching >>> where it does not itch. >>> >>> We choose not to *market* Pharo as a Smalltalk, because each time >>> someone outside our small world hear about Smalltalk believes that >>> is a long time dead language. No matter how much effort you put into >>> explain that is not true, people will not believe it. And people is >>> always more willing to try something new than something old (except >>> in the case of wines and fine alcohols, of course). >>> Soâ¦ we prefer to track people to our community and let them notice >>> wat WE ALL KNOW: Smalltalk is not dead, and Pharo is a proof of that. >>> >>> Esteban >>> >>> On 30 Apr 2014, at 20:07, Jimmie Houchin <jlhouchin(a)gmail.com >>> <mailto:jlhouchin@gmail.com>> wrote: >>> >>>> In the Smalltalk heritage. Pharo comes from Smalltalk 80. >>>> >>>> But we don't want to be stuck in 1980. We want Smalltalk 2014. >>>> Smalltalk 80 was modern for 1980. They didn't want to be stuck in >>>> 1976. ... >>>> >>>> And Smalltalk isn't unique to this. Is C11 not a C because it is >>>> not K&R, or C89, C90 or C99? >>>> Is Python 3.x not Python because it is not fully compatible with >>>> Python 2.x which is dominant? >>>> >>>> Pharo wants to be a modern Smalltalk able to empower people in this >>>> era to do things that we do in 2014. We need appropriate modularity >>>> in the image. We need the image to be clean. We need to learn the >>>> lessons we as Smalltalker's have learned in the last 24 years and >>>> apply them to Pharo Smalltalk. And I believe that is much of what >>>> Pharo is attempting to do. >>>> >>>> Noel in his talk said that Smalltalk doesn't play well with others. >>>> And with Pharo it still isn't as easy as in other languages like >>>> Python, Ruby, Lua, etc. But with NativeBoost we have a tool which >>>> enables us to do much. And NativeBoost isn't finished. I believe >>>> when NativeBoost is fully mature and the vm/image has sufficiently >>>> changed to enable us. We will have one of the best plays with >>>> others well stories. >>>> >>>> I know in the app I am writing, NativeBoost's current condition >>>> struggled with my library. It often crashed. This library has to >>>> deal with a C Thread. Which is why I am spending my current time >>>> studying C. >>>> >>>> Whether or not the Smalltalk Inspired crowd likes it, the moment >>>> some else declares that Pharo is a Smalltalk the Smalltalk Inspired >>>> marketing is tanked. The cat is out of the bag. >>>> >>>> The Reddit thread demonstrates this. People went to the new >>>> website. They read the current marketing and were confused. What is >>>> this Pharo thing. And in the thread it comes out that Pharo is a >>>> Smalltalk. Lets make that clear up front. Then lets define what it >>>> means to be Pharo Smalltalk. >>>> >>>> Here is an unfortunate quote from that thread. >>>> >>>> """ >>>> emaringolo 1 point an hour ago >>>> Pharo is aimed to do serious/business development, and it's been >>>> reshaping itself since its conception (several years ago when it >>>> forked from Squeak). >>>> It doesn't want to have any backward or "historic" compatibility >>>> with other Smalltalks. >>>> You can see its changelogs and the roadmap for future versions to >>>> see how it is different, and how it will be different. >>>> """ >>>> >>>> This makes it sound like Pharo wants remove compatibility simply >>>> for the sake of not being a Smalltalk. As opposed to what I believe >>>> Esteban meant. And yes I understand that English is not his native >>>> language, and there are many for whom it is, who still use it >>>> poorly. What I believe he meant, is that Pharo will not be >>>> constrained by backward compatibility. If a change or feature that >>>> is of value to Pharo Smalltalk. That feature will be done even if >>>> it means breaking backward compatibility with other Smalltalk 80 >>>> based Smalltalks. We are moving forward. But this does not >>>> invalidate Pharo being a Smalltalk. As has been stated before, >>>> breaking changes happened in Smalltalk 76 and 80. >>>> >>>> Smalltalk has a wonderful heritage. It is not without its issues. >>>> However the good of Smalltalk is enormous. Take a look at this chart >>>> http://exploringdata.github.io/vis/programming-languages-influence-network/ >>>> Smalltalk is a big influence in the history of programming. This is >>>> something worth being a part of. Be proud of it. >>>> >>>> Pharo needs to define what one vision of a modern Smalltalk is. Let >>>> us educate people of what our vision for Pharo Smalltalk is. And >>>> guess what folks its 2014. Before long it wont be. And before long >>>> the vision of Pharo 2014 will no longer be any more modern than >>>> Smalltalk 80. But neither Smalltalk 80 nor Pharo 3.0 constrain what >>>> it means to be Smalltalk. Smalltalk inspires vision and inspires >>>> people to do things which change the present and the future. Lets >>>> build on that heritage and take it forward. What does a modern >>>> Smalltalk snapshot 2014 mean. Lets educate and communicate. Others >>>> (non-Smalltalkers) don't get to define what Smalltalk is. We do. >>>> >>>> Let us learn from them what they think Smalltalk is. Where they are >>>> wrong, educate them. Where they are right and we have an issue. >>>> Let's learn a lesson and improve our Smalltalk. >>>> >>>> Computer science/art is young. This is a journey. Lets make it a >>>> good one. >>>> >>>> Jimmie >>>> >>>> >>>> >>>> On 04/30/2014 11:12 AM, phil(a)highoctane.be wrote: >>>>> Pharo := Smalltalk ++ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Apr 30, 2014 at 5:43 PM, Jimmie Houchin >>>>> <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> wrote: >>>>> >>>>> On 04/28/2014 11:12 AM, Marcus Denker wrote: >>>>> >>>>> â¦ more a Smalltalk one using Pharo: >>>>> >>>>> MountainWest RubyConf 2014 >>>>> >>>>> Noel Rappin: "But Really, You Should Learn Smalltalkâ >>>>> >>>>> Smalltalk has mystique. We talk about it more than we use >>>>> it. It seems like it should be so similar to Ruby. It has >>>>> similar Object-Oriented structures, it even has blocks. >>>>> But everything is so slightly different, from the >>>>> programming environment, to the 1-based arrays, to the >>>>> simple syntax. Using Smalltalk will make you look at >>>>> familiar constructs with new eyes. Weâll show you how to >>>>> get started on Smalltalk, and walk through some sample >>>>> code. Live coding may be involved. Youâll never look at >>>>> objects the same way again. >>>>> >>>>> http://www.confreaks.com/videos/3284-mwrc-but-really-you-should-learn-small… >>>>> >>>>> >>>>> In this thread and many others there is this debate as to >>>>> whether Pharo is a Smalltalk or is Smalltalk Inspired. >>>>> >>>>> I find the Smalltalk Inspired arguments to be unpersuasive. To >>>>> be Smalltalk Inspired is to say that you are not a Smalltalk. >>>>> It is to say that Pharo is not Smalltalk but inspired by it. >>>>> >>>>> I find that reasoning patently false. >>>>> >>>>> First of all everything in Pharo begins from a Smalltalk >>>>> image. It comes from Squeak Smalltalk which comes from Apple >>>>> Smalltalk. etc. >>>>> >>>>> Pharo has an isA relationship with Smalltalk, not an >>>>> isInspiredBy relationship. It may change and add features, but >>>>> as has been stated before, Smalltalk isn't a static idea or >>>>> artifact. It has always been a dynamic live environment in >>>>> which to change itself into something it believed to be >>>>> better. By removing features and by growing them. >>>>> >>>>> Smalltalk (an instance of SmalltalkImage), SmalltalkImage, >>>>> SmalltalkImageTest, SmalltalkEditingState are all part of the >>>>> Pharo Smalltalk image. >>>>> >>>>> The Pharo image is a Smalltalk image. It says so inside the >>>>> image itself. >>>>> >>>>> Where are we hosting are source code? Would that be SmalltalkHub? >>>>> Lets see something. >>>>> http://www.smalltalkhub.com/#!/~Pharo >>>>> <http://www.smalltalkhub.com/#%21/%7EPharo> >>>>> >>>>> Okay, Pharo might be doing things that would break >>>>> compatibility with other Smalltalks. And that causes some >>>>> people pain and grief. However that does not make Pharo not a >>>>> Smalltalk. Was Smalltalk 76 constrained by backward >>>>> compatibility with Smalltalk 72? Or Smalltalk 80 with either >>>>> Smalltalk 76 or 72? No! >>>>> >>>>> Is it a requirement of Pharo to be constrained by other >>>>> Smalltalk implementations in order to still be a Smalltalk. No! >>>>> >>>>> And then there is the argument of the outside worlds >>>>> perception of Smalltalk. Since when does the perception of the >>>>> outside world change whether or not Pharo is a Smalltalk? If >>>>> the outside world changed their mind and decided Smalltalk is >>>>> wonderful, does Pharo then all of the sudden become a >>>>> Smalltalk? Ugh! >>>>> >>>>> We are who we are. Our roots are our roots. Pharo should be >>>>> happy and proud to be a Smalltalk. A Smalltalk that is >>>>> continuing the heritage of innovation. A Smalltalk that is >>>>> continuing the heritage of inventing the future. >>>>> >>>>> We have decided to be marketing driven. Marketing is >>>>> important. But marketing should determine who we are. And we >>>>> should engage in disingenuous marketing practice trying to >>>>> hide our roots or who we are. >>>>> >>>>> Why do we things distancing ourselves from Smalltalk >>>>> advantages us? Just because there are lots of uneducated >>>>> people who have the wrong idea about Smalltalk. Clojure >>>>> embraced its Lisp heritage and is thriving. Lisp has every bit >>>>> as much baggage. >>>>> >>>>> This talk which inspired this thread called Pharo as >>>>> Smalltalk. He said, Pharo Smalltalk throughout the >>>>> presentation. So in the mind of the presenter and now in the >>>>> mind of the audience at the conference and of the video, Pharo >>>>> is a Smalltalk. So now are we to go about re-educating all >>>>> these people that Pharo is not a Smalltalk but is rather >>>>> Smalltalk Inspired? >>>>> >>>>> We don't require the outside world's permission. We don't need >>>>> their approval. We would like to have a reasonable and >>>>> sufficient number of them to catch the Pharo Smalltalk vision >>>>> and become a part of the family. Do we really desire >>>>> everybody. No. Do we desire those people who are so closed >>>>> minded that the mention of Smalltalk closes their mind because >>>>> of their ignorance. I don't think so. >>>>> >>>>> Smalltalk is different. Pharo is Smalltalk and is different. >>>>> There will be those who don't like it because of the baggage >>>>> they bring, not the baggage we bring. And that is okay. All of >>>>> us think different. People need to embrace what empowers them >>>>> and quit complaining about what empowers somebody else. We >>>>> need to embrace empowering people who understand Smalltalk not >>>>> the people who don't get it for whatever reason. Let those >>>>> people go and be empowered somewhere else. We and they will >>>>> both be better off. >>>>> >>>>> Feel free to shred and destroy my arguments. I am proud to use >>>>> Smalltalk. And currently Pharo is the Smalltalk I am choosing >>>>> to use. Currently I am studying C. A C library is required for >>>>> my project and in order to use Pharo and use this library, I >>>>> need sufficient C skills. >>>>> >>>>> My opinion unapologetically. >>>>> >>>>> And if the powers that be who are in charge of Pharo decide >>>>> that Smalltalk (in name) is baggage and Pharo is not >>>>> Smalltalk. And that marketing Pharo as Smalltalk is bad. Then >>>>> please be honest and change all references in the image of >>>>> Smalltalk to Pharo. Also change SmalltalkHub to PharoHub or >>>>> SmalltalkInspiredHub. >>>>> >>>>> If if not, be sincere and embrace Pharo Smalltalk. >>>>> >>>>> Long live Smalltalk. >>>>> >>>>> Jimmie >>>>> >>>>> >>>> >>> >>

April 30, 2014

Re: [Pharo-dev] New Website online

by Tudor Girba

Excellent work! Thank you: Nico, Esteban, Marcus! Doru On Wed, Apr 30, 2014 at 4:44 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > yeah, and donât forget Nicoâs effort :) > I put him real pressure on him last 3 weeks, and he took it without > complainâ¦ and he did a great work :) > > Esteban > > On 30 Apr 2014, at 16:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > Marcus Denker-4 wrote > >> The new website is online! > > > > Wow! Instantly obvious that Aurelia was involved because it has that > "well > > designed" look instead of our usual "I'm an engineer trying my best" > look, > > lol ;-P > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/New-Website-online-tp4757241p4757250.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

April 30, 2014

Re: [Pharo-dev] good article on mainstream adoption of programming languages

by kilon alios

I am sorry but again a big NO from me. I am interested in two field, Graphics (2D and 3D) and music/audio synthesis. Both of these fields are dominated by C/C++. You could say is because of the fact that C/C++ is heavily optimised and of course I would agree but its not that of a big reason because a) other languages can use C/C++ libs b) its possible to compile a language to C/C++. For example python has cython , similar to Slang for Pharo. Take your language of choice outputs optimised C/C++ that can get compiled and linked back to your favorite language as a library. Still the vast majority of coders code in C/C++ for these two fields. Why ? Simple, libraries, tons of them. There is no way anyone would port all of these libraries to Python let alone Pharo. Its not hard to use those libraries from Python but people dont do it , its just more effort, and because its simple just to do it on the language the lib is documented. This is why also language popularity is highly heated discussion, popularity highly fluctuates. For example you go web dev Javascript is king, you leave web dev Javascript becomes practically unknown. Enterprise ? Java is the undisputed king. Windows development ? .NET and C++ hands down. How about iOS ? Objective C without a doubt. Android ? Java again. Unix/Linux ? of course C/C++ and so on so forth. You could even say that languages prosper more when they pick a niche and again the reason why that happens is because of course of libraries. Afterall the language itself is rarely non general purpose. Its the libraries that give the specialisation to the language. On Wed, Apr 30, 2014 at 10:55 PM, Johan Brichau <johan(a)inceptive.be> wrote: > > > Yet it worked like a charm because developers loved the fact that they > had in their hand a huge monolithic platform that could satisfy their > wildest dream as far as library support went through. And on top that > platform was cross platform. > > Sounds like Smalltalk :-) > > Don't get me wrong: a language without libraries is like an OS without > applications, but the point is that most of the unpopular languages have > sufficient libraries. After doing Smalltalk for over 15 years, I still > discover things inside the libraries that come with a standard image. > > And yes, some libraries will attract people: office libraries in .net, RoR > in Ruby, etc... > > I think once sufficient libraries are present, an active community is more > important (in the absence of large company backing) and libraries are a > consequence. > > But hey, we should probably go have a beer over this ;-) > > Johan >

April 30, 2014

Pharo is Smalltalkâ¦ and Not

by Sean P. DeNigris

All of the arguments why Pharo is Smalltalk are correct. Let me tell you a story... My friends and I are planning a trip to Spain. I am explaining that in Spanish, "yo" - which means "hi" in English slang - means "l". They are arguing passionately that "yo" means "hi" and presenting evidence upon evidence to prove it. Then I snap back that, no, "yo" definitely means "I". Ridiculous, right? Sounds kind of like a Monty Python skit. Well, Pharo is planning a trip to the programming world of non-Smalltalkers. I am explaining that in Ruby, "Smalltalk" - which means "a language with a development environment written in itself which both were designed to continually evolve*" in the Smalltalk community - means "Smalltalk-80". My friends are arguing passionately that "Smalltalk" means the former and presenting evidence upon evidence to prove it. Both of these disagreements fail to take into account that truth is contextual and language imprecise. So please, please, please, please, please, no more theses on why Pharo is Smalltalk, or why it's not. It's neither, and both, and more! We're talking about effectively marketing to non-Smalltalkers, and our theory (only time will tell) is: for our first initial sound bite, Smalltalk-inspired (or silent about Smalltalk, which I think may be even better) will be more intention revealing to the target audience than Smalltalk. Either way, we're going to have to do some more explaining if they're interested in hearing more. But with the first, maybe, they will be interested in hearing more before being turned off by a preconceived (and incomplete) notion of what "Smalltalk" is. But there is a valid question here of how to manage the inevitable misunderstandings... I'll posted some ideas for that in a bit... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-is-Smalltalk-and-Not-tp4757342.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Sean P. DeNigris

sebastian(a)flowingconcept.com wrote > Then itâs a failed decision as Reddit reactions proves. I think that's a bit premature. The reaction on Reddit was because there was no mention on the Pharo site/release-notice of Smalltalk *anywhere*. There was no path to take people from the sound bite to the full picture (I'm writing some thoughts on that right now and will start a separate thread). You don't wave the white flag after losing one battle! And certainly not when the evidence of losing even that battle is a few commenters on Reddit! We learned an important lesson - if we're not going to provide people with a neat little pink plane Smalltalk box to put Pharo in, then we better have some good answers as to what it /really/ is when they start investigating. Each one of those criticisms is an opportunity. The useful question is - what supporting explanation on the website would have taken their initial curiosity, possibly enabled by not being turned off by a misunderstanding of the word "Smalltalk", and guided them down the path of understanding the fuller picture that - it is an environment, and a library, and a dialect of the Smalltalk language. ----- Cheers, Sean -- View this message in context: http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757341… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] Pharo RPi and FileSystem error

by jannik laval

Thank you guys, I will try to find something that does not break Phratch. Cheers, Jannik 2014-04-30 19:43 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I thought that we did that already: > > OSEnvironment class>>#isAvailable > NativeBoost class>>#isAvailable > PlatformIndependentEnvironment > > No ? > > Are you using the latest 3.0 ? > > On 30 Apr 2014, at 18:49, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> > wrote: > > > That the point I want to checks it, run test and if work integrated for > raspbian. > > It is completely generated it shouldn't have any problem. But ... > > > > A really nice guy can just do the image side hack to avoid FileSystem > error. > > > > On 30 Apr 2014, at 18:24, Douglas McPherson <djm1329(a)san.rr.com> wrote: > > > >> As a data point, OSProcess works "out-of-the-box" with the Squeak > interpreter VM shipped with Raspbian. So should be ok in Pharo, but I > haven't tried it. > >> > >> Doug > >> > >> On Apr 30, 2014, at 09:03 , David T. Lewis wrote: > >> > >>>> > >>>> There are no NativeBoost on Rpi, FFI or OSProcess. > >>>> Basically the fileSystem work, but some data are fetch via env > variable > >>>> and then NativeBoost. > >>>> The solution is to bypass all the request of env variable. > >>>> You should use another way until, we finish to integrate a way to > request > >>>> correctly the env variable (NB on arm). > >>>> > >>>> I will studies the possibility to reintegrate fast the OSProcess > plugin to > >>>> offer "better" solution. > >>> > >>> > >>> I would expect OSProcess to work without problems on Rpi, although I do > >>> not have a way to test it. The plugin should be fine. Maybe some > changes > >>> will be needed on the image side for detecting the platform, I'm not > sure. > >>> > >>> Let me know if I can help, I will be glad to add any necessary patches > to > >>> OSProcess. > >>> > >>> Dave > >>> > >>> > >> > >> > > > > > > > > Best Regards > > Jean Baptiste Arnaud > > jbaptiste.arnaud(a)gmail.com > > > > > > > > > > > > > > > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

April 30, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by kilon alios

We should not forget the "Java is dead" craze over a decade ago. It was the time where dynamic language like python and ruby were gaining a lot of traction but here we are a decade later and Java is alive and kicking. I seriously doubt that there are a lot of people out there that take "Smalltalk dead" seriously when the internet is littered with "C is Dead" , "Javascript is Dead" , "Lisp is Dead" etc etc Its just a meaningless word that people love to use in a desperate attempt to get more hits and appear in Google results. Its more like a joke. I completely agree with you that "Smalltalk inspired" is reinforcing "Sorry for dead Smalltalk , we will try to follow its legacy, RIP Smalltalk" , at least this is how I see it. I may be wrong. The question I want to raise is how many coders out there are even aware what Smalltalk really is ? I was not aware of Smalltalk 2 years ago. Thats the sad truth. Another mistake is that people tend to over idealising Smalltalk and it appears as if Smalltalk used to be popular, but I have found no evidence that Smalltalk was ever popular. Again I may be wrong but this is also maybe a motivation to regard Smalltalk dead. On Wed, Apr 30, 2014 at 10:38 PM, vfclists . <vfclists(a)gmail.com> wrote: > > > > On 30 April 2014 19:33, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> 2014-04-30 15:07 GMT-03:00 Jimmie Houchin <jlhouchin(a)gmail.com>: >> > Here is an unfortunate quote from that thread. >> > >> > """ >> > emaringolo 1 point an hour ago >> > Pharo is aimed to do serious/business development, and it's been >> reshaping >> > itself since its conception (several years ago when it forked from >> Squeak). >> > It doesn't want to have any backward or "historic" compatibility with >> other >> > Smalltalks. >> > You can see its changelogs and the roadmap for future versions to see >> how it >> > is different, and how it will be different. >> > """ >> > >> > This makes it sound like Pharo wants remove compatibility simply for the >> > sake of not being a Smalltalk. As opposed to what I believe Esteban >> meant. >> > And yes I understand that English is not his native language, and there >> are >> > many for whom it is, who still use it poorly. >> >> That's certainly an interpretation. >> >> I didn't mean it wants to REMOVE compatibility, but I did mean it >> doesn't wan't backward compatibility with Smalltalk per se. Sometimes >> it isn't compatible with previous versions of itself! >> >> I remember having read exactly that: "we don't want backward >> compatibility". >> >> > What I believe he meant, is that Pharo will not be constrained by >> backward compatibility. >> > If a change or feature that is of value to Pharo Smalltalk. That >> feature will be done even >> > if it means breaking backward compatibility with other Smalltalk 80 >> based >> > Smalltalks. >> >> This is exactly what I meant. >> >> > We are moving forward. But this does not invalidate Pharo being >> > a Smalltalk. As has been stated before, breaking changes happened in >> > Smalltalk 76 and 80. >> >> As a disclaimer I'm a strong defender of not hiding the "Smalltalk" >> heritage in Pharo. >> However there is no need to name something "Pharo Smalltalk" to have a >> connection with its past, but also no need to avoid any mention of the >> word Smalltalk in the new home page. At least from the SEO point of >> view. :) >> >> Regards, >> >> >> Esteban A. Maringolo >> >> > > The problem here is that if you downplay the Smalltalk foundations of > Pharo then you only reinforce the impression that Smalltalk is outdated > when it is revealed that Pharo is a Smalltalk. What matters more is whether > Pharo is a "Smalltalk done right", or Smalltalk for the New web 3.0 era, > where none of the popular languages offer a live coding environment. > > An open source Smalltalk should really target Python in the areas where > Python is used as a scripting front end to systems written in higher > performance languages, ie stuff like Blender, Unity, Gephi etc. Power users > who need live interactive environments should be the main target of a tool > like Pharo. That also fits with early Smalltalk designers principles which > were focused on helping end users model their stuff, children to a large > extent. > > For software developers something like Smalltalk/X would probably be a > better bet if the licensing could draw more developers to it, or one of the > other Java based Smalltalk if they were finished. They need better > interoperability and the ability to drop down to C or some other low level > language when they need it. Software developers are not thinking about what > they can do with it now, they are thinking of what they will not be able to > do with it 18 months down the line. > > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com >

April 30, 2014

Re: [Pharo-dev] good article on mainstream adoption of programming languages

by Johan Brichau

> On 30 Apr 2014, at 21:51, kilon alios <kilon.alios(a)gmail.com> wrote: > > Every language out there runs in the Browser You may know this: https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript Johan

April 30, 2014

[OT] The Sociological Science Behind Social Networks and Social Influence

by Sebastian Sastre

Not exactly pharo-dev related but people related and Pharo is done by people and this might contribute to understand the dynamics of people: Nicholas Christakis: The Sociological Science Behind Social Networks and Social Influence http://www.youtube.com/watch?v=wadBvDPeE4E

April 30, 2014