Can't we have a part of Pharo days devoted to fixing some of this? It would be useful I am sure.
STH is putting Amber, Pharo and Mongo together and is a good case for scaling properly. This may feel like a problem but is actually a huge opportunity to get our stack right. Amber is now 0.13 and much nicer inside. Is there a way to get a clone of the current running system for experimenting? I mean with the whole stack as it is? And STH can also be extended to point to Github resources, commits, ... and add a lot of readability to the packages. I do not want STH to die. It is useful. It is a great case. It works and just needs a little love. Who wants to help here? I think that I can, just need some interested people to join. Mail me. Phil Le 29 nov. 2014 01:08, "volk...@nivoba.de" <volk...@nivoba.de> a écrit : > > Am 27.11.2014 um 11:46 schrieb Sven Van Caekenberghe: > >> On 27 Nov 2014, at 11:14, Noury Bouraqadi <bouraq...@gmail.com> wrote: >>> >>> SmalltalkHub is slow, so don’t click too fast :-( >>> >>> While I’m grateful to developers of SmalltalkHub and previously >>> SqueakSource, I believe as a small community, we cannot afford developing >>> everything by ourselves. We don’t have enough man-power. We can see the >>> symptoms since SmalltalkHub is in beta stage since way too long... >>> >>> It’s better to use some mainstream platform such as github. >>> We’ll we have support for it in Pharo 4? >>> >>> It would be interesting also from the communication point of view to >>> make the world a little bit more aware of Pharo. >>> >> I think it is important to have a serious online system written in Pharo >> and in daily use (you know, eat your own dog food). >> >> There is also a difference between the system itself and the way it is >> deployed/managed. >> >> Please do not underestimate how much work this is for something that is >> used so heavily, like StHub. >> >> Yes, this is important for Pharo in some way. But such a the system have > to be maintained > and developed further/keept up to date, otherwise it has a bad impact. > But i have the feeling > in Pharo so many cool things started and then slowly waste away ... Why? > The Community > is to small, ... the cool guys move further. The PhD is finished ... Gaps > hard to close. Would > be sad, if this happens to SmalltalkHub. > > There should be only 2-3 public, open source key systems (or type of > systems) where to put > the focus on and give them a long term perspective & support from the > association / consortium > or other donators. And the systems and its building blocks should move > with Pharo in the future. > And the system should be in some obviously way special & exceptional ... > and part of > the "Pharo Masterplan". > > (a) Data Analysis & Visualization System > => ?? MOOSE ?? > => Key Building Blocks: f.e. Roassal2/3D, ZincHTTP, NeoCSV, NeoJSON, > ... > (b) Online/Web System > => ?? SmalltalkHub ?? > => Key Building Blocks: f.e. Amber, Seaside, ZincHTTP, NeoCSV, > NeoJSON, ... > (c) A Cool Game (would love it) > => ??? > => Key Building Blocks: ??? > (d) ??? > > I know, it is easy to say. But the best promotion for Pharo are cool > systems in Pharo. But maybe > Pharo has not more potential than doing one type of systems right and > ongoing, f.e. (a). > I have no problems with it. I like Pharo for (a) as i like Erlang/OTP for > (b) and Lua/Love2D for (c). > The coolest would be a perspective for (a), (b), (c) and (d) in Pharo. But > i do not see it ... > > But yes, it is better to do one or two things good, and not a five bad. > > My 2 cents, > Volkert > > > > > > > > > > > > >
