pharo VS rust-analyzer

I think in part it's because the idea that programming is text and math-based is too ingrained in society.

For example, we talk about programming languages. But IMO there are also programming systems such as Smalltalk [1]. I've programmed 2 years professionally in it, currently looking for an engagement in a different language (a curiosity thing, also a resume thing).

I think Smalltalk has a lot to offer by switching the programmer's view of thinking about programming systems rather than programming languages.

Moreover, programming systems is also not where it is at. One downside that Pharo in particular has is that the community is small. A lot of plugins/libraries that are a given in other languages aren't there! For some, however, this is a strength because one gets to learn much better how to build stuff from the ground up and tinker on it by yourself. Given that there is still a lot of low hanging fruit it is easy to become a contributor.

But this part, whether a community is big or small means that I think it's smarter to think about programming ecosystems where a programming language or programming system is the central hub connecting the programming community together.

Why don't schools teach about programming communities? See my first sentence ;-)

[1] https://pharo.org - a modern Smalltalk

I read Pharo for just a split second

And Pharo is a good Smalltalk!

What you need is a cross platform GUI framework that still is a mutable environment allowing easy extend ability with a simple language. May I suggest Pharo Smalltalk?

https://github.com/pharo-project/pharo/issues/9729#issuecomm...

When all the required dependencies are being found on your Fedor install we should wonder why "the VM seemed to hang and never started properly".

Consider playing with Pharo [1], it shows how it can still use Git to store sources in background.

There is LivelyKernel [2] but some versions are more file-oriented (like Lively 4 [3)

[1] https://pharo.org/

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer