|
|
|
|
|
|
by justbeast
4077 days ago
|
|
|
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. |
|
|
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.