And working on a fuse thing that exposes my running image as a filesystem so that I can such tools as well.
But saying that the tools are different and you cannot be bothered to use them? Look, Visual Studio is a monster beast, with tons and tons of features, including Azure ones. It takes a serious while to master.
And vim also takes a serious while to use well. Especially when we use a couple of plugins.
An engineer knows the tools. Then a specialist masters them. The master makes them. Or changes them.
Pharo allows one to do that. Without strings attached.
I believe the point the parent is trying to make is that when you spend the time to learn Visual Studio, vim, etc. you can transfer that knowledge to multiple languages. With Pharo those tools are limited to, well, Pharo.
The benefits of learning a particular tool are essentially proportional to how often you use that tool. The greater flexibility of other tools such as vim means that the cost of learning it can be amortized over essentially as many projects as you wish. The costs for learning Pharo tooling are only spread over as many Pharo projects you do. If you don't believe you'll be doing all that much in Pharo, it makes it a fairly daunting proposition to invest that time.
And working on a fuse thing that exposes my running image as a filesystem so that I can such tools as well.
But saying that the tools are different and you cannot be bothered to use them? Look, Visual Studio is a monster beast, with tons and tons of features, including Azure ones. It takes a serious while to master.
And vim also takes a serious while to use well. Especially when we use a couple of plugins.
An engineer knows the tools. Then a specialist masters them. The master makes them. Or changes them.
Pharo allows one to do that. Without strings attached.