Offer still stands if you run into other bugs that aren't in our issue tracker.

I have `zed --version` working on my Windows machine:

PS C:\WINDOWS\system32> zed --version

Zed 1.0.0 5ec84a926ef83865afb92d2a3d1ca3b419572cf9 – \\?\C:\Users\mrg\AppData\Local\Programs\Zed\Zed.exe

If you're up for it, we can pair next week to get a proper bug report filed

https://calendar.app.google/qPgW7q6upb3RqPjx5

If you have a reproducible setup for a bug we don't know about, we'd love to get a proper report of it.

You can schedule 15mins with me here: https://calendar.app.google/fyLQkqvne7EdvR8XA

I'm a support engineer at Zed - would you like to pair for 15mins so we can file a proper report?

https://calendar.app.google/69fz5NZSbZcdf43Y8

Comments URL: https://news.ycombinator.com/item?id=45892191

Points: 318

# Comments: 169

Comments URL: https://news.ycombinator.com/item?id=45891772

Points: 37

# Comments: 24

Comments URL: https://news.ycombinator.com/item?id=45572537

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43323027

Points: 7

# Comments: 0

Well, if you're looking for good REPL resources, I just happened to have done a 3 hour Julia REPL Mastery for a previous JuliaCon.

https://www.youtube.com/watch?v=bHLXEUt5KLc

I should shrink this a more bite-sized version at some point.

* Rust's tooling lets you have a base-floor of what is acceptable code that is much more palatable than non-top tier Julia codes. There's a world of difference opening a random crate's code in Rust that has been linted/clippy'd/check'd by the compiler rather than a random Julia package that a coworker/colleague just fired up. This tooling is getting better and better in Julia and I'd be interested to hear which Julia projects you worked on were really hampered by TTFX and refactoring woes. Hard agree on the footguns - I want the VSCode plugin to be better at detecting dead code, it cost me weeks on a project lately.

* I'm also excited for some notion of interfaces to come to Julia. Perhaps it will be a 2.0 thing, but there's still lots of design stuff to figure out.

* We have different understandings of "productive" for different focii then - I still find it painful to do the equivalent of `rand(1:10, (20, 20))` in Rust and I can get STEM people to be productive with Julia before you can even finishing saying "borrowchecker".

At least for some scientific computing codes, but I did learn a lot of Rust along the way and extended my knowledge into (some) embedded and systems programming. Learning has been fun and the Rust people have been very friendly.

Precisely, the most natural symbiosis for a Julia + Rust combo seems to fill a hard-realtime, critical safety or embedded niche with offline simulation.

The Py03 and maturin story is something that we haven't brought to Julia yet and I'd love to have some time to work on a tighter integration story there. For example, getting a hot-reload with Revise.jl and a bindings generator that watches file changes and recompiles and the fly so that a Julia REPL gets updated with the new definitions would be so enviable.

I haven't spoken to Tim Holy to see how to string that together but many of the pieces are there.

Now I've done a "From Julia to Rust" workshop at the latest JuliaCon and an accompanying survival guide, so that still ongoing work.

When I wrote this, my main takeaways were numerical computations with arrays, which don't tend to use for loops in Rust, and which require grokking iterators for maximum performance and rayon-parallelism boons.

To a Julia audience, seeing this style of iterator chaining is quite a new flavor to think about composing computation, so I wanted it was with that audience in mind that I wrote this.