Earlier quoted context omitted.
I think OO has fallen out of fashion because there's a perception it can more easily lead to confusing code. While one can write confusing code using FP, it's not as easy to do.
What's FP?
Pharo 9
91–100 of 232 posts
Re: Pharo 9
#92The page seems to be going out of it's way to not mention the word "Smalltalk". Does anyone have an idea why that is? Does Smalltalk have such a bad reputation nowadays or has someone trademarked the term?
I've noticed that as well - it's a bit strange given that Pharo is a fork of Squeak, which does proclaim its ST origins on its front page. I wouldn't say Smalltalk has a bad rep nowadays, but it used to be knocked for being too expensive (the cost of ST licences back when was beyond a joke), too slow, and producing nasty-looking non-native GUIs. These have almost all been fixed.
The second reason is that the general knowledge about Smalltalk is very poor, and most people only remember that it is something old and long dead. Try to sell a dead fish.
Re: Pharo 9
#93Earlier quoted context omitted.
I've noticed that as well - it's a bit strange given that Pharo is a fork of Squeak, which does proclaim its ST origins on its front page. I wouldn't say Smalltalk has a bad rep nowadays, but it used to be knocked for being too expensive (the cost of ST licences back when was beyond a joke), too slow, and producing nasty-looking non-native GUIs. These have almost all been fixed.
hm, does Pharo have native-looking GUI now?
Re: Pharo 9
#94Earlier quoted context omitted.
I've noticed that as well - it's a bit strange given that Pharo is a fork of Squeak, which does proclaim its ST origins on its front page. I wouldn't say Smalltalk has a bad rep nowadays, but it used to be knocked for being too expensive (the cost of ST licences back when was beyond a joke), too slow, and producing nasty-looking non-native GUIs. These have almost all been fixed.
hm, does Pharo have native-looking GUI now?
Re: Pharo 9
#95Earlier quoted context omitted.
Maybe Smalltalk sounds old like COBOL. It's hard to re-kindle interest in old tech in the eyes of new devs. It seems every generation of programmers want to have their "own" tools, even if they're worse than the previous ones.
You mean like C, born in 1972?
Re: Pharo 9
#96Earlier quoted context omitted.
Yeah, the more usual wording is " given a free rein", which makes it a little clearer. A monarch isn't given their reign, it's theirs by right (well, with a bit of hand-waving. Or possibly sword-waving, but not since Henry VII).
For English kings you forgot William III
Re: Pharo 9
#97Earlier quoted context omitted.
You mean like C, born in 1972?
C never really fell out of favor, though. And it's also the only available choice apart from assembler in many circumstances. But trying to revive interest in Ada, D, Sather, Prolog, etc would be a lot more difficult.
Apparently people don't have any issue hanging to an OS about the same age as COBOL.
Re: Pharo 9
#98Thank you very much for explaining what Pharo is in one sentence on the linked page. Seriously, other projects and submissions should take notice because the general attitude is as if everybody knew exactly what your project is and what can be used for.
Re: Pharo 9
#99Earlier quoted context omitted.
Not a lesson I was expecting to learn today, but here we are. I always thought it was the "reign" version because monarchs can "reign freely".
Yeah, the more usual wording is " given a free rein", which makes it a little clearer. A monarch isn't given their reign, it's theirs by right (well, with a bit of hand-waving. Or possibly sword-waving, but not since Henry VII).
Re: Pharo 9
#100Earlier quoted context omitted.
You mean like C, born in 1972?
C never really fell out of favor, though. And it's also the only available choice apart from assembler in many circumstances. But trying to revive interest in Ada, D, Sather, Prolog, etc would be a lot more difficult.