- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 7.0 released!

by Norbert Hartl

Congratulations to you all! It has been a hard piece of work which was postponed 9 months. But the changes to collaboration process, build process, 64 bit maturing and huge list of things was worth it. Hopefully the next version is less huge. Happy to be able to take part!!! Norbert > Am 22.01.2019 um 14:36 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Pharo 7.0 released! > =============== > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > <pastedGraphic.png> > > > This is our most significant release yet. Here are the key highlights of this release: > > â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. > â¢ Pharo comes with a new version of the PharoLauncher (https://pharo.org/download) THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). > â¢ Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. > â¢ Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. > â¢ Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. > â¢ IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. > â¢ The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. > > Pharo 70âs new infrastructure and process set the stage for a new generation of version. > The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. > > These are just the more prominent highlights, but the details are just as important. > > We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change…) > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. > (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

Jan. 23, 2019

Pharo 7 image does not load

by sergio ruiz

I have been working in my image all day today, and it was working great. This evening, when I went to fire it up, it appears to start, but I am not seeing the image running. The icon hangs, and it does nothing. Here is an my debug.log for just one iteration of this. Any help would be appreciated! https://gist.github.com/sergio101/c86396d10f6fea4923b59930ad44a2a0 ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 23, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 7.0 released!

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Thank you, everybody, this is a massive collaborative effort, something to > be proud of. +100!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 23, 2019

Re: [Pharo-users] [squeak-dev] Falsehoods programmers believe about Smalltalk

by Eliot Miranda

On Mon, Jan 21, 2019 at 1:13 PM HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > > Done. > > I have some possible myths, but I'd like to confirm or reject: > > - All Smalltalk bytecode sets are stack-based VM. (?) > While there might be some implementations that use a register based bytecode set I've never heard of one. I do know of a few implementations that don't use bytecode at all. > - Bytecodes are always fixed-size. (?) > False. > - Most of the time spent by a VM is in the instruction interpreter. > (actually it's in the GC right?) > Neither. In a JIT VM most time is spent executing Smalltalk code. GC overheads vary depending on workload, typically in the range 1% to 50% (typically for specially constructed benchmarks written to stress the GC). > - You cannot serialize objects containing blocks. (IIRC one can use > MessageSends) > False. > - Image cannot be bootstrapped. (This is possible in ST/X and now in Pharo > I think). > False. > - All Smalltalks includes UI classes. (GemStone doesn't have AFAIK). > False. > - All implementations uses direct pointers, (GST?) > False. VisualWorks uses indirection pointers. Xerox Smalltalk-80 implementations used indirection. But many modern implementations use direct pointers. > - All implementations uses green threads. (VAST? MT?) > False. SmalltalkMT. But still mostly true. VAST & VW have green threads and a threaded FFI. > I'm sure people in this list will have a lot more myths heard from > Conferences, Forums, Videos, Talks, etc. Like the guy who said Smalltalk > was dead. So if you did something which could be ignored publicly, please > don't hesitate to reply or ping me to get added as collaborator. > > Cheers, > > HernÃ¡n > > > > El dom., 20 ene. 2019 a las 22:41, Eliot Miranda (<eliot.miranda(a)gmail.com>) > escribiÃ³: > >> Hi HernÃ¡n, >> >> On Sun, Jan 20, 2019 at 2:31 PM HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com> wrote: >> >>> Hi there, >>> >>> I just created a GitHub repo to collect myths around Smalltalk-based >>> technologies: Pharo, Squeak, VW, VAST, Smalltalk/X, GNU/ST, etc. in the >>> spirit of the Falsehoods lists [1-4]. >>> >>> This is just a draft now but please feel free to add falsehoods based on >>> your own experiences. Examples are greatly appreciated. >>> >> >> You want pull requests? If not, would you give me write permission? I'd >> love to add to the "Smalltalk is obsolete" section... >> >> >>> >>> https://github.com/hernanmd/falsehoods_smalltalk >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> [1] >>> https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-ab… >>> [2] >>> https://chiselapp.com/user/ttmrichter/repository/gng/doc/trunk/output/false… >>> [3] >>> https://github.com/googlei18n/libphonenumber/blob/master/FALSEHOODS.md >>> [4] >>> https://meta-package-manager.readthedocs.io/en/develop/falsehoods.html >>> >>> >>> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> > -- _,,,^..^,,,_ best, Eliot

Jan. 23, 2019