Hi Igor! This is not the point. Modern architectures have different goals in mind. Projected on Pharo, it means that:
1. Make Pharo nonblocking. Remove any locking, completely. 2. Make Pharo fast. Use "in situ algorithms", avoid any copying of data, objects, whatever. 3. Make Pharo "overload proof". Install selfprotecting algorithms. 4. Read Knuth, use advanced algothims. Modern architectures dont't need to GC (or rarely). "Objects not created do not to be garbage collected!" 5. Make any GC concurrent for no longer intererrupting the VM. 6. Make Pharo multithreaded. Even my mobile has 2 processors, ASUS prime tablet even has 5! 7. Drop COGVM. LVCC is able to post - jit, callback problem solved, MP-ready, e.t.c. 8. UNIT Testing is not enough. Continuous benchmarking and stress/overload tests belong to *every* serious software development process. 9. You develop on MacOS. Where in the world are webhosters using MacOS? Make it work stable on FreeBSD, Linux, Windows Server 2008 ... 10. Use Moose...whatever to detect possible deadlocks. This belongs to modern software development. 11. Offer a collaboration tool on Pharo, where Smalltalk hobbyists may help you refactoring ... a todo list .. 12. Same for translations. 13. Long time ago i posted a bug: "Wrong development process". Stef deleted my entry without understanding. tnx 4 understanding, Guido Stepken 2012/2/14 Igor Stasenko <siguc...@gmail.com> > On 14 February 2012 17:07, Guido Stepken <gstep...@googlemail.com> wrote: > > Am 14.02.2012 16:57, schrieb Igor Stasenko: > > > >> On 14 February 2012 15:07, Hernan Wilkinson > >> <hernan.wilkin...@10pines.com> wrote: > >>> > >>> Well... this is an example of what the "thread" was about at the > >>> beginning... that is, the lack of knowledge on software development... > I > >>> you > >>> have known a little bit about architecture, multi-threading and vm > >>> implementation, you would quickly realize that pharo will not scale as > a > >>> server. Squeak (where pharo comes from) was not design/implemented to > be > >>> used as a server (and please, don not take this bad, I don't want to > >>> be unworthy with Pharo because it is changing and getting better with > >>> every > >>> realease) > >>> > >> There's no reason to take it bad, because you stating the truth. > >> > >>> So, if you want to do a "serious enterprise" application, you should > have > >>> used and architecture prepare for that such as GemStone (GLASS in this > >>> case)... it is a pity you lost so much money due to you "lack" of > >>> knowledge. > >>> > >> People who taking it serious also first discover the area of > possibility, > >> which implies talking to people and asking questions. > >> > >> I never seen from Guido questions like "does it scales if i run it > >> standalone etc". > >> And that means that he's not any serious with his harsh statements, > >> just trolling. > >> > > > > Lookup Google "Pharo hanging" ... very few companies are really using > Pharo, > > but i am not the only one reporting this. > > > Look for "rails hanging" - ~ 11 million hits > Look for "C# hanging" , java hanging etc > > now if this is the only criteria, on which you basing your choice, > then i feel sorry for you, because you cannot use any software made in > this world. > > so, have fun hacking. > > > Tnx for the "troll". > > > > Have fun hacking, Guido Stepken > > > > > > -- > Best regards, > Igor Stasenko. > >
