[reymus]

> then you don't understand what Smalltalk is anyway Sorry, but I think that is just wrong. As far as I know, Pharo is one of the best and more approachable alternatives to enter the Smalltalk world. They should be doing a better job at welcoming people to "their world". If they want people to just come already knowing what they are going to get, I don't see how are they going to go mainstream, ever (assuming they would like to.)

[kilon]

My personal opinion on this and no way the opinion of core Pharo devs, I am just a newcomer to Pharo and a minor contributor.

Mainstream will kill Pharo in an instant. Pharo is too cool and too well designed for mainstream. Pharo also is going towards a complete opposite direction of sacrificing features over ease of usage.

So in the end Pharo is not designed for the mainstream developer its designed for the developer that looks for something radical diffirent.

But diffirence comes with a cost, it means that you get out your comfort zone, explaining basic concepts takes much more time and effort because of lack of familiarity etc etc.

So if you dont understand Pharo at first try, thats not a bug thats a feature. If you do understand Pharo at second try that's a bug.

Some people refer to pharo as "the red pill" of coding, taking the red pill has its advantages but also significant disadvantages. The choice in the end is yours.

Sure documentation and website can be improved but it wont solve the problem that Pharo is outside mainstream way of doing coding because this is what makes Pharo so fun to work with :)

[zak_mc_kracken]

> Pharo is too cool and too well designed for mainstream.

And people wonder why the Smalltalk community has such a bad reputation.

[kilon]

Does your definition of "bad reputation" also includes modern software basing itself on ideas and implementation that either originated from Smalltalk or greatly improved by it, like GUI MVC , mouse integration, VM , Test Driven Development , IDE and much more ?

If yes then I hope Pharo keeps bringing a lot more of this "bad reputation" I find it very useful and productive. Frankly I wish I was aware of this "bad reputation" 25 years ago, would have saved me a lot of trouble learning all these languages which just recycle the same old things slightly modified. Unfortunately I converted to Squeak and then Pharo , a couple years ago. But better late than never :)

By the way you do not need to be a "snob" Smalltalker to be upset about mainstream's software disregard of good designs. There are endless posts on C++ design, Java design, Javascript design , Eclipse design , Visual Studio design, the horror of MFC, the horrors of web development, the horrors of android development and so much more.

[zak_mc_kracken]

> Does your definition of "bad reputation" also includes modern software basing itself on ideas and implementation that either originated from Smalltalk or greatly improved by it, like GUI MVC , mouse integration, VM , Test Driven Development , IDE and much more ?

No, my definition of bad reputation is perfectly demonstrated by your tone and attitude throughout this thread. You don't even seem to be aware of it, which is mystifying.

Try to step back for a second, reread what you wrote and start wondering if you'd be even remotely interested in joining a community filled with people with a similar elitist and condescending attitude such as yours.

You like Smalltalk, I get it. Good for you. Now try to learn to promote what you like without making it sound like everyone who doesn't share your passion is an idiot.

[kilon]

You assume too much. I never called other people idiots. There is much more to coding than good design. Mainstream coding choose to focus on features, performance and background compatibility. Thats not stupid its practical.

Many of the good designs of Smalltalk have been integrated to modern coding as well. There are complex practical reasons why good design and ease of use has not been the focus for the majority of programming languages for very long time.

To classify myself as elitist you will have to find at least one time of me mentioning Pharo as best solution out there. Quite the contrary I already said that it comes with its own share of problems and issues.

I am not here to promote it, I am here to help people understand what it is and let them make their own mind if they are interested in giving it a try or not.

[justbeast]

Ugh, I agree with zak_mc_kracken.

The Pharo community needs to knock it off, with that kind of arguments. (And I say that, being a part of that community).

Pharo is NOT too cool and too well designed for the mainstream. :( It /is/ cool, and has a lot of good work put into it. But it still needs a lot more work (especially in documentation and tutorials) before it's really useable by people without extensive Smalltalk experience. So, everybody shut up and roll up your sleeves and work. And be humble.

[kilon]

First that was my argument and my opinion as I stated several times already. Not an opinion of a whole community. Second I prefer to say things as they are instead of being humble.

I don't believe for example its good design to depend on C libraries so heavily especially for something as essential like GUI development . I know for at least one bug in GTK that took a year to get resolved on MacOS because most people were not interested in it. In Pharo bug fixing is a lot easier because the language is dynamic and live and it has plenty of powerful IDE tools to make your life easier find bugs and resolved them. Same process in C or C++ is a pain in the ass. Python community chose to heavily depend on third party C/C++ GUI APIs .

I completely agree about documentation and tutorials but that does not make Pharo any less cooler in my back or worse designed , its makes it partly undocumented. Which is one of downsides of using Pharo.

And this is not just about Pharo, take Common Lisp and compare it with Javascript, how one language has been designed and how another. Which one is most popular ? How many articles have been written about Javascript ugliness ? What about C++ and Java way of doing OOP ? Compare it with the way Smalltalk is doing OOP.

Good design have been proven again and again in the software world highly unpopular , because people prefer to buy features. You can be humble and you can be honest, but you cant be both. I chose to be honest.

[zak_mc_kracken]

> You can be humble and you can be honest, but you cant be both

I... I literally have no words.

[proksoup]

This would be great if there weren't so many red pills to choose from.

Like calling it "the" red pill is overselling it I mean.

It's "a" red pill.

[kilon]

As far as me is concerned to call something a red pill , it will have to offer a very diffirent experience. Thats is definetly not the case when it comes to coding, where you have the same old same recipe with some new things here and there. This is why also it took me so long to get used doing things in Pharo compared to learning another programming language which would be far faster. Pharo requires a rethinking of the fundamentals of the coding workflow.

You could argue that some language like Lisp requires the same, but the problem is that Lisp is just a language, Pharo is a lot more than that.

So for me, Pharo is the only "red pill" I can think of. Not because its diffirent but because is so fundamentally diffirent. Everything else is just blue pills with some red spots here and there. Thus I cant call Pharo , "a" red pill.

But if you have something else that is as diffirent as Pharo is I am mostly welcome the info , love to try fresh approaches to coding :)

Another thing to note here is that I dont use the term "red pill" to identify it as something superior. Its not superior , far from it , it come with its own problems and weaknesses. Pharo is neither a paradise or a utopia.

Pharo is not for everyone but for specific people looking for a very diffirent way of coding. But even they may not like Pharo.

In the end Pharo is another way of doing coding, it wont make you sexy with the ladies or turn you into a super coder.

[lispm]

> You could argue that some language like Lisp requires the same, but the problem is that Lisp is just a language, Pharo is a lot more than that.

Actually Lisp is so much more.

Lisp is a whole family of programming languages and its implementations. From Lisps on tiny micro-controllers, PCs, servers, to supercomputers. From simple interpreters to highly optimizing whole-program compilers.

Pharo is just one particular implementation of the programming language Smalltalk.

[zenlot]

"You could argue that some language like Lisp requires the same, but the problem is that Lisp is just a language, Pharo is a lot more than that." - You could possibly try Racket.

[draven]

This "red pill" metaphor really can apply to anything. For example for a high-level programming language user, C could be a red-pill if learning it helps them visualize what's happening automagically thanks to the VM/interpreter of their usual language.

[CyberDildonics]

It's also too cool to have a hello world that you can give to someone come in under 20 MB.

[justbeast]

Nonsense. Hello world code in Pharo / Smalltalk is still a line or two, like in other languages.

You're probably referring to the fact that there's an option to deploy the hello world PLUS the VM it runs on, in a single package. That's like saying "You can't give a Java hello world to someone under 50 MB". Yes, technically true, the couple of lines of Hello World source code don't work without a 50 MB JRE. But you're being disingenuous.

[CyberDildonics]

You can't give a Java hello world to someone under 50 MB.