While there are certainly folks doing other things in it, the Pharo project focuses on the problems of improving the Pharo project to make it easier to develop Pharo.
As with many OSS projects, the developers are there to scratch their itches, which is Pharo, not just random programming projects.
You'd like to think that these goals, improving the development experience, would be generic enough to "lift all boats". I mean, they do solve a lot of issues with Smalltalk distributed development, distribution, source code control, etc. But, to be honest, those are all advanced cases and, while part of the development experience, don't do much to attract developers who are doing distribute "IDE" development.
I've tried several times to work with Pharo as a tool for random GUI apps, and found the experience quite frustrating. But, clearly, the Pharo developers continue to make progress, its just that whatever their destination is, it's not congruent with mine, so I dabble and leave.
If you want a more friendly approach to Smalltalk (which, you'll note, Pharo does not claim to be -- there's no mention of Smalltalk on their front page), then take a look at Squeak.
https://github.com/Cuis-Smalltalk/Learning-Cuis/blob/master/...
One of the images is the Pharo MOOC. The website has links to several documents to get you started.
No offense but you kind of have to look around it to not find the ways in which the Pharo team attemps to get you underway.
Pharo defies all of those conventions (well, maybe not Github, but even that is unusual). People just aren't accustomed to in-IDE tutorials. It doesn't even occur to people that such things might exist.
It's hard to notice that which you never even imagined possible.
It IS alien to those who come from text editors and IDEs.
OTOH, it makes our usual development environments look crude in comparison. In fact, Smalltalk 80 still has that effect.
Well, yeah. But it opens when you open an image for the first time. It's right there in plain view. The first thing you see on the website are "discover" "download" and "learn" buttons. It's all these in plain view; it's not hidden away.
I had to switch to my Mac to get it to properly launch. The Pharo onboarding experience needs work.
I often see GitHub repos that seem very interesting and even quite liked but as a newcomer you're just supposed to figure everything out blindly by yourself.
P.S: Thanks for saving me the time to download and try out Pharo.
Lots of FOSS is written that way, especially corporate PR FOSS, where engagement and other things are important, because otherwise the cost/value calculation doesn't work out yadda yadda.
But lots of other FOSS is released just because someone wrote something, and then just put it out for others to use, if they're curious. They don't owe you anything, and spending time working on the onboarding UX, tutorials or guides might detract from what they wanted to do: entertain themselves solving a problem they care about.
Unnecessarily snarky
if it's a commercial product, they might get your money, but most projects on github aren't
I'd just think if you write something like a programming language of all things you'd want others to use it and have a pleasant experience getting started.
You might be surprised how many different nuances exist in what motivates humans.
I have even avoided to share code in public repositories, because I didn’t want to be bothered by feedback like yours, because I didn’t bring the documentation up to a level that someone farther away from my little niche need and use case can understand it.
While such feedback isn’t going to kill me, it’s nonetheless one of a million tiny little cuts that my life is more pleasant without.
i don't want other people to use my open source code unless it's more useful to them than the alternatives, and i think they're a better judge of that than i am; trying to convince them to use it would imply i think i'm a better judge of it than they are
i'm always happy to talk with them about it, but i'm not coming from an advocacy perspective, and i think people who are are bad
And that worked "got curious, downloaded and installed it" but then hit a bug "Lots of things to click on, and no text editor".
We can see that they are trying to explore using the knowledge they already have, as we might expect.
I wanted to follow a tutorial (or another guide) to learn about Pharo, but couldn't find any, at least in the official docs. That's the point I'm making!
Smalltalk in general is about a fully integrated environment, so everything lives inside of the environment, including applications, docs and also the tutorial.
Once you launched the Launcher, you create a image (latest stable, official distribution), launch the image, press the "Next" button until you see "You can learn Pharo by clicking on the following expression:" which launches the tutorial. That's about it.
And I did that the first time just now, without having any experience doing so in the past, or knowing 100% where to go. Everything was easily guessable. But I did know since before what a Smalltalk environment usually looks like, even though I haven't used Pharo specifically before for this.
https://ceronio.net/2017/07/first-steps-with-pharo-smalltalk...
In this lineage of computing, you do not edit text files and then run a compiler and then run your tests and then cross your fingers and ship to prod. That is, if you like, the “Frankenstein” approach, you cobble together dead body parts into a chunk of dead code and then reanimate it with a lightning bolt. And it has eaten the world so uh can't really bash it.
But another lineage is preserved in spreadsheets and smalltalks, where that general outlook is considered a little barbaric and you want to instead be surrounded by your living, breathing program, with everything available to inspect and tinker with and test and replace. You run the image and you are launched into your running program. Yeah it doesn't do anything yet, because you haven't told it what to do... but here you are, ready to mold and model the compute like clay into whatever your imagination desires. The first few pots you throw, you're lucky if they don't collapse on you.
My standard example of the mentality difference is Object.become. Imagine I tell the standard Java developer, “we search through all of memory, find all private and public variables pointing to that object, and instead point them to this object...” They will look at you like you are nuts! But that’s essentially the underlying functionality needed for “you can edit the method and the entire system will start using your new method.”
So things like versioning and inspecting and editing are generally baked into the image rather than external tools because you want to be able to debug and undo your changes in vivo ... There is going to be an impedance mismatch, and the community can certainly make it easier on you for sure but there is going to be a lot of unlearning no matter what.
Ummm I daresay the vast majority of Smalltalk programmers never have (and never will) use become:
Extreme TDD is amazing - you write a test, run it, and when it fails you basically fill in the chunk of code right from the error window and continue. It's not always super obvious how to get into the flow, but I found that although I didn't feel productive enough with the Pharo ecosystem, I _really_ miss the smalltalky development flow which foregoes using text files to organize code.
please note you _do_ have to type in code in text, but not monolithic amounts of it as you would in (say) a C++ program.
Select the package, class, and then method (or the options to create new ones) and the method will be in an editor pane for you. Start changing it, and the change is immediately applied once saved. No need to rebuild the world and restart the image. (Of course, that leads to some fun things where you can redefine True/False and break the image right there on the spot. Pharo seems to do a good job of blocking you from changing things like that so easily.)
Smalltalk code "lives" in a database. You interact with that database. The code is also serialized to a file if you happen to want more conventional access, but that's not the normal route. Though serialization to files is how Pharo and others allow you to interact with git and collaborate with other people.
I don’t have time to waste on something that ignores the last 40 years of progress in that realm.
They're not selling a product here, they're releasing software they've written in their own spare time. If you can't spare 30 minutes for running through the tutorial, why should they spend more time catering to you rather than spending it on more interesting problems?
Of course, if you're content with your community stagnating and nobody ever using that software, then there's really no reason to put that effort in.
I remember similar arguments about Linux installers. Why should they cater to people who don't even know fdisk? We have kernel to work on, UX of an installer - with obvious, immediate impact on adoption and getting new users - is boring in comparison. Having installed Fedora last week I can attest that this line of thinking, fortunately, went away in Linux as far as installers go. The chances of it going away in the Pharo community, however, are slim at best.
Like - when I first learned about Smalltalk, and looked at the syntax, I wanted to try it out right away! Playing with that realm of object oriented programming looks like fun!
But jumping through hoops to make it work is not fun - the process of just setting things up and trying to pick through the whole alien interface completely evaporated my enthusiasm. It quickly became clear to me that you can't 'just sit down and write code' the way you can with basically any other modern language I've worked with. You have to do a bunch of other stuff first. And I don't want to do that.
You can open a web browser, hit F12, and immediately start writing javascript and running it. You can use notepad to make an .htm file, drag it into the browser, and boom it's a web page. If you're on a device that makes task switching awkward, you can navigate straight to codepen.io, no sweat. You know what I mean? Immediacy is an essential quality, for me - obscurity, esotericism, inaccessibility and poor usability are all banes of my existence.
It's like sure, I can do anything I put my mind to - I can spend the next hour, the next day, the next week, month, year, decade, learning to do this thing... but that's time I'll never get back, and that's time I could be spending more efficiently stepping into something else, equally exciting and different and new and interesting, with significantly less barrier to entry.
If you care about your work, and your goal is to expose others to it, then you need to put the work into making it accessible. That's been my experience.
Put something like that on the front page and you're good to go.
I'd say: to show that its authors have a sense of decency, at least. But let's not assassinate the lads any more than this.
I did ask. See my other comment[1]. The only thing I got out of asking was name calling, dismissive and rude remarks, and the immortal "do it yourself". Before the package manager thing, I did the same - years earlier - asking on the mailing list how to bind keys to commands. What I got out of this was name calling, dismissive and rude remarks, and the immortal "learn to use the mouse already!"
Sure, nobody owes anything to anybody, not even not being toxic and abrasive. But I also don't owe the toxic and abrasive community anything - certainly not avoiding criticizing it. Right?
As in the reply to a sibling comment, yeah, nobody owes anything to anybody. But, you know, we do things we don't owe to anybody every day. I don't owe my neighbor saying "hi" when I meet them, but I still do. I don't owe my guests anything, but I still offer them a seat. Pharo community tries to do it both ways: they appear to want new users, but when you come closer you'll see what they actually want is new fanatics. Screw that. They don't owe me anything, but neither do I owe them keeping quiet about what I've been through.
Smalltalk is beautiful. And, Smalltalk is not just Pharo. There are other communities, and there are much better Smalltalks out there. Cincom (no affiliation) Visual Works is so much better an implementation that it's scary. Pharo could be like that, if only the "incredible community" stopped killing all semblance of stability with constant rewrites of everything, stopped treating users like unwanted baggage, stopped insulting people whose use cases don't completely fit the community's idea of what's good and bad.
Pharo community is a museum that preserved the culture of Smug Lisp Weenies intact. Good for them. Meanwhile, Pharo being advertised as "the most actively developed and most advanced Smalltalk" - which means that it's first, and very often last Smalltalk tried out by people - hurts the wider community and hurts Smalltalk adoption. They don't care. Is this a decent behavior? I think it's irresponsible, at the very least.
This has been a problem before:
https://news.ycombinator.com/item?id=32121722 (July 2022)
https://news.ycombinator.com/item?id=31418768 (May 2022)
https://news.ycombinator.com/item?id=31418760 (May 2022)
I'm not going to ban you right now because I didn't see other cases of this in your recent history, but please fix this going forward so we don't have to.
But I did try to get commercial license, once. I had a project and a client for it, and a seemingly ideal use case. However, I wasn't able to sell the client the kind of licensing scheme Cincom wanted (they weren't unreasonable, just not what the client was willing to have). I ultimately abandoned the idea. Still, even knowing that I'm just a solo developer that's not going to earn them much, my contact with an account from Cincom was very pleasant and helpful. I saw the changelog for the next version of VW - there was a lot of really nice stuff there! Welcome fixes, improvements in many important packages, new functionalities - the product is evidently alive and getting better, but there was one thing missing. There were No. Breaking. Changes. I could reasonably expect my app to work if I built with 8.x version and later upgraded to 9.x. Can you imagine this?
Cincom is, of course, a company targeting big corporations - a for-profit organization, and the most important part of VW is closed source. If Cincom dies, VW will probably also die, along with my projects. It's a risk, and it's not ideal. The fact that the PUL version is 6 years old at this point also isn't nice. And, above all, I don't wear suits and neckties. So, I'd really prefer fully open source Smalltalk (the only reasonable alternative, Smalltalk/X, also has the compiler distributed only as a binary blob) Unfortunately, Pharo simply cannot be that Smalltalk for me.
To the dead sibling commenter: sure, I don't event want anybody to care. I'm writing all this for my own satisfaction, so please, just do your job of not caring properly and ignore it all.
https://news.ycombinator.com/newsguidelines.html
Edit: This kind of thing has been a problem before:
https://news.ycombinator.com/item?id=33024799 (Sept 2022)
https://news.ycombinator.com/item?id=22714938 (March 2020)
https://news.ycombinator.com/item?id=11301279 (March 2016)
Please review the rules and stick to them from now on.
p.s. I appreciate your love for Smalltalk but if you express it using swipes and attacks, you're actually discrediting it to less knowledgeable readers (i.e. most of us). It's not in your interest to turn people off of something you love, so you should follow the rules out of self-interest too.
Also, frankly, Pharo has its niche. It isn't really competing for attention in the same way as others, since it is the "goto big Smalltalk"
I love Smalltalk. The language is great, incredibly powerful even though it rests on just a few simple concepts. The design and architecture of some of Smalltalk libraries is marvelous and should be made into UNESCO world heritage site for OOP design. PetitParser is unmatched in the ease of creating and extending parsers, not even PyParsing comes close (Raku grammars are close but use another metaphor for actions, ScalaParsing is... somewhat related but limited). The idea of finally working with a live codebase instead of its dead carcass[1] is frankly groundbreaking - and older than me, apparently. The Smalltalk debugger is a work of art, and the idea of working with images that contain the "whole world" in them is actually very appealing if you ever had to write a Dockerfile.
However, while Pharo may well be the most "advanced" Smalltalk(-like) environment, it's also one of the worst. On my Linux machine releases after 5 refused to as much as display anything - I got an empty window and the VM seemed to hang and never started properly. Glamorous Toolkit version did work, even though they share most of Pharo code. The churn in UI toolkits, the constant rewrites of everything, the utter lack of any kind of documentation (including on classes!) of installable packages, deprecation of tools that work (ofc after breaking them) in favor of tools that don't, yet leaving the former in place just to confuse users (b/c what other goal could it have?) - that's Pharo in a nutshell.
A few years ago I went to complain about the lack of backward compatibility and the fact that a tool, Package Manager, that used to work perfectly well, stopped working altogether. I learned that nobody under the Heavens cares more about backward compatibility than Pharo community (praphrasing: "look, we're even developing all-new annotation/pragma based system for marking and automatically fixing incompatibilities!") and that nobody uses the package manager anyway because they use... something else, I forgot, but anyway - the new thing was nowhere in the menus, while package manager stayed in the same place it was before. I gave up when I got no response after asking "how the heck should I, the user, know about deprecation of a tool if it's not indicated anin any way in the UI". What I got instead of an answer was a bunch of name calling and the usual suggestion for me to go and fix it myself.
I still love Smalltalk. If you love it too, but feel that - at least with Pharo - that feeling is not mutual, go grab Visual Works (no affiliation). Personal license is restrictive, and the version you get is 6 years old at this point. But. It comes with thousands of pages of PDFs with up to date documentation, manuals and guides. It comes with a stable, battle-tested UI framework, not based on Morphic but integrating seamlessly with your env windows (btw: "Pharo can do it too", say Pharo users, "it's just that nobody cares about such things") while still allowing all the dynamic introspection Smalltalk is known for. The infra for versioning and sharing code is idiosyncratic - you need to spin a local Postgres instance - but solid and surprisingly (if you come from git) powerful. There's a working package manager and you can install and run code from the nineties, something that's just absurd to attempt in Pharo, despite all the "caring" about backward compatibility. Yes, the VM is closed source, but it at least starts up properly.
It's a bit underwhelming in the performance dept, which made me reconsider starting one project with it, but by that point I already built my own little Smalltalk environment after fixing a lot of glitches (because, other than the VM, the source of everything else is available and you can modify it as easily as any other code) and I honestly felt really comfortable in it. It's incredibly similar to Emacs in terms of power and workflow, but with proper widgets and no need to worry about terminal users.
I also tried using GNU Smalltalk for a project, but that's basically dead at this point, with a lot of things unfinished. I still managed to build quite nice shell PoC in it. I also tried Smalltalk/X-jv, and it was kind of ok, but VW looked more polished and I didn't need the other langs integrations that Smalltalk/X does, so I stayed with VW. Cuis is also a nice attempt, but I wanted to break out of Morphic, so I didn't investigate it too deeply.
TLDR: Smalltalk is not just Pharo, there are Smalltalks that are not like Pharo, that don't treat users like unneeded baggage, that take integration with modern GUIs seriously, that have a lot of advanced tooling that's actually useful and needed. Oh, and also, there are Smalltalks that are not actively hostile to keyboard shortcuts! Give one of them a chance, you'll be surprised!
[1] https://gbracha.blogspot.com/2021/08/how-is-programmer-like-...
That seems close to misrepresentation, Pharo works OK.
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
Pharo 9.0.21 on quad-core 3.0GHz Intel® i5-3330® with 15.8 GiB of RAM and 2TB SATA disk drive; using Ubuntu™ 22.10 x86_64 GNU/Linux 5.19.0-29-generic
COMMAND LINE:
/opt/src/pharo-vm-Linux-x86_64-stable/pharo --headless [...]
Yeah. It indeed works. With --headless. It's "just" incapable of displaying GUI.I use Fedora. I ran every other available Smalltalk implementation on it, including Visual Age. GToolkit distribution, too, worked without problems. Pharo didn't, and still doesn't. I know that wanting this to be fixed is lazy of me and shows incredible entitlement, so I stopped - but please don't tell me I misrepresent something.
(SystemWindow windowsIn: World
satisfying: [:w | w model canDiscardEdits])
do: [:w | w delete].
works in headless mode. I guess #windowsIn:satisfying: simply returns an empty array?But, why do you ask?
-▶ ~/portless/pharolauncher/pharo-vm/pharo --headless Pharo10-SNAPSHOT-64bit-0618067.image a.st
with a.st: Object subclass: #BenchmarksGame
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: ''!
Transcript show: BenchmarksGame!
First signals an error: primitive #primLoadSymbol:module: in TFFIBackend failed
this seems to be related to libgit, as the stacktrace ends with: LGitLibrary(FFILibrary)>>ffiCall:
LGitLibrary>>libgit2_init
but it continues running and displays: BenchmarksGame
and then hangs. I suspect I should tell it to quit, but since I don't have the GUI, I can't easily check what method I should call to do that. Ctrl+C works though.So, yes, without loading the GUI the VM and image seem to work.
BTW, Smalltalk/X has a fully functional REPL, including console based Inspector and debugger. Imagine what would happen if you suggested providing such functionality in Pharo... ("only masochists can bear working with terminal", the "incredible" community says)
What if a.st is
Stdio stdout
nextPutAll: 'Hello, world';
nextPut: Character lfIf you have an image with Seaside project (they should work in headless mode) or something similar laying around I can try running it, I suspect it'd work.
Seems like this:
https://github.com/pharo-project/pharo/issues/9729#issuecomm...
When all the required dependencies are being found on your Fedora install we should wonder why "the VM seemed to hang and never started properly" but not before.
And no, LD_PRELOAD is not something I should be using, or at least, I didn't need to use it with any other Smalltalk, nor any other program I tried to run in a the past decade. I did have to use it once, with Baldurs Gate 2 (Linux/steam version) and that's about it.
ldd libgit2.1.0.0.soThere are also "GNU/Linux Packages" and in particular rpm for Fedora 37, Fedora 36, Fedora 35, Fedora 34. I wonder if you tried them?
On the few occasions that I've needed Pharo, I simply downloaded the "Pharo stable VM for Linux" and "Pharo image" separately and unpacked them into the same directory. Maybe it helped to already have a working git install.
> BTW, Smalltalk/X has a fully functional REPL, including console based Inspector and debugger. Imagine what would happen if you suggested providing such functionality in Pharo... ("only masochists can bear working with terminal", the "incredible" community says)
You should not generalize in this way. Some people are working on the TUI Spec backend to allow all the tools to run from the console, and I don't know anyone who doesn't realize the importance of keyboard control.
Wait, what? We're talking about Linux. Pharo Launcher also, obviously, doesn't display anything, so how could I do anything there?
> report it on the issue tracker with more details.
No.
> You should not generalize in this way.
Sorry, that was too much, you're right. While it is an exact quote from a member of the community, of course it doesn't mean everyone there is that bad.
Good to know that some people have a bit of a common sense. Congrats.
Maybe you wanted to step through like this (and then go explore by yourself):
https://cuis-smalltalk.github.io/TheCuisBook/Writing-your-fi...
https://cuis-smalltalk.github.io/TheCuisBook/A-brief-introdu...
Once the image is run, a "welcome" window appears. The first two panes are a brief description and theme setting. The third pane is how to learn pharo, which lists a few resources and then tells me I can learn Pharo by clicking on the ProStef link. I do.
ProStef tells me to highlight the text below and right click and select "do it". It takes me a couple tries because I'm curious what happens if I select one word or the other. Learned: the entire expression has to be highlighted before telling Pharo to run it works, and both words were part of the expression.
The tutorial proceeds fairly obviously from there, teaching print and inspect. Some additional experimentation reveals that selecting the entire page runs everything, kind of like you might be used to in an IDE that sends things to a repl, and double clicking before the first character on a line selects the whole line.
If you're expecting the sort of tutorial where a guide not only tells you what to do, but shows you what to do before you do it to avoid any ambiguity, so that all you have to do is mimic it, ProfStef isn't that, but mimicry is a weaker form of learning. I'm not sure I'll like Pharo, but the tutorial looks like it starts okay to me. The launcher takes a moment to figure out, but if it's so difficult how do you get anything done that you've never done before?
Searched for a tutorial on the website, and found nothing! I don't want to spend 30 minutes to look at some random videos of Virtual Reality in Thames or whatever, or read "Pharo for Rubyists" (I use mostly Python). I just wanted to explore a bit, and maybe if it seemed interesting, tomorrow I would continue exploring it. But now I've deleted Pharo!
Warning to other project maintainers: just show a tutorial, or an hands-on doc, so that newcomers may get a feeling of what it is. This is especially important for relatively unknown projects like this.
Some projects that have done it right: